[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/PCI: make all config space writes subject to XSM checking

To: Jan Beulich <JBeulich@xxxxxxxx>, xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxxx>
From: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Date: Tue, 24 Nov 2015 13:10:29 -0500
Cc: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Tue, 24 Nov 2015 18:10:59 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 24/11/15 09:42, Jan Beulich wrote:

Now that we intercept them all, there's no reason not to also uniformly
hand them to XSM. Reads (which are expected to be of less interest) get
handled as before (MMCFG accesses un-audited).

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Acked-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH] x86/PCI: make all config space writes subject to XSM checking
  - From: Jan Beulich

Prev by Date: [Xen-devel] [PATCHv6] 01/28] build: import Kbuild/Kconfig from Linux 4.2
Next by Date: Re: [Xen-devel] [PATCHv2 0/3] Implement per-cpu reader-writer locks
Previous by thread: [Xen-devel] [PATCH] x86/PCI: make all config space writes subject to XSM checking
Next by thread: [Xen-devel] [PATCH] x86/kexec: Hide more kexec infrastructure behind CONFIG_KEXEC
Index(es):
- Date
- Thread

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.