xen-devel
Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation
To: |
Gerd Hoffmann <kraxel@xxxxxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation |
From: |
Ingo Molnar <mingo@xxxxxxx> |
Date: |
Tue, 19 May 2009 17:24:56 +0200 |
Cc: |
Jeremy Fitzhardinge <jeremy@xxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>, the arch/x86 maintainers <x86@xxxxxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>, Jan Beulich <JBeulich@xxxxxxxxxx>, "H. Peter Anvin" <hpa@xxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx>, "Eric W. Biederman" <ebiederm@xxxxxxxxxxxx> |
Delivery-date: |
Tue, 19 May 2009 08:26:11 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<4A12C84A.5070100@xxxxxxxxxx> |
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> |
References: |
<20090519095918.GA11790@xxxxxxx> <4A12A46A02000078000017E1@xxxxxxxxxxxxxxxxxx> <20090519110837.GA10548@xxxxxxx> <4A12A05C.6050004@xxxxxxxxxx> <20090519122623.GD14305@xxxxxxx> <4A12B244.8070301@xxxxxxxxxx> <20090519133138.GA8410@xxxxxxx> <4A12B97C.9040706@xxxxxxxxxx> <20090519141708.GA6008@xxxxxxx> <4A12C84A.5070100@xxxxxxxxxx> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
* Gerd Hoffmann <kraxel@xxxxxxxxxx> wrote:
>>>>> No, the linux kernel probably should do the wrmsr on one cpu only then.
>>>> Why?
>
>> | The change of MTRR's on _any_ of the guest CPUs in a dom0 context
>> | should immediately be refected on all CPUs. Assymetric MTRR
>> | settings are madness.
>
> Exactly. And thats why it is pointless to let the dom0 kernel
> write the mtrr msrs on more than one cpu.
How does this negate my claim that the Linux kernel needs no
modifications? (which i think your point is - let me know if you
have some other point here.)
the Xen hypervisor can simply repeat all requests (i.e. not care at
all about the fact that a guest does these modifications on all CPUs
it sees), or realize that the modification has already been done and
skip it. This is in no way a performance sensitive codepath - mtrrs
are only modified in init sequences - and setting mtrrs is slow and
globally serialized to begin with.
>>>>> Oops, the third "proper technical solutions" is missing.
>>>> Yeah, the third one is to not touch MTRRs after bootup and use PAT.
>>> Works only in case the CPU has PAT support.
>>
>> Which specific CPU without PAT support do you worry about?
>
> For example: I have a Notebook here, with MTRR and without PAT
> according to the boot log. "Pentium III (Coppermine)" says
> /proc/cpuinfo.
That's a really old CPU, but even Coppermine has PAT support in the
CPU. You need to go back to things like P5 200 MHz CPUs to find
PAT-less CPUs.
On the Linux side it's easy to enable it (and _such_ a patch would
make sense indeed) - it's just that nobody has yet gone through the
effort of testing and validating the PAT code on that CPU. If you
care enough, you can do it, send a patch and ping the Intel folks
about it.
Once the issues are framed correctly, Linux is helped for real.
Ingo
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, (continued)
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Gerd Hoffmann
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Ingo Molnar
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Gerd Hoffmann
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Ingo Molnar
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Gerd Hoffmann
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation,
Ingo Molnar <=
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Gerd Hoffmann
- Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Jeremy Fitzhardinge
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Jeremy Fitzhardinge
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Andi Kleen
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Jeremy Fitzhardinge
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Andi Kleen
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Jeremy Fitzhardinge
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, H. Peter Anvin
- [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation, Chris Wright
|
|
|