From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [kvm-devel] 2.6.23.1-rt4 and kvm 48 Date: Tue, 30 Oct 2007 13:37:51 +0200 Message-ID: <4727178F.8040005@qumranet.com> References: <9c21eeae0710290709x527cf4fcq52bb410907ff496@mail.gmail.com> <4726B088.1010709@qumranet.com> <4726DF66.4000000@osadl.org> <4726FE2A.1040607@siemens.com> <47271057.5040102@qumranet.com> <472716C1.1090102@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm-devel@lists.sourceforge.net, Carsten Emde , Linux Kernel Mailing List To: Jan Kiszka Return-path: In-Reply-To: <472716C1.1090102@siemens.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org Jan Kiszka wrote: > Avi Kivity wrote: > >> Jan Kiszka wrote: >> >>> Interesting result - you've read about the wbinvd issues? Is there no >>> wbinvd in the bios shipped with older kvm? Which VM extension did you >>> test, both Intel and AMD? I would bet that your X issues are due to the >>> same effect. X startup/shutdown involves a lot of wbinvd calls on my >>> test boxes. >>> >>> >>> >> kvm.git now traps invd and wbinvd on amd, so there shouldn't be any >> issues there. >> > > So kvm can then simply ignore the instructions, or what does it do about > them? I recall some replies in the related thread that some more work > may be required. > > It currently ignores the instructions. When device passthrough is implemented more work will be needed. -- Any sufficiently difficult bug is indistinguishable from a feature.