From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Vrabel Subject: Re: Xen 4.3: x86 32 bit code removed or depreciated? Date: Wed, 10 Jul 2013 13:03:02 +0100 Message-ID: <51DD4D76.9050109@citrix.com> References: <1373451839.92539.YahooMailNeo@web171305.mail.ir2.yahoo.com> <51DD54C502000078000E3CFD@nat28.tlf.novell.com> <1373455685.30183.YahooMailNeo@web171306.mail.ir2.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: George Dunlap Cc: Ian Murray , Jan Beulich , xen-devel List-Id: xen-devel@lists.xenproject.org On 10/07/13 12:32, George Dunlap wrote: > On Wed, Jul 10, 2013 at 12:28 PM, Ian Murray wrote: > >>> Just to be clear, this is the 32-bit *hypervisor* which was removed. >>> 32-bit tools in a 32-bit dom0 still work. >>> >> >> Thanks. Thanks for clearing that up. Perhaps off-topic for dev, but are there any advantages to running a 32 bit dom0 as in this configuration? > > Probably the biggest thing is about performance. Until the PVH mode > is implemented, 64-bit PV guests will have a performance degradation, > due to the way the architecture changed between 32-bit and 64-bit. This isn't really that true for real dom0 workloads. Most of the theoretical performance penalty caused by system calls having to trap into the hypervisor are offset by the general performance improvement of the amd64 archiecture (e.g., more general purpose registers and the lack of high memory needing bouncing/mapping all the time). David