From: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>
To: qemu-devel@nongnu.org
Cc: bcain@quicinc.com, tsimpson@quicinc.com
Subject: [PATCH 0/2] Hexagon: improve output for arch version debugging
Date: Thu, 4 May 2023 15:53:10 -0300 [thread overview]
Message-ID: <cover.1683225804.git.quic_mathbern@quicinc.com> (raw)
If we run qemu with an Hexagon binary compiled to an arch version that
is higher than the threshold modeled by qemu, we will get the following
error:
qemu-hexagon: unable to find CPU model 'unknown'
This can be confusing ("Was qemu unable to read the arch version from
this binary? Or did it read but does not know such version?").
And running `qemu-hexagon -cpu help` doesn't help either, as it just
errors out with no output. This patchset tries to improve this process.
https://lore.kernel.org/qemu-devel/cover.1673616964.git.quic_mathbern@quicinc.com/
Matheus Tavares Bernardino (2):
Hexagon: list available CPUs with `-cpu help`
Hexagon: append eflags to unknown cpu model string
linux-user/hexagon/target_elf.h | 7 ++++++-
target/hexagon/cpu.h | 3 +++
target/hexagon/cpu.c | 20 ++++++++++++++++++++
3 files changed, 29 insertions(+), 1 deletion(-)
--
2.37.2
next reply other threads:[~2023-05-04 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 18:53 Matheus Tavares Bernardino [this message]
2023-05-04 18:53 ` [PATCH 1/2] Hexagon: list available CPUs with `-cpu help` Matheus Tavares Bernardino
2023-05-05 18:58 ` Taylor Simpson
2023-05-04 18:53 ` [PATCH 2/2] Hexagon: append eflags to unknown cpu model string Matheus Tavares Bernardino
2023-05-05 18:58 ` Taylor Simpson
2023-05-05 18:59 ` [PATCH 0/2] Hexagon: improve output for arch version debugging Taylor Simpson
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=cover.1683225804.git.quic_mathbern@quicinc.com \
--to=quic_mathbern@quicinc.com \
--cc=bcain@quicinc.com \
--cc=qemu-devel@nongnu.org \
--cc=tsimpson@quicinc.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 NNTP newsgroup(s).