From: Peter Maydell <peter.maydell@linaro.org>
To: Leif Lindholm <leif@nuviainc.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Andrew Jones <drjones@redhat.com>, qemu-arm <qemu-arm@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>,
Rob Herring <robh@kernel.org>
Subject: Re: kvm_target, QEMU_KVM_ARM_TARGET_GENERIC_V8 questions
Date: Mon, 8 Jun 2020 13:42:19 +0100 [thread overview]
Message-ID: <CAFEAcA_V3eqzxDRbn-K3C4EKCsHx5rhcMy3NiZ8Y7gB=C3HzNg@mail.gmail.com> (raw)
In-Reply-To: <20200608120226.GM28566@vanye>
On Mon, 8 Jun 2020 at 13:02, Leif Lindholm <leif@nuviainc.com> wrote:
> On Thu, Jun 04, 2020 at 19:43:06 +0100, Peter Maydell wrote:
> > https://www.kernel.org/doc/Documentation/devicetree/bindings/arm/cpus.yaml
> > is the official list of permitted strings, incidentally.
>
> My feeling is none of the values there are appropriate (arm,armv8
> indicates ARM ltd, but not aarch64 support). I made something up for
> the RFC set. We could always send a patch adding some qemu, or
> generic, target.
arm,armv8 is the generic "for software models" target, which
sounds appropriate enough to me. Anything consuming a dtb
presumably already knows whether it's in AArch64 state. If
you needed to be able to determine that from the device tree
then I think you'd be better off defining a property for it
rather than having some kind of lookup table of "these compat
string values imply 64-bit and these others do not".
However, I've just noticed that when the kernel added this to the
CPU binding list (apparently in passing during the conversion
to yaml) in commit 672951cbd1b70a9ede6f9c6eba4ed6b726d32b03
in 2018, it documented "arm,armv8", whereas the string QEMU uses
when KVM is being used is "arm,arm-v8" with a hyphen (or
"arm,arm-v7" for 32-bit KVM), which is what we've used since
2013. So I guess we need to also add the with-a-hyphen version
to the kernel binding documentation.
thanks
-- PMM
prev parent reply other threads:[~2020-06-08 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-04 12:55 kvm_target, QEMU_KVM_ARM_TARGET_GENERIC_V8 questions Leif Lindholm
2020-06-04 13:10 ` Peter Maydell
2020-06-04 13:10 ` Peter Maydell
2020-06-04 13:32 ` Andrew Jones
2020-06-04 13:32 ` Andrew Jones
2020-06-04 13:37 ` Peter Maydell
2020-06-04 13:37 ` Peter Maydell
2020-06-04 15:38 ` Leif Lindholm
2020-06-04 15:38 ` Leif Lindholm
2020-06-04 15:59 ` Peter Maydell
2020-06-04 15:59 ` Peter Maydell
2020-06-04 13:18 ` Andrew Jones
2020-06-04 16:03 ` Leif Lindholm
2020-06-04 16:09 ` Peter Maydell
2020-06-04 16:26 ` Leif Lindholm
2020-06-04 18:43 ` Peter Maydell
2020-06-08 12:02 ` Leif Lindholm
2020-06-08 12:42 ` Peter Maydell [this message]
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='CAFEAcA_V3eqzxDRbn-K3C4EKCsHx5rhcMy3NiZ8Y7gB=C3HzNg@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=drjones@redhat.com \
--cc=leif@nuviainc.com \
--cc=pbonzini@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=robh@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 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.