From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steve Ofsthun Subject: Re: [RFC] Hypercalls from HVM guests Date: Fri, 07 Apr 2006 13:06:01 -0400 Message-ID: <44369BF9.9070101@virtualiron.com> References: <907625E08839C4409CE5768403633E0BA7FBC7@sefsexmb1.amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <907625E08839C4409CE5768403633E0BA7FBC7@sefsexmb1.amd.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Petersson, Mats" Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Petersson, Mats wrote: > Interesting subject - I must have missed the September patchset... I've > been thinking a lot about para-virtualized drivers for HVM guests > (because it would improve performance on some functions by a great deal > to avoid intercepting half a dozen IO operations to actually perform a > single transaction - like one READ of the virtual hard-disk). This is exactly our interest as well. > I'd like to make sure that you're aware that the AMD architecture also > has a VMMCALL instruction, which is opcode (0F 01 D9). It would be great > if you could implement some sort of auto-detect/switching so that your > code works for AMD too. Of course, we could intercept invalid opcode and > interpret the instruction, but that's far from a practical solution, I > would think. Thanks for pointing that out. I didn't realize the opcode was different. I should be able to easily alter the hypercall page initialization to use the proper AMD opcode. What is the preferred method to distinguish SVM vs. VMX from within guest code running in an HVM guest? Steve -- Steve Ofsthun - Virtual Iron Software, Inc.