From: Andreas Schwab <schwab@suse.de>
To: Helge Deller <deller@gmx.de>
Cc: qemu-devel@nongnu.org
Subject: Re: Generic way to detect qemu linux-user emulation
Date: Tue, 18 Mar 2025 12:10:56 +0100 [thread overview]
Message-ID: <mvmr02uh9vj.fsf@suse.de> (raw)
In-Reply-To: <ff0cde0c-67d7-4fc3-8996-ad0e8645deed@gmx.de> (Helge Deller's message of "Tue, 18 Mar 2025 11:36:03 +0100")
On Mär 18 2025, Helge Deller wrote:
> My current (unreliable) way to detect it is using uname.
> The kernel string and arch name don't match:
>
> (sid_hppa)root@paq:/# uname -a
> Linux paq 6.1.0-31-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.128-1 (2025-02-07) parisc GNU/Linux
>
> (sid_hppa)root@paq:/# uname -r
> 6.1.0-31-amd64
>
> (sid_hppa)root@paq:/# uname -m
> parisc
>
> This is a qemu-linux-user parisc(hppa) emulation running on x86-64.
That is highly distribution specific, by default the release part does
not contain anything arch specific.
For riscv the most reliable way is to look for "uarch *: qemu" in
/proc/cpuinfo.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2025-03-18 11:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-18 10:18 Generic way to detect qemu linux-user emulation Andreas Schwab
2025-03-18 10:36 ` Helge Deller
2025-03-18 10:45 ` Helge Deller
2025-03-18 10:53 ` Peter Maydell
2025-03-18 11:58 ` Daniel P. Berrangé
2025-03-18 12:34 ` Andreas Schwab
2025-03-18 12:43 ` Daniel P. Berrangé
2025-03-18 13:06 ` Peter Maydell
2025-03-18 13:54 ` Daniel P. Berrangé
2025-03-18 14:17 ` Andreas Schwab
2025-03-18 17:32 ` Daniel P. Berrangé
2025-03-18 15:04 ` Peter Maydell
2025-03-18 17:08 ` Peter Maydell
2025-03-18 17:18 ` Daniel P. Berrangé
2025-03-18 17:48 ` Peter Maydell
2026-03-25 17:08 ` Florian Weimer
2025-03-18 11:10 ` Andreas Schwab [this message]
2026-03-25 14:51 ` Lawrence Hunter
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=mvmr02uh9vj.fsf@suse.de \
--to=schwab@suse.de \
--cc=deller@gmx.de \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.