All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: "Milan Holzäpfel" <listen@mjh.name>
Subject: Re: Re: 2.6.28.7 domU: 32-bit emulation seems to be broken
Date: Mon, 10 Aug 2009 14:59:31 +0200	[thread overview]
Message-ID: <200908101459.31377.Christoph.Egger@amd.com> (raw)
In-Reply-To: <20090810132121.3859d865.listen@mjh.name>

On Monday 10 August 2009 13:21:21 Milan Holzäpfel wrote:
> On Tue, 17 Mar 2009 09:52:59 -0700
>
> Jeremy Fitzhardinge <jeremy@goop.org> wrote:
> > Sven Köhler wrote:
> > > Jeremy Fitzhardinge schrieb:
> > >> I need to find/set up an AMD system to try to repro it I think.  I
> > >> think the problem is actually the return from the syscall, rather than
> > >> the syscall entry itself.  What happens if you run the program under
> > >> either strace or gdb?
> > >
> > > The program just works:
> > >
> > > # strace ./a.out
> > > [...]
> >
> > OK, that confirms that its sysret32 that's failing.  vdso32=0 on the
> > kernel command line should be the workaround until we've got a proper
> > fix.
>
> Hi,
>
> 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 ?

Christoph


-- 
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632

  reply	other threads:[~2009-08-10 12:59 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 [this message]
2009-08-11  7:36                                 ` Milan Holzäpfel
2009-08-14 20:55                                 ` Jeremy Fitzhardinge
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=200908101459.31377.Christoph.Egger@amd.com \
    --to=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.