From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Christoph Egger <Christoph.Egger@amd.com>
Cc: xen-devel@lists.xensource.com, "Milan Holzäpfel" <listen@mjh.name>
Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
Date: Fri, 14 Aug 2009 13:55:27 -0700 [thread overview]
Message-ID: <4A85CF3F.9020701@goop.org> (raw)
In-Reply-To: <200908101459.31377.Christoph.Egger@amd.com>
On 08/10/09 05:59, Christoph Egger wrote:
>> I still notice this problem with vanilla 2.6.30.4 domU under Xen 3.3.2
>> (32 bit binaries on a 64 bit domU kernel segfault, AMD CPU). vdso32=0
>> still helps.
>>
>> Any news?
>>
>
> What does Linux use w/o vdso32=0 on your box ? Does it use sysenter, syscall
> or int 0x80 ?
>
> Do you boot the DomU directly or does this happen after migration from
> an Intel box ?
>
There appears to be a bug in the 64-bit xen_sysret32, which attempts to
take the sysret environment and turn it into an iret hypercall (since
iret is the only way to do a 64-bit kernel -> 32-bit user return).
I don't have an AMD test machine on hand, so I haven't had a chance to
work out what's actually failing. I couldn't see anything wrong by
staring at the code, but that probably means I was either starting hard
at the bug, or looking right next to the bug...
Could you try looking at this?
J
next prev parent reply other threads:[~2009-08-14 20:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gpe0vg$j67$1@ger.gmane.org>
2009-03-13 21:11 ` 2.6.28.7 domU: 32-bit emulation seems to be broken Sven Köhler
2009-03-14 0:38 ` Jeremy Fitzhardinge
2009-03-14 0:59 ` Jeremy Fitzhardinge
2009-03-14 8:48 ` Sven Köhler
2009-03-14 22:03 ` Jeremy Fitzhardinge
2009-03-15 11:39 ` Sven Köhler
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 17:43 ` Sven Köhler
2009-03-15 17:45 ` Jeremy Fitzhardinge
2009-03-15 22:18 ` [Xen-devel] " Sven Köhler
2009-03-15 22:21 ` Sven Köhler
2009-03-15 17:48 ` Jeremy Fitzhardinge
2009-03-15 12:24 ` Sven Köhler
2009-03-15 13:30 ` [Xen-users] " Boris Derzhavets
2009-03-15 15:32 ` Jeremy Fitzhardinge
2009-03-15 16:28 ` Jeremy Fitzhardinge
2009-03-15 17:27 ` [Xen-devel] " Sven Köhler
2009-03-16 20:20 ` Jeremy Fitzhardinge
2009-03-16 20:23 ` Jeremy Fitzhardinge
2009-03-16 22:29 ` Sven Köhler
2009-03-16 22:36 ` Jeremy Fitzhardinge
2009-03-17 14:08 ` Sven Köhler
2009-03-17 16:52 ` Jeremy Fitzhardinge
2009-03-17 20:31 ` [Xen-devel] " Sven Köhler
2009-03-17 21:14 ` Jeremy Fitzhardinge
2009-08-10 11:21 ` Milan Holzäpfel
2009-08-10 12:59 ` Christoph Egger
2009-08-11 7:36 ` Milan Holzäpfel
2009-08-14 20:55 ` Jeremy Fitzhardinge [this message]
2009-03-14 9:13 ` [Xen-devel] " Sven Köhler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A85CF3F.9020701@goop.org \
--to=jeremy@goop.org \
--cc=Christoph.Egger@amd.com \
--cc=listen@mjh.name \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.