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:37:07 +0100 [thread overview]
Message-ID: <20230123173707.GC13172@1wt.eu> (raw)
In-Reply-To: <Y87EVVt431Wx2zXk@biznet-home.integral.gnuweeb.org>
On Tue, Jan 24, 2023 at 12:31:01AM +0700, Ammar Faizi wrote:
> I figured it out. It turned qemu-user is a different package.
> So I have "qemu-system" installed, but not "qemu-user".
>
> Without building from source, just do this on Ubuntu:
>
> $ sudo apt-get install qemu-user -y
> ...
> Preparing to unpack .../qemu-user_1%3a6.2+dfsg-2ubuntu6.6_amd64.deb ...
> Unpacking qemu-user (1:6.2+dfsg-2ubuntu6.6) ...
> Selecting previously unselected package qemu-user-binfmt.
> Preparing to unpack .../qemu-user-binfmt_1%3a6.2+dfsg-2ubuntu6.6_amd64.deb ...
> Unpacking qemu-user-binfmt (1:6.2+dfsg-2ubuntu6.6) ...
> Setting up qemu-user (1:6.2+dfsg-2ubuntu6.6) ...
> Setting up qemu-user-binfmt (1:6.2+dfsg-2ubuntu6.6) ...
> Processing triggers for man-db (2.10.2-1) ...
>
> $ which qemu-x86_64
> /usr/bin/qemu-x86_64
Ah cool! I looked for something like this on a remote ubuntu system but
failed to figure it out by myself. Do you also have the other archs with
it ?
> $ sudo make run-user
> MKDIR sysroot/x86/include
> make[1]: Entering directory '/home/ammarfaizi2/work/linux.work.cc/tools/include/nolibc'
> make[2]: Entering directory '/home/ammarfaizi2/work/linux.work.cc'
> make[2]: Leaving directory '/home/ammarfaizi2/work/linux.work.cc'
> make[2]: Entering directory '/home/ammarfaizi2/work/linux.work.cc'
> INSTALL /home/ammarfaizi2/work/linux.work.cc/tools/testing/selftests/nolibc/sysroot/sysroot/include
> make[2]: Leaving directory '/home/ammarfaizi2/work/linux.work.cc'
> make[1]: Leaving directory '/home/ammarfaizi2/work/linux.work.cc/tools/include/nolibc'
> CC nolibc-test
> 83 test(s) passed.
Great. And without sudo you should see two of them fail. I intend to
implement geteuid() and condition their result to it, that will be
sufficient for most cases. I'd rather avoid seeing users run test
programs under sudo actually, since they're run on the local system :-/
> Sorry for that. I didn't know that they come from different packages.
> It works fine for me now.
No, don't be sorry, quite the opposite, you taught us something useful!
Thank you!
Willy
next prev parent reply other threads:[~2023-01-23 17:37 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
2023-01-23 17:31 ` Ammar Faizi
2023-01-23 17:37 ` Willy Tarreau [this message]
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=20230123173707.GC13172@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