From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andrew Cooper Subject: Re: [PATCH v3 04/16] hypervisor part of add vmware_port to xl.cfg Date: Mon, 8 Sep 2014 16:32:02 +0100 Message-ID: <540DCBF2.40209@citrix.com> References: <1410182158-8542-1-git-send-email-dslutz@verizon.com> <1410182158-8542-5-git-send-email-dslutz@verizon.com> <540DC4B6.1000707@oracle.com> <540DE5D3020000780003222A@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <540DE5D3020000780003222A@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich , xen-devel@lists.xen.org, Boris Ostrovsky , Don Slutz Cc: Kevin Tian , Keir Fraser , Ian Campbell , Stefano Stabellini , Jun Nakajima , Eddie Dong , Ian Jackson , Tim Deegan , Aravind Gopalakrishnan , Suravee Suthikulpanit List-Id: xen-devel@lists.xenproject.org On 08/09/14 16:22, Jan Beulich wrote: >>>> On 08.09.14 at 17:01, wrote: >> I wonder whether we should enable #GP intercepts only when we know that >> the guest is VMware-aware (which we do as far as I can tell since we >> have a config option). > I didn't look at the patches themselves yes, but I very much expected > this to now be the case considering discussion on the earlier version. > If it's not, I'm not even sure looking at the new version is going to be > of much use... > > Jan > I find it incredibly hard to believe that VMWare do unconditional #GP exits, and looking at the Intel manual, you do not actually need to intercept #GP faults. The "unconditional I/O exiting" control can be used to cherry-pick specific IO ports in combination with the IO port bitmap, ahead of the #GP fault due to a failure of IOPL. I would expect AMD has a similar option. ~Andrew