From: Palmer Dabbelt <palmer@rivosinc.com>
To: philipp.tomsich@vrull.eu, dj@redhat.com
Cc: Vineet Gupta <vineetg@rivosinc.com>,
Darius Rad <darius@bluespec.com>,
Alistair Francis <Alistair.Francis@wdc.com>,
vincent.chen@sifive.com, christoph.muellner@vrull.eu,
libc-alpha@sourceware.org, sw-dev@groups.riscv.org
Subject: Re: riscv glibc testing
Date: Fri, 11 Nov 2022 12:46:01 -0800 (PST) [thread overview]
Message-ID: <mhng-67def9be-3fdf-4454-a186-ace9e215583b@palmer-ri-x1c9a> (raw)
In-Reply-To: <CAAeLtUCp5anxZSC4BjZYQNPUG-pq_74eWpYWHXWYAzr+fR3b6A@mail.gmail.com>
On Fri, 11 Nov 2022 11:51:21 PST (-0800), philipp.tomsich@vrull.eu wrote:
> Vineet,
>
> We run all testing using qemu userland through binfmt_misc by
> replacing the system-installed qemu with our own (containing the
> latest extensions).
> This supports even the strangest cases (such as fork + exec that
> alternates host and target binaries): e.g., even the test-workload of
> perlbench_r is no problem.
THat's OK for the GCC and binutils test suites, but last I checked
QEMU's user-mode emulation couldn't handle the glibc test suite and
wasn't accepted as a target for saying "this patch passes the tests".
It's kind of a bummer because it makes running the glibc test suite
without real hardware a lot more of a headache, but I think it's just
the nature of the beast here: the glibc test suite exercises a lot of
edge case behavior in the Linux uABI, trying to get that all matched
perfectly in QEMU would be a lot of work (and IIUC come with some
performance issues).
I don't think any of that has changed, but it's not really a
RISC-V-specific problem so one of the global maintainers would know for
sure. I know DJ's been doing a lot of work on the patchwork testing
stuff, so it's entirely possible something's changed?
> Philipp.
>
>
> On Fri, 11 Nov 2022 at 20:48, Vineet Gupta <vineetg@rivosinc.com> wrote:
>>
>> Hi,
>>
>> Trying to understand how folks working on riscv glibc run the testsuite.
>>
>> One could run native on Unmatched (but doesn't allow testing new
>> extensions) or native on qemu with linux (but that will likely be too
>> slow) specially the building part.
>>
>> My preferred solution would be to avoid linux altogether, do a host
>> cross-build and test with User mode qemu. And then wire it into
>> riscv-gnu-toolchain [1] just like it currently tests gcc dejagnu.
>> However glibc cross testing from my prior ARC work required linux+ssh etc.
>>
>> This email is to see if someone has such as setup already.
>>
>> Thx,
>> -Vineet
>>
>> [1] https://github.com/riscv-collab/riscv-gnu-toolchain
next prev parent reply other threads:[~2022-11-11 20:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 19:48 Vineet Gupta
2022-11-11 19:51 ` Philipp Tomsich
2022-11-11 20:46 ` Palmer Dabbelt [this message]
2022-11-14 19:41 ` DJ Delorie
2022-11-11 20:46 ` Christoph Müllner
2022-11-11 21:14 ` Vineet Gupta
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=mhng-67def9be-3fdf-4454-a186-ace9e215583b@palmer-ri-x1c9a \
--to=palmer@rivosinc.com \
--cc=Alistair.Francis@wdc.com \
--cc=christoph.muellner@vrull.eu \
--cc=darius@bluespec.com \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=philipp.tomsich@vrull.eu \
--cc=sw-dev@groups.riscv.org \
--cc=vincent.chen@sifive.com \
--cc=vineetg@rivosinc.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 read-only IMAP folder(s) and NNTP newsgroup(s).