From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>,
xiantao.zhang@intel.com
Subject: Re: [PATCH 1/3] x86: don't allow Dom0 access to the MSI address range
Date: Wed, 21 Aug 2013 10:29:31 -0400 [thread overview]
Message-ID: <20130821142931.GG2593@phenom.dumpdata.com> (raw)
In-Reply-To: <52147C2A02000078000ED38B@nat28.tlf.novell.com>
On Wed, Aug 21, 2013 at 07:36:58AM +0100, Jan Beulich wrote:
> In particular, MMIO assignments should not be done using this area.
And just to make sure there are no regressions - have you tested
this with an upstream dom0 kernel to make sure it does not blow things up?
Or at least if it does blow up - are there any WARN or BUG to help
in coming up with a patch?
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/domain_build.c
> +++ b/xen/arch/x86/domain_build.c
> @@ -1122,6 +1122,10 @@ int __init construct_dom0(
> if ( !rangeset_contains_singleton(mmio_ro_ranges, mfn) )
> rc |= iomem_deny_access(dom0, mfn, mfn);
> }
> + /* MSI range. */
> + rc |= iomem_deny_access(dom0, paddr_to_pfn(MSI_ADDR_BASE_LO),
> + paddr_to_pfn(MSI_ADDR_BASE_LO +
> + MSI_ADDR_DEST_ID_MASK));
>
> /* Remove access to E820_UNUSABLE I/O regions above 1MB. */
> for ( i = 0; i < e820.nr_map; i++ )
>
>
>
> x86: don't allow Dom0 access to the MSI address range
>
> In particular, MMIO assignments should not be done using this area.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/xen/arch/x86/domain_build.c
> +++ b/xen/arch/x86/domain_build.c
> @@ -1122,6 +1122,10 @@ int __init construct_dom0(
> if ( !rangeset_contains_singleton(mmio_ro_ranges, mfn) )
> rc |= iomem_deny_access(dom0, mfn, mfn);
> }
> + /* MSI range. */
> + rc |= iomem_deny_access(dom0, paddr_to_pfn(MSI_ADDR_BASE_LO),
> + paddr_to_pfn(MSI_ADDR_BASE_LO +
> + MSI_ADDR_DEST_ID_MASK));
>
> /* Remove access to E820_UNUSABLE I/O regions above 1MB. */
> for ( i = 0; i < e820.nr_map; i++ )
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-08-21 14:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 6:20 [PATCH 0/3] remotely XSA-59 related adjustments Jan Beulich
2013-08-21 6:36 ` [PATCH 1/3] x86: don't allow Dom0 access to the MSI address range Jan Beulich
2013-08-21 14:17 ` Zhang, Xiantao
2013-08-21 14:29 ` Konrad Rzeszutek Wilk [this message]
2013-08-21 14:44 ` Jan Beulich
2013-08-21 14:48 ` Konrad Rzeszutek Wilk
2013-08-21 14:55 ` Jan Beulich
2013-08-21 6:37 ` [PATCH 2/3] x86: don't allow Dom0 access to the HT " Jan Beulich
2013-08-21 6:38 ` [PATCH 3/3] VT-d: warn about Compatibility Format Interrupts being enabled by firmware Jan Beulich
2013-08-21 9:13 ` George Dunlap
2013-08-21 9:24 ` Jan Beulich
2013-08-21 14:18 ` Zhang, Xiantao
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130821142931.GG2593@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=JBeulich@suse.com \
--cc=keir@xen.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xiantao.zhang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.