From: Willy Tarreau <w@1wt.eu>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
linux-kernel@vger.kernel.org, Shuah Khan <shuah@kernel.org>,
linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/2] selftests/nolibc: small simplification of test development phase
Date: Mon, 23 Jan 2023 18:20:16 +0100 [thread overview]
Message-ID: <20230123172016.GB13172@1wt.eu> (raw)
In-Reply-To: <Y868lIin0bLM9HfM@biznet-home.integral.gnuweeb.org>
Hi Ammar,
On Mon, Jan 23, 2023 at 11:57:56PM +0700, Ammar Faizi wrote:
> Is there a way to make it work for the default qemu installation?
> Or maybe it's a mandatory requirement to build qemu from the source?
>
> I use the qemu that comes from Ubuntu apt. I have "qemu-system-x86_64",
> but no "qemu-x86_64". So, something like this...
>
> $ which qemu-x86_64
> $ echo $?
> 1
>
> $ which qemu-system-x86_64
> /usr/bin/qemu-system-x86_64
Ah now I think I understand Paul's question. I didn't know that the
userland version was not always provided. I've always had both side
by side.
> It would be great if we can avoid building qemu from the source. But if
> not, let's go with that.
As Paul indicated, it's really trouble-free and I think I've only done
that since the very first day I started to use QEMU, reason why I probably
never noticed that not everything was packaged.
Then at least to respond to Paul, it could make sense to add a note that
on some distros the userland version might not always be provided and
might require a pretty simple rebuild of QEMU.
Thanks!
Willy
next prev parent reply other threads:[~2023-01-23 17:20 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
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 [this message]
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=20230123172016.GB13172@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