From: Nina Schotterl-Glausch <Nina.Schoetterl-Glausch@ibm.com>
To: "shalini@linux.ibm.com" <shalini@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
"qemu-s390x@nongnu.org" <qemu-s390x@nongnu.org>
Cc: "brueckner@linux.ibm.com" <brueckner@linux.ibm.com>,
"Daniel Berrangé" <berrange@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [PATCH v5 2/3] hw/s390x: add Control-Program Identification to QOM
Date: Thu, 5 Jun 2025 13:16:12 +0000 [thread overview]
Message-ID: <3b95b9ad476e7ea1dd2afb95813f78a7680e7688.camel@ibm.com> (raw)
In-Reply-To: <581bb44f-6549-44cc-9466-ef4172fe6ddc@redhat.com>
On Thu, 2025-06-05 at 13:56 +0200, Thomas Huth wrote:
> On 05/06/2025 10.34, Nina Schoetterl-Glausch wrote:
> > On Tue, 2025-06-03 at 15:56 +0200, Shalini Chellathurai Saroja wrote:
> > > Add Control-Program Identification (CPI) data to the QEMU Object
> > > Model (QOM), along with the timestamp in which the data was received
> > > as shown below.
> >
> > [...]
> > >
> > > Signed-off-by: Shalini Chellathurai Saroja <shalini@linux.ibm.com>
> > > ---
> > > hw/s390x/sclpcpi.c | 47 +++++++++++++++++++++++++
> > > include/hw/s390x/event-facility.h | 5 +++
> > > qapi/machine.json | 58 +++++++++++++++++++++++++++++++
> > > 3 files changed, 110 insertions(+)
> > >
> > > diff --git a/hw/s390x/sclpcpi.c b/hw/s390x/sclpcpi.c
> > > index 935fa87acd..ec711e2291 100644
> > > --- a/hw/s390x/sclpcpi.c
> > > +++ b/hw/s390x/sclpcpi.c
> > > @@ -15,7 +15,9 @@
> > > */
> >
> > [...]
> > >
> > > +static void cpi_init(Object *obj)
> > > +{
> > > + SCLPEventCPI *e = SCLP_EVENT_CPI(obj);
> > > +
> > > + object_property_add_str(obj, "system_type", get_system_type, NULL);
> > > + object_property_add_str(obj, "system_name", get_system_name, NULL);
> > > + object_property_add_str(obj, "sysplex_name", get_sysplex_name, NULL);
> > > + object_property_add_uint64_ptr(obj, "system_level", &(e->system_level),
> > > + OBJ_PROP_FLAG_READ);
> > > + object_property_add_uint64_ptr(obj, "timestamp", &(e->timestamp),
> > > + OBJ_PROP_FLAG_READ);
> > > +}
> >
> > I think it would be cleaner if those were class properties.
> > You could use object_class_property_add_str in cpi_class_init,
> > but I think it'd be nice to use DEFINE_PROP_(STR|UINT64) and
> > device_class_set_props.
>
> For "normal" properties I'd say "yes" ... but in this case, this would also
> allow the user to set the properties from the host side - which would be a
> little bit weird? So I think it might be cleaner to keep it this way here
> without the "setter" functions? WDYT?
Oh, yeah I didn't consider this.
Still, object_class_property_add_str would be better I think, all instances
of the class should have these properties.
[...]
--
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht Stuttgart, HRB 243294
next prev parent reply other threads:[~2025-06-05 14:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-03 13:56 [PATCH v5 0/3] Add SCLP event type CPI Shalini Chellathurai Saroja
2025-06-03 13:56 ` [PATCH v5 1/3] hw/s390x: add " Shalini Chellathurai Saroja
2025-06-05 8:45 ` Nina Schoetterl-Glausch
2025-06-03 13:56 ` [PATCH v5 2/3] hw/s390x: add Control-Program Identification to QOM Shalini Chellathurai Saroja
2025-06-05 8:34 ` Nina Schoetterl-Glausch
2025-06-05 11:56 ` Thomas Huth
2025-06-05 12:03 ` Thomas Huth
2025-06-05 13:19 ` Nina Schoetterl-Glausch
2025-06-16 7:21 ` Shalini Chellathurai Saroja
2025-06-05 13:16 ` Nina Schotterl-Glausch [this message]
2025-06-16 7:14 ` Shalini Chellathurai Saroja
2025-06-06 9:34 ` Shalini Chellathurai Saroja
2025-06-13 9:59 ` Thomas Huth
2025-06-13 11:37 ` Shalini Chellathurai Saroja
2025-06-03 13:56 ` [PATCH v5 3/3] hw/s390x: support migration of CPI data Shalini Chellathurai Saroja
2025-06-05 12:04 ` Thomas Huth
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=3b95b9ad476e7ea1dd2afb95813f78a7680e7688.camel@ibm.com \
--to=nina.schoetterl-glausch@ibm.com \
--cc=berrange@redhat.com \
--cc=brueckner@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=shalini@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).