From: David Hildenbrand <david@redhat.com>
To: Thomas Huth <thuth@redhat.com>, Cornelia Huck <cohuck@redhat.com>,
qemu-devel@nongnu.org
Cc: Halil Pasic <pasic@linux.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
qemu-s390x@nongnu.org, Matthew Rosato <mjrosato@linux.ibm.com>
Subject: Re: [PATCH] hw/s390x: Add a more verbose comment about get_machine_class() and the wrappers
Date: Fri, 24 Jan 2020 15:30:14 +0100 [thread overview]
Message-ID: <6fb2e099-1c5b-be8b-1211-8c22f233f596@redhat.com> (raw)
In-Reply-To: <20200123170256.12386-1-thuth@redhat.com>
On 23.01.20 18:02, Thomas Huth wrote:
> While working on the "Enable adapter interruption suppression again"
> recently, I had to discover that the meaning of get_machine_class()
> and the related *_allowed() wrappers is not very obvious. Add a more
> verbose comment here to clarify how these should be used.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> hw/s390x/s390-virtio-ccw.c | 15 ++++++++++++---
> 1 file changed, 12 insertions(+), 3 deletions(-)
>
> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> index e0e28139a2..7fb389f0e5 100644
> --- a/hw/s390x/s390-virtio-ccw.c
> +++ b/hw/s390x/s390-virtio-ccw.c
> @@ -505,6 +505,18 @@ static inline void machine_set_dea_key_wrap(Object *obj, bool value,
>
> static S390CcwMachineClass *current_mc;
>
> +/*
> + * Get the class of the s390-ccw-virtio machine that is currently in use.
> + * Note: libvirt is using the "none" machine to probe for the features of the
> + * host CPU, so in case this is called with the "none" machine, the function
> + * returns the TYPE_S390_CCW_MACHINE base class. In this base class, all the
> + * various "*_allowed" variables are enabled, so that the *_allowed() wrappers
> + * below return the correct default value for the "none" machine.
> + * Attention! Do *not* add additional new wrappers for CPU features (e.g. like
> + * the ri_allowed() wrapper) via this mechanism anymore. CPU features should
> + * be handled via the CPU models, i.e. checking with cpu_model_allowed() during
> + * CPU initialization and s390_has_feat() later should be sufficient.
> + */
> static S390CcwMachineClass *get_machine_class(void)
> {
> if (unlikely(!current_mc)) {
> @@ -521,19 +533,16 @@ static S390CcwMachineClass *get_machine_class(void)
>
> bool ri_allowed(void)
> {
> - /* for "none" machine this results in true */
> return get_machine_class()->ri_allowed;
> }
>
> bool cpu_model_allowed(void)
> {
> - /* for "none" machine this results in true */
> return get_machine_class()->cpu_model_allowed;
> }
>
> bool hpage_1m_allowed(void)
> {
> - /* for "none" machine this results in true */
> return get_machine_class()->hpage_1m_allowed;
> }
>
>
Very helpful, thanks!
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-01-24 14:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 17:02 [PATCH] hw/s390x: Add a more verbose comment about get_machine_class() and the wrappers Thomas Huth
2020-01-23 17:42 ` Cornelia Huck
2020-01-24 8:42 ` Thomas Huth
2020-01-24 14:30 ` David Hildenbrand [this message]
2020-01-24 14:38 ` Cornelia Huck
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=6fb2e099-1c5b-be8b-1211-8c22f233f596@redhat.com \
--to=david@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.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).