From: "Jan Beulich" <jbeulich@novell.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: mapping of memory below 16Mb
Date: Thu, 24 Jan 2008 16:35:48 +0000 [thread overview]
Message-ID: <4798CC74.76E4.0078.0@novell.com> (raw)
In-Reply-To: <C3BE6CE2.1B643%Keir.Fraser@cl.cam.ac.uk>
>>> Keir Fraser <Keir.Fraser@cl.cam.ac.uk> 24.01.08 17:27 >>>
>On 24/1/08 16:24, "Jan Beulich" <jbeulich@novell.com> wrote:
>
>>>> The WP attribute raises another question: Are there any plans to make
>>>> Xen use PAT rather than (relying on) MTRRs? Linux folks seem to be
>>>> finally getting closer to this, too, so even virtual PAT support may be
>>>> needed in not too distant future...
>>>
>>> We already support PAT for both PV guests and HVM guests.
>>
>> Oh, and my understanding of PAT support goes beyond just setting the
>> PAT MSR and adjusting page table flags. Specifically, if we have PAT we
>> should never need to modify MTRRs, which would eliminate conflicts on
>> updates of those that I'm seeing on various boxes, always just
>> depending on how BIOS sets them up, and always related to overlaps
>> of the video memory with existing MTRR ranges.
>
>That's a dom0 issue. Xen itself does not proactively mess with the MTRRs.
Yes and no: Yes in the sense that Dom0 could be given an alternative
hypercall to specify memory types. No in the sense that we already have
such a hypercall (setting the MTRRs) that would simply need to do
translation to PAT semantics rather than writing to the MTRR MSRs.
Jan
next prev parent reply other threads:[~2008-01-24 16:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-24 15:15 mapping of memory below 16Mb Jan Beulich
2008-01-24 15:26 ` Keir Fraser
2008-01-24 15:57 ` Jan Beulich
2008-01-24 16:08 ` Keir Fraser
2008-01-24 16:22 ` Keir Fraser
2008-01-25 7:51 ` Jan Beulich
2008-01-25 7:57 ` Keir Fraser
2008-01-24 16:24 ` Jan Beulich
2008-01-24 16:27 ` Keir Fraser
2008-01-24 16:35 ` Jan Beulich [this message]
2008-01-24 16:39 ` Keir Fraser
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=4798CC74.76E4.0078.0@novell.com \
--to=jbeulich@novell.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=xen-devel@lists.xensource.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.