From: Willy Tarreau <w@1wt.eu>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org,
Ammar Faizi <ammarfaizi2@gnuweeb.org>
Subject: Re: [PATCH 0/2] selftests/nolibc: small simplification of test development phase
Date: Mon, 23 Jan 2023 18:17:12 +0100 [thread overview]
Message-ID: <20230123171712.GA13172@1wt.eu> (raw)
In-Reply-To: <20230123164721.GO2948950@paulmck-ThinkPad-P17-Gen-1>
Hello Paul,
On Mon, Jan 23, 2023 at 08:47:21AM -0800, Paul E. McKenney wrote:
> And building from sources proved to be reasonably easy, so the test
> now passes for me. My initial thought of putting qemu-x86_64 into
> my ~/bin directory fails the sudo test, but putting it into /usr/bin
> works fine.
Great!
> Thank you for the hints!
>
> Should I add a sentence to the commit log noting the potential need to
> build qemu from the git repo and to install qemu-x86_64, give or take
> what architecture one is running?
Well, I've always had all the variants for all supported archs and
didn't know that sometimes only part of them could be installed.
I've used and tested qemu-{i386,x86_64,arm,aarch64,mips,s390x,riscv64}
with this with success, and all of them are built by default for me.
Thus I'm not seeing a good reason for making a special case of x86_64.
Or maybe I'm missing the point ?
Thanks,
Willy
next prev parent reply other threads:[~2023-01-23 17:18 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-21 8:53 [PATCH 0/2] selftests/nolibc: small simplification of test development phase Willy Tarreau
2023-01-21 8:53 ` [PATCH 1/2] selftests/nolibc: support "x86_64" for arch name Willy Tarreau
2023-01-21 8:53 ` [PATCH 2/2] selftests/nolibc: add a "run-user" target to test the program in user land Willy Tarreau
2023-01-21 20:00 ` [PATCH 0/2] selftests/nolibc: small simplification of test development phase Paul E. McKenney
2023-01-21 21:34 ` Willy Tarreau
2023-01-23 16:47 ` Paul E. McKenney
2023-01-23 17:17 ` Willy Tarreau [this message]
2023-01-23 17:34 ` Paul E. McKenney
2023-01-23 16:57 ` Ammar Faizi
2023-01-23 17:09 ` Paul E. McKenney
2023-01-23 17:20 ` Willy Tarreau
2023-01-23 17:31 ` Ammar Faizi
2023-01-23 17:37 ` Willy Tarreau
2023-01-23 17:40 ` Ammar Faizi
2023-01-23 17:40 ` Paul E. McKenney
2023-01-23 19:01 ` Ammar Faizi
2023-01-23 19:12 ` Paul E. McKenney
2023-01-23 19:12 ` Willy Tarreau
2023-01-23 19:25 ` Paul E. McKenney
2023-01-23 17:34 ` Ammar Faizi
2023-01-23 17:52 ` Paul E. McKenney
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=20230123171712.GA13172@1wt.eu \
--to=w@1wt.eu \
--cc=ammarfaizi2@gnuweeb.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=shuah@kernel.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