|
|
|
|
|
|
|
|
|
|
xen-devel
Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation
To: |
Ingo Molnar <mingo@xxxxxxx> |
Subject: |
Re: [Xen-devel] Re: [GIT PULL] xen /proc/mtrr implementation |
From: |
Gerd Hoffmann <kraxel@xxxxxxxxxx> |
Date: |
Tue, 19 May 2009 16:55:06 +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 07:57:27 -0700 |
Envelope-to: |
www-data@xxxxxxxxxxxxxxxxxxx |
In-reply-to: |
<20090519141708.GA6008@xxxxxxx> |
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: |
<20090518085902.GE10687@xxxxxxx> <4A11A3F8.1010202@xxxxxxxx> <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> |
Sender: |
xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
User-agent: |
Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1b3pre) Gecko/20090513 Fedora/3.0-2.3.beta2.fc11 Lightning/1.0pre Thunderbird/3.0b2 |
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.
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.
cheers,
Gerd
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [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
|
|
|
|
|