From: Cornelia Huck <cohuck@redhat.com>
To: Andrew Jones <drjones@redhat.com>
Cc: kvm@vger.kernel.org, nikos.nikoleris@arm.com, alex.bennee@linaro.org
Subject: Re: [PATCH kvm-unit-tests] arm64: TCG: Use max cpu type
Date: Fri, 03 Jun 2022 15:38:08 +0200 [thread overview]
Message-ID: <87sfol98an.fsf@redhat.com> (raw)
In-Reply-To: <20220603131557.onhq5h5tt4f57vfn@gator>
On Fri, Jun 03 2022, Andrew Jones <drjones@redhat.com> wrote:
> On Fri, Jun 03, 2022 at 02:21:10PM +0200, Cornelia Huck wrote:
>> On Fri, Jun 03 2022, Andrew Jones <drjones@redhat.com> wrote:
>>
>> > The max cpu type is a better default cpu type for running tests
>> > with TCG as it provides the maximum possible feature set. Also,
>> > the max cpu type was introduced in QEMU v2.12, so we should be
>> > safe to switch to it at this point.
>> >
>> > There's also a 32-bit arm max cpu type, but we leave the default
>> > as cortex-a15, because compilation requires we specify for which
>> > processor we want to compile and there's no such thing as a 'max'.
>> >
>> > Signed-off-by: Andrew Jones <drjones@redhat.com>
>> > ---
>> > configure | 2 +-
>> > 1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/configure b/configure
>> > index 5b7daac3c6e8..1474dde2c70d 100755
>> > --- a/configure
>> > +++ b/configure
>> > @@ -223,7 +223,7 @@ fi
>> > [ -z "$processor" ] && processor="$arch"
>> >
>> > if [ "$processor" = "arm64" ]; then
>> > - processor="cortex-a57"
>> > + processor="max"
>> > elif [ "$processor" = "arm" ]; then
>> > processor="cortex-a15"
>> > fi
>>
>> This looks correct, but the "processor" usage is confusing, as it seems
>> to cover two different things:
>>
>> - what processor to compile for; this is what configure help claims
>> "processor" is used for, but it only seems to have that effect on
>> 32-bit arm
>> - which cpu model to use for tcg on 32-bit and 64-bit arm (other archs
>> don't seem to care)
>>
>> So, I wonder whether it would be less confusing to drop setting
>> "processor" for arm64, and set the cpu models for tcg in arm/run (if
>> none have been specified)?
>>
>
> Good observation, Conny. So, I should probably leave configure alone,
> cortex-a57 is a reasonable processor to compile for, max is based off
> that.
Yes, it would be reasonable; however, I only see Makefile.arm put it
into CFLAGS, not Makefile.arm64, unless I'm missing something here. But
it doesn't hurt, either.
> Then, I can select max in arm/run for both arm and arm64 tests
> instead of using processor there.
Unless you want to be able to override this via -processor=
explicitly... although I doubt that this is in common use.
next prev parent reply other threads:[~2022-06-03 13:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 11:13 [PATCH kvm-unit-tests] arm64: TCG: Use max cpu type Andrew Jones
2022-06-03 12:21 ` Cornelia Huck
2022-06-03 13:15 ` Andrew Jones
2022-06-03 13:38 ` Cornelia Huck [this message]
2022-06-03 15:10 ` Andrew Jones
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=87sfol98an.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=drjones@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=nikos.nikoleris@arm.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