From: David Vrabel <david.vrabel@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Keir Fraser <keir@xen.org>
Cc: Juergen Gross <jgross@suse.com>, X86 ML <x86@kernel.org>,
Toshi Kani <toshi.kani@hp.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Stuart Hayes <stuart.w.hayes@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andy Lutomirski <luto@amacapital.net>,
Borislav Petkov <bp@alien8.de>, "H. Peter Anvin" <hpa@zytor.com>,
"Paul McKenney" <paulmck@linux.vnet.ibm.com>,
Yinghai Lu <yinghai@kernel.org>, "Ingo Molnar" <mingo@kernel.org>
Subject: Re: [Xen-devel] MTRR on Xen - BIOS use and implications for Linux
Date: Thu, 17 Mar 2016 11:13:03 +0000 [thread overview]
Message-ID: <56EA913F.1040403@citrix.com> (raw)
In-Reply-To: <CAB=NE6UTp0T=rbOcAg88iPsfBJneY7O5-3c11VfFgAPiepoTNg@mail.gmail.com>
tl;dr?
Somewhere in here are some actual questions which I will attempt to
answer. Please try and be more concise in future.
On 16/03/16 20:08, Luis R. Rodriguez wrote:
> Toshi noted a while ago as well that if BIOS/firmware enables MTRR but
> the kernel does not have it enabled one issue might have been any
> MTRRs set up by the BIOS and ensuring the mapping is respected, in
> particular UC settings, this concern is raised above. Another issue
> though is that the kernel would be "unable to verify if a large page
> mapping is aligned with MTRRs" [3]
This is not a relevant concern for Xen guests: PV guests do not
support superpage mappings and HVM guests never see real MTRRs.
David
next prev parent reply other threads:[~2016-03-17 11:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 20:08 MTRR on Xen - BIOS use and implications for Linux Luis R. Rodriguez
2016-03-17 11:13 ` David Vrabel [this message]
2016-03-17 18:56 ` [Xen-devel] " Luis R. Rodriguez
2016-03-29 17:22 ` Luis R. Rodriguez
2016-03-29 22:14 ` Toshi Kani
2016-03-29 22:28 ` Luis R. Rodriguez
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=56EA913F.1040403@citrix.com \
--to=david.vrabel@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=keir@xen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stuart.w.hayes@gmail.com \
--cc=toshi.kani@hp.com \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
--cc=yinghai@kernel.org \
/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.