From: Peter Maydell <peter.maydell@linaro.org>
To: Claudio Fontana <cfontana@suse.de>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
qemu-arm <qemu-arm@nongnu.org>,
qemu-devel <qemu-devel@nongnu.org>,
"Eduardo Habkost" <ehabkost@redhat.com>
Subject: Re: arm: "max" CPU class hierarchy changes possible?
Date: Thu, 11 Mar 2021 15:02:22 +0000 [thread overview]
Message-ID: <CAFEAcA8T+u6QG9PQWs40PTSZ86SEeLQrciT8WHxFyH3UVbipiA@mail.gmail.com> (raw)
In-Reply-To: <11e9d3bb-c94c-4ad7-35b0-b698376c5e00@suse.de>
On Thu, 11 Mar 2021 at 14:27, Claudio Fontana <cfontana@suse.de> wrote:
> the "max" cpu in x86 and s390 is a class,
>
> and then "host" has "max" as parent.
>
> This would be a convenient setup for ARM too, as it would allow to put common code between kvm and tcg in the "max" class,
> and allow "host" to specialize the behavior for KVM (and in the future HVF probably).
>
> Would changing the class hierarchy this way be acceptable, cause any problems?
It's not clear to me why 'host' would be a subtype of 'max':
that doesn't seem like an obvious relationship.
thanks
-- PMM
next prev parent reply other threads:[~2021-03-11 15:52 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 14:27 arm: "max" CPU class hierarchy changes possible? Claudio Fontana
2021-03-11 15:02 ` Peter Maydell [this message]
2021-03-11 15:21 ` Claudio Fontana
2021-03-11 16:02 ` Peter Maydell
2021-03-11 16:18 ` Paolo Bonzini
2021-03-11 17:16 ` Claudio Fontana
2021-03-11 17:35 ` Eduardo Habkost
2021-03-11 18:33 ` Peter Maydell
2021-03-11 19:10 ` Andrew Jones
2021-03-18 11:06 ` arm_cpu_post_init (Was: Re: arm: "max" CPU class hierarchy changes possible?) Claudio Fontana
2021-03-18 11:32 ` Claudio Fontana
2021-03-18 12:08 ` Andrew Jones
2021-03-18 12:42 ` Claudio Fontana
2021-03-18 12:59 ` Andrew Jones
2021-03-18 13:10 ` Eduardo Habkost
2021-03-19 8:19 ` Claudio Fontana
2021-03-19 8:23 ` Claudio Fontana
2021-03-19 8:33 ` Claudio Fontana
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=CAFEAcA8T+u6QG9PQWs40PTSZ86SEeLQrciT8WHxFyH3UVbipiA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=cfontana@suse.de \
--cc=ehabkost@redhat.com \
--cc=f4bug@amsat.org \
--cc=pbonzini@redhat.com \
--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).