From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Roedel, Joerg" Subject: Re: [PATCH v5] KVM: VMX: Execute WBINVD to keep data consistency with assigned devices Date: Tue, 29 Jun 2010 14:32:32 +0200 Message-ID: <20100629123232.GD1788@amd.com> References: <4C286CCE.10309@redhat.com> <1277781419-13227-1-git-send-email-sheng@linux.intel.com> <4C29BF58.20107@redhat.com> <4C29CBD1.1060604@siemens.com> <4C29CE31.4080101@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Jan Kiszka , Sheng Yang , Marcelo Tosatti , "kvm@vger.kernel.org" , "Yaozu (Eddie) Dong" To: Avi Kivity Return-path: Received: from va3ehsobe006.messaging.microsoft.com ([216.32.180.16]:54039 "EHLO VA3EHSOBE010.bigfish.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1753404Ab0F2Md0 (ORCPT ); Tue, 29 Jun 2010 08:33:26 -0400 Content-Disposition: inline In-Reply-To: <4C29CE31.4080101@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Tue, Jun 29, 2010 at 06:42:57AM -0400, Avi Kivity wrote: > On 06/29/2010 01:32 PM, Jan Kiszka wrote: > Correctness is more important than performance. Since we don't know > whether the guest needs it or not, we have to enable it. The user may > disable it if he likes. Can't this code only be enabled if VT-d hardware is detected that does not support the snoop force bit? So the user does not have to struggle with configuration options that are hard to understand for a non-developer. Joerg