From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Liguori Subject: Re: [PATCH] KVM: emulator: Only allow VMCALL/VMMCALL trapped by #UD Date: Sat, 05 Jan 2008 20:29:03 -0600 Message-ID: <47803CEF.7000303@codemonkey.ws> References: <200801040936.08670.sheng.yang@intel.com> <477D9610.4010605@codemonkey.ws> <10EA09EFD8728347A513008B6B0DA77A029B54D6@pdsmsx411.ccr.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, "Liu, Eric E" To: "Dong, Eddie" Return-path: In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A029B54D6-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@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 Dong, Eddie wrote: > Anthony: > Actually I am wondering if the binary used for VMMCALL could be > assumed will never be used by Intel processor or vice versa. BTW, what > is the nenefit to remove hypercall page, which provide more clean > approach IMO? > A hypercall page doesn't help the situation with respect to migration between an AMD and Intel system. It was bad enough that Intel and AMD couldn't just agree on a common instruction in the first place. It would just be mean if you reused the other guys VMCALL instruction for something else. You guys can't be that mean, right ;-) Regards, Anthony Liguori > thx,eddie > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/