From: David Gibson <david@gibson.dropbear.id.au>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Sam Bobroff" <sam.bobroff@au1.ibm.com>,
"Aníbal Limón" <anibal.limon@linux.intel.com>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>,
"QEMU Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] qemu-pcc 2.8.0 linux-user segfaults
Date: Thu, 2 Feb 2017 09:30:23 +1100 [thread overview]
Message-ID: <20170201223023.GC13219@umbus.fritz.box> (raw)
In-Reply-To: <CAFEAcA-FPmqw0pt7kT=eHR_osfFbZNhrDdGAb87VxUWD_XXSNw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1490 bytes --]
On Wed, Feb 01, 2017 at 03:25:05PM +0000, Peter Maydell wrote:
> On 30 January 2017 at 23:52, Sam Bobroff <sam.bobroff@au1.ibm.com> wrote:
> >> On 01/16/2017 03:56 PM, Aníbal Limón wrote:
> >> > I'm trying to upgrade qemu to 2.8.0 in Openembedded-core and segfaults
> >> > in qemu-ppc when is executing:
>
> > I've recently encountered a similar problem and I've posted a fix. If
> > you'd like to try it, it's here:
> >
> > https://lists.gnu.org/archive/html/qemu-ppc/2017-01/msg00413.html
>
> Hmm, I missed that patch (it doesn't seem to have made it
> to the qemu-devel list), but it isn't correct, I'm afraid.
> In the patch for handling TARGET_USER_ESIGRETURN you must
> not change the nip register, because we will have just
> set it from the signal context that the guest provided
> to the sigreturn syscall. (The patch as it stands will
> cause us to reexecute an instruction after return from
> a signal handler, which isn't going to go very well).
>
> David, can you drop that patch from your ppc queue, please?
Ok, dropped, pending discussion of what the right fix is.
> (I think the change is good otherwise but I couldn't
> seem to find the bit in the ppc linux kernel that
> corresponds to moving the NIP value around.)
>
> thanks
> -- PMM
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-02-01 22:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 21:56 [Qemu-devel] qemu-pcc 2.8.0 linux-user segfaults Aníbal Limón
2017-01-16 22:03 ` Aníbal Limón
2017-01-30 23:52 ` Sam Bobroff
2017-01-31 21:49 ` Aníbal Limón
2017-02-01 15:25 ` Peter Maydell
2017-02-01 22:30 ` David Gibson [this message]
2017-02-01 23:42 ` [Qemu-devel] [Qemu-ppc] " Laurent Vivier
2017-02-01 23:48 ` [Qemu-devel] " Sam Bobroff
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=20170201223023.GC13219@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=anibal.limon@linux.intel.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sam.bobroff@au1.ibm.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.