From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: 2.6.23.1-rt4 and kvm 48 Date: Tue, 30 Oct 2007 13:07:03 +0200 Message-ID: <47271057.5040102@qumranet.com> References: <9c21eeae0710290709x527cf4fcq52bb410907ff496@mail.gmail.com> <4726B088.1010709@qumranet.com> <4726DF66.4000000@osadl.org> <4726FE2A.1040607@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, Carsten Emde , Linux Kernel Mailing List To: Jan Kiszka Return-path: In-Reply-To: <4726FE2A.1040607-kv7WeFo6aLtBDgjK7y7TUQ@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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. I hope that Intel will add similar traps in future iterations of VT. -- Any sufficiently difficult bug is indistinguishable from a feature. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/