From: Matthew Rosato <mjrosato@linux.ibm.com>
To: Pierre Morel <pmorel@linux.ibm.com>, qemu-s390x@nongnu.org
Cc: alex.williamson@redhat.com, schnelle@linux.ibm.com,
cohuck@redhat.com, thuth@redhat.com, farman@linux.ibm.com,
richard.henderson@linaro.org, david@redhat.com,
pasic@linux.ibm.com, borntraeger@linux.ibm.com, mst@redhat.com,
pbonzini@redhat.com, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH v7 8/8] s390x/s390-virtio-ccw: add zpcii-disable machine property
Date: Thu, 23 Jun 2022 10:26:19 -0400 [thread overview]
Message-ID: <ae85d880-97c3-20da-8ef1-c06e04ce7b9b@linux.ibm.com> (raw)
In-Reply-To: <5c6bd37d-45b3-026a-aa2c-e9d6c3349cf9@linux.ibm.com>
On 6/23/22 9:50 AM, Pierre Morel wrote:
>
>
> On 6/22/22 17:20, Matthew Rosato wrote:
>> On 6/22/22 4:50 AM, Pierre Morel wrote:
>>>
>>>
>>> On 6/6/22 22:36, Matthew Rosato wrote:
>>>> The zpcii-disable machine property can be used to force-disable the use
>>>> of zPCI interpretation facilities for a VM. By default, this setting
>>>> will be off for machine 7.1 and newer.
>>>>
>>>> Signed-off-by: Matthew Rosato <mjrosato@linux.ibm.com>
>>>> ---
>>>> hw/s390x/s390-pci-kvm.c | 4 +++-
>>>> hw/s390x/s390-virtio-ccw.c | 24 ++++++++++++++++++++++++
>>>> include/hw/s390x/s390-virtio-ccw.h | 1 +
>>>> qemu-options.hx | 8 +++++++-
>>>> util/qemu-config.c | 4 ++++
>>>> 5 files changed, 39 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/hw/s390x/s390-pci-kvm.c b/hw/s390x/s390-pci-kvm.c
>>>> index 9134fe185f..5eb7fd12e2 100644
>>>> --- a/hw/s390x/s390-pci-kvm.c
>>>> +++ b/hw/s390x/s390-pci-kvm.c
>>>> @@ -22,7 +22,9 @@
>>>> bool s390_pci_kvm_interp_allowed(void)
>>>> {
>>>> - return kvm_s390_get_zpci_op() && !s390_is_pv();
>>>> + return (kvm_s390_get_zpci_op() && !s390_is_pv() &&
>>>> + !object_property_get_bool(OBJECT(qdev_get_machine()),
>>>> + "zpcii-disable", NULL));
>>>> }
>>>
>>> Isn't it a duplication of machine_get_zpcii_disable?
>>>
>>
>> No, this will actually trigger machine_get_zpcii_disable -- it was
>> setup as the 'getter' routine in s390_machine_initfn() -- see below:
>
> OK, I did not explain myself correctly:
> I was curious why we do not use directly ms->zpci_disabled and use the
> getter.
>
To do so, we'd have to either call machine_get_zpcii_disable directly
from here or duplicate the work machine_get_zpcii_disable does by
casting the machine to S390CcwMachineState so we could look at
ms->zpcii_disabled. We can't call machine_get_zpcii_disable directly
as-is, it's a static routine in s390-virtio-ccw.c -- making a 'getter'
routine public seems wrong, so we are left with recreating the cast and
looking at ms->zpcii_disabled here; but as far as I can figure the point
is to have a unified interface for querying a machine property value via
object_property_get_*(). Why wouldn't we use that interface?
FWIW, I modeled this after the way we today handle aes-key-wrap in
target/s390x/kvm/kvm.c and loadparm in hw/s390x/ipl.c (albeit we use
object_property_get_str for the latter since it's a different property
type).
> Does not mean it is false. Far from.
> >>
>>> Wouldn't it better go to hw/s390x/kvm/ ?
>>>
>>> There get the MachineState *ms = MACHINE(qdev_get_machine()) and
>>> return the ms->zpcii_disable
>>>
>>> ?
>>>
>>>> int s390_pci_kvm_aif_enable(S390PCIBusDevice *pbdev, ZpciFib *fib,
>>>> bool assist)
>>>> diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
>>>> index cc3097bfee..70229b102b 100644
>>>> --- a/hw/s390x/s390-virtio-ccw.c
>>>> +++ b/hw/s390x/s390-virtio-ccw.c
>>>> @@ -645,6 +645,21 @@ static inline void
>>>> machine_set_dea_key_wrap(Object *obj, bool value,
>>>> ms->dea_key_wrap = value;
>>>> }
>>>> +static inline bool machine_get_zpcii_disable(Object *obj, Error
>>>> **errp)
>>>> +{
>>>> + S390CcwMachineState *ms = S390_CCW_MACHINE(obj);
>>>> +
>>>> + return ms->zpcii_disable;
>>>> +}
>>>> +
>>>> +static inline void machine_set_zpcii_disable(Object *obj, bool value,
>>>> + Error **errp)
>>>> +{
>>>> + S390CcwMachineState *ms = S390_CCW_MACHINE(obj);
>>>> +
>>>> + ms->zpcii_disable = value;
>>>> +}
>>>> +
>>>> static S390CcwMachineClass *current_mc;
>>>> /*
>>>> @@ -740,6 +755,13 @@ static inline void s390_machine_initfn(Object
>>>> *obj)
>>>> "Up to 8 chars in set of [A-Za-z0-9. ] (lower case
>>>> chars converted"
>>>> " to upper case) to pass to machine loader, boot
>>>> manager,"
>>>> " and guest kernel");
>>>> +
>>>> + object_property_add_bool(obj, "zpcii-disable",
>>>> + machine_get_zpcii_disable,
>>
>> ^^ Here.
>
prev parent reply other threads:[~2022-06-23 14:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 20:36 [PATCH v7 0/8] s390x/pci: zPCI interpretation support Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 1/8] Update linux headers Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 2/8] s390x/pci: add routine to get host function handle from CLP info Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 3/8] s390x/pci: enable for load/store intepretation Matthew Rosato
2022-06-22 8:35 ` Pierre Morel
2022-06-22 15:20 ` Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 4/8] s390x/pci: don't fence interpreted devices without MSI-X Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 5/8] s390x/pci: enable adapter event notification for interpreted devices Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 6/8] s390x/pci: let intercept devices have separate PCI groups Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 7/8] s390x/pci: reflect proper maxstbl for groups of interpreted devices Matthew Rosato
2022-06-06 20:36 ` [PATCH v7 8/8] s390x/s390-virtio-ccw: add zpcii-disable machine property Matthew Rosato
2022-06-22 8:50 ` Pierre Morel
2022-06-22 15:20 ` Matthew Rosato
2022-06-23 13:50 ` Pierre Morel
2022-06-23 14:26 ` Matthew Rosato [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=ae85d880-97c3-20da-8ef1-c06e04ce7b9b@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=schnelle@linux.ibm.com \
--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).