xen-devel

[Top] [All Lists]

[Xen-devel] [PATCH] x86-64: refine access permission check for wrmsr to

from [Jan Beulich]

[Permanent Link][Original]

To:	"xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	[Xen-devel] [PATCH] x86-64: refine access permission check for wrmsr to MSR_FAM10H_MMIO_CONF_BASE
From:	"Jan Beulich" <JBeulich@xxxxxxxxxx>
Date:	Mon, 10 Jan 2011 09:18:13 +0000
Delivery-date:	Mon, 10 Jan 2011 01:19:11 -0800
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
List-help:	<mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id:	Xen developer discussion <xen-devel.lists.xensource.com>
List-post:	<mailto:xen-devel@lists.xensource.com>
List-subscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

We really don't want the mmconf window to move/disappear whenever we
use is ourselves, not only when we enabled it.

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

--- a/xen/arch/x86/traps.c
+++ b/xen/arch/x86/traps.c
@@ -2297,8 +2297,7 @@ static int emulate_privileged_op(struct 
                 goto fail;
             if (
 #ifdef CONFIG_X86_64
-                 (pci_probe & PCI_PROBE_MMCONF) &&
-                 (pci_probe & PCI_CHECK_ENABLE_AMD_MMCONF) ?
+                 (pci_probe & PCI_PROBE_MASK) == PCI_PROBE_MMCONF ?
                  val != msr_content :
 #endif
                  ((val ^ msr_content) &

x86_64-fam10-mmconf-wrmsr-2.patch
Description: Text document

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] x86-64: refine access permission check for wrmsr to MSR_FAM10H_MMIO_CONF_BASE, Jan Beulich <=

Previous by Date:	Re: [Xen-devel] [PATCH] x86-64: don't allow wrmsr to MSR_FAM10H_MMIO_CONF_BASE when Xen itself is using it, Jan Beulich
Next by Date:	Re: [Xen-devel] Biweekly VMX status report. Xen: 22653 & Dom0:862ef9719, Jan Beulich
Previous by Thread:	[Xen-devel] [xen-unstable test] 4780: regressions - FAIL, xen . org
Next by Thread:	[Xen-devel] [xen-unstable test] 4791: regressions - FAIL, xen . org
Indexes:	[Date] [Thread] [Top] [All Lists]