qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, Khem Raj <raj.khem@gmail.com>
Cc: "QEMU Developers" <qemu-devel@nongnu.org>,
	"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] ppc: Include asm/ptrace.h for pt_regs struct definition
Date: Mon, 14 Mar 2022 11:52:48 -0700	[thread overview]
Message-ID: <304dcefe-de5a-5955-aef2-5ac6f14679f1@linaro.org> (raw)
In-Reply-To: <CAFEAcA87zZ8JoSk-1b6R8DYs255BzjNeP=HVbFEAs8yXByhQ6w@mail.gmail.com>

On 3/14/22 11:06, Peter Maydell wrote:
>> I have a custom distro building with Yocto which is using musl C
>> library instead of glibc.
> 
> Ah, musl. I found this gcc mailing list post from one of the musl
> upstream developers:
> https://www.mail-archive.com/gcc-patches@gcc.gnu.org/msg281012.html
> 
> where he suggests a different approach involving uc_regs->gregs[32]
> for ppc32 and uc_mcontext.gp_regs[32] for ppc64.
> 
> Richard: any opinion on that idea ?
Reasonable.  I would also remove the indirection between 
linux-user/include/host/ppc64/host-signal.h to linux-user/include/host/ppc/host-signal.h.

We don't support ppc32 anymore -- there are afaik no current distros supporting ppc32 with 
which we could even test.


r~


      reply	other threads:[~2022-03-14 18:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-14 17:02 [PATCH] ppc: Include asm/ptrace.h for pt_regs struct definition Khem Raj
2022-03-14 17:05 ` Peter Maydell
2022-03-14 17:22   ` Khem Raj
2022-03-14 18:06     ` Peter Maydell
2022-03-14 18:52       ` Richard Henderson [this message]

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=304dcefe-de5a-5955-aef2-5ac6f14679f1@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=f4bug@amsat.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=raj.khem@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).