From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
qemu-devel@nongnu.org, "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-ppc@nongnu.org, "Khem Raj" <raj.khem@gmail.com>
Subject: Re: [PATCH v2] ppc: Include asm/ptrace.h for pt_regs struct definition
Date: Mon, 14 Mar 2022 19:02:28 +0000 [thread overview]
Message-ID: <Yi+RROpNYGqbwdyp@redhat.com> (raw)
In-Reply-To: <CAFEAcA8bKnYQ4KroudyEowv-7A+ru6A6RTrRVgjqbtEafrPJnQ@mail.gmail.com>
On Mon, Mar 14, 2022 at 06:06:40PM +0000, Peter Maydell wrote:
> On Mon, 14 Mar 2022 at 17:59, Daniel Henrique Barboza
> <danielhb413@gmail.com> wrote:
> > I am intrigued about why we didn't hit this before, especially considering that ppc64 header is just a
> > pointer to this file.
>
> It's specific to musl, which does different things with its
> system includes than glibc does.
And while we have CI testing for QEMU with Alpine that uses musl, this
is only x86_64 host. IOW we don't have CI coverage of ppc64 host
with musl, only glibc
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-03-14 19:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 17:25 [PATCH v2] ppc: Include asm/ptrace.h for pt_regs struct definition Khem Raj
2022-03-14 17:58 ` Daniel Henrique Barboza
2022-03-14 18:06 ` Peter Maydell
2022-03-14 19:02 ` Daniel P. Berrangé [this message]
2022-03-14 19:18 ` Richard Henderson
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=Yi+RROpNYGqbwdyp@redhat.com \
--to=berrange@redhat.com \
--cc=danielhb413@gmail.com \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=raj.khem@gmail.com \
--cc=richard.henderson@linaro.org \
/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).