From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken Date: Tue, 17 Mar 2009 14:14:37 -0700 Message-ID: <49C012BD.4020509@goop.org> References: <49BAFC72.4040501@goop.org> <49BB0184.1020503@goop.org> <49BB6F4A.90000@gmail.com> <49BC2994.6040404@goop.org> <49BCF38B.3000507@gmail.com> <49BD2CCA.6070308@goop.org> <49BD3A87.3060403@gmail.com> <49BEB487.3090503@goop.org> <49BEB526.7060608@goop.org> <49BED2DE.7060203@gmail.com> <49BED46C.2040906@goop.org> <49BFAEFA.80605@gmail.com> <49BFD56B.1040003@goop.org> <49C0089A.3060706@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <49C0089A.3060706@gmail.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: =?ISO-8859-15?Q?Sven_K=F6hler?= Cc: xen-devel@lists.xensource.com, xen-users@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Sven K=F6hler wrote: > Jeremy Fitzhardinge schrieb: >> OK, that confirms that its sysret32 that's failing. vdso32=3D0 on the= =20 >> kernel command line should be the workaround until we've got a proper=20 >> fix. > > vdso32=3D0 works. Thank you for your help! > > But i wonder: what's the drawback of this workaround? Performance=20 > loss? Or something more dramatic?=20 Slight performance loss, probably only measurable with micro-benchmarks. J