From: Richard Henderson <richard.henderson@linaro.org>
To: Andrew Jones <drjones@redhat.com>
Cc: "peter.maydell@linaro.org" <peter.maydell@linaro.org>,
"qemu-arm@nongnu.org" <qemu-arm@nongnu.org>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"ishii.shuuichir@fujitsu.com" <ishii.shuuichir@fujitsu.com>
Subject: Re: [PATCH v4 1/3] target-arm: Add support for Fujitsu A64FX
Date: Tue, 17 Aug 2021 05:53:34 -1000 [thread overview]
Message-ID: <3846b738-719f-a9a1-a59d-d7f54e71009c@linaro.org> (raw)
In-Reply-To: <20210817153639.o5fxdgmuhjusvyhq@gator.home>
On 8/17/21 5:36 AM, Andrew Jones wrote:
> On Tue, Aug 17, 2021 at 05:23:17AM -1000, Richard Henderson wrote:
>> On 8/17/21 1:56 AM, Andrew Jones wrote:
>>> I guess it's fine. You could easily create a new cpu_arm_set_sve_vq()
>>> which would forbid changing the properties if you wanted to, but then
>>> we need to answer Peter's question in order to see if there's a
>>> precedent for that type of property.
>>
>> I don't see the point in read-only properties. If the user wants to set
>> non-standard values on the command-line, let them. What is most important
>> is getting the correct default from '-cpu a64fx'.
>>
>
> So maybe we should just go ahead and add all sve* properties, but then
> make sure the default vq map is correct.
I think that's the right answer.
Presently we have a kvm_supported variable that's initialized by kvm_arm_sve_get_vls(). I
think we want to rename that variable and provide a version of that function for tcg.
Probably we should have done that before, with a trivial function for -cpu max to set all
bits.
Then eliminate most of the other kvm_enabled() checks in arm_cpu_sve_finalize. I think
the only one we keep is the last, where we verify that the final sve_vq_map matches
kvm_enabled exactly, modulo max_vq.
This should minimize the differences in behaviour between tcg and kvm.
r~
next prev parent reply other threads:[~2021-08-17 15:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 6:04 [PATCH v4 0/3] Add support for Fujitsu A64FX processor Shuuichirou Ishii
2021-08-12 6:04 ` [PATCH v4 1/3] target-arm: Add support for Fujitsu A64FX Shuuichirou Ishii
2021-08-12 9:16 ` Andrew Jones
2021-08-12 9:25 ` Andrew Jones
2021-08-12 9:36 ` Peter Maydell
2021-08-17 6:43 ` ishii.shuuichir
2021-08-17 11:56 ` Andrew Jones
2021-08-17 15:23 ` Richard Henderson
2021-08-17 15:36 ` Andrew Jones
2021-08-17 15:53 ` Richard Henderson [this message]
2021-08-17 16:28 ` Andrew Jones
2021-08-18 8:29 ` ishii.shuuichir
2021-08-18 8:57 ` Andrew Jones
2021-08-19 5:17 ` ishii.shuuichir
2021-08-12 6:04 ` [PATCH v4 2/3] hw/arm/virt: target-arm: Add A64FX processor support to virt machine Shuuichirou Ishii
2021-08-12 6:04 ` [PATCH v4 3/3] tests/arm-cpu-features: Add A64FX processor related tests Shuuichirou Ishii
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=3846b738-719f-a9a1-a59d-d7f54e71009c@linaro.org \
--to=richard.henderson@linaro.org \
--cc=drjones@redhat.com \
--cc=ishii.shuuichir@fujitsu.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--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 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).