From: Andi Kleen Subject: Re: [RFC, PATCH 17/24] i386 Vmi msr patch Date: Tue, 14 Mar 2006 17:23:53 +0100 Message-ID: <200603141723.54365.ak@suse.de> References: <200603131812.k2DICGJE005747@zach-dev.vmware.com> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200603131812.k2DICGJE005747@zach-dev.vmware.com> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org To: virtualization@lists.osdl.org Cc: Zachary Amsden , Linus Torvalds , Linux Kernel Mailing List , Xen-devel , Andrew Morton , Dan Hecht , Dan Arai , Anne Holler , Pratap Subrahmanyam , Christopher Li , Joshua LeVasseur , Chris Wright , Rik Van Riel , Jyothy Reddy , Jack Lo , Kip Macy , Jan Beulich , Ky Srinivasan , Wim Coekaerts , Leendert van Doorn List-Id: xen-devel@lists.xenproject.org On Monday 13 March 2006 19:12, Zachary Amsden wrote: > Fairly straightforward code motion of MSR / TSC / PMC accessors > to the sub-arch level. Note that rdmsr/wrmsr_safe functions are > not moved; Linux relies on the fault behavior here in the event > that certain MSRs are not supported on hardware, and combining > this with a VMI wrapper is overly complicated. The instructions > are virtualizable with trap and emulate, not on critical code > paths, and only used as part of the MSR /proc device, which is > highly sketchy to use inside a virtual machine, but must be > allowed as part of the compile, since it is useful on native. I'm not aware of any MSR access being on a critical code path on a 32bit kernel. And I don't think it's a good idea to virtualize the TSC without CPU support. Why would you want to do any of this? -Andi