From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/6] add sysenter/syscall emulation for 32bit compat mode Date: Thu, 18 Jun 2009 11:48:27 +0300 Message-ID: <4A39FF5B.9080101@redhat.com> References: <1245246636-30760-1-git-send-email-andre.przywara@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Amit Shah , Christoph Egger To: Andre Przywara Return-path: Received: from mx2.redhat.com ([66.187.237.31]:40043 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753907AbZFRIsE (ORCPT ); Thu, 18 Jun 2009 04:48:04 -0400 In-Reply-To: <1245246636-30760-1-git-send-email-andre.przywara@amd.com> Sender: kvm-owner@vger.kernel.org List-ID: On 06/17/2009 04:50 PM, Andre Przywara wrote: > sysenter/sysexit are not supported on AMD's 32bit compat mode, whereas > syscall is not supported on Intel's 32bit compat mode. To allow cross > vendor migration we emulate the missing instructions by setting up the > processor state accordingly. > The sysenter code was originally sketched by Amit Shah, it was completed, > debugged, syscall added and made-to-work by Christoph Egger and polished > up by Andre Przywara. > Please note that sysret does not need to be emulated, because it will be > exectued in 64bit mode and returning to 32bit compat mode works on Intel. > > This has been tested with GETPIDs in a tight loop in compat mode on both > Intel and AMD boxes. Additionally a 32-bit userland was booted under a > 64-bit kernel and then cross-vendor migrated. > > Please apply or comment ;-) > Looks good except for the limit thing I pointed out. If the correct thing is to change it to 0xffffffff, let me know and I'll do it in place, instead of resending the whole thing. -- error compiling committee.c: too many arguments to function