From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Shalini Chellathurai Saroja <shalini@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>
Cc: qemu-s390x mailing list <qemu-s390x@nongnu.org>,
Thomas Huth <thuth@redhat.com>,
Daniel Berrange <berrange@redhat.com>,
qemu-devel mailing list <qemu-devel@nongnu.org>
Subject: Re: [PATCH v4 1/4] hw/s390x: add SCLP event type CPI
Date: Tue, 06 May 2025 08:48:35 +0200 [thread overview]
Message-ID: <db6dbf5b1baf3a6ada04168ecf9fde24890cc1c1.camel@linux.ibm.com> (raw)
In-Reply-To: <ad66ac925ff301a945ac1f56fc1d31cc@linux.ibm.com>
On Mon, 2025-05-05 at 08:55 +0200, Shalini Chellathurai Saroja wrote:
> On 2025-04-28 11:22, Janis Schoetterl-Glausch wrote:
> > On Thu, 2025-04-10 at 17:09 +0200, Shalini Chellathurai Saroja wrote:
> > > Implement the Service-Call Logical Processor (SCLP) event
> > > type Control-Program Identification (CPI) in QEMU. This
> > > event is used to send CPI identifiers from the guest to the
> > > host. The CPI identifiers are: system type, system name,
> > > system level and sysplex name.
> > >
> > > System type: operating system of the guest (e.g. "LINUX").
> > > System name: user configurable name of the guest (e.g. "TESTVM").
> > > System level: distribution and kernel version, if the system type is
> > > Linux
> > > (e.g. 0x50e00).
> > > Sysplex name: name of the cluster which the guest belongs to (if any)
> > > (e.g. "PLEX").
> > >
> > > Signed-off-by: Shalini Chellathurai Saroja <shalini@linux.ibm.com>
> > > Reviewed-by: Thomas Huth <thuth@redhat.com>
> > > ---
> > > hw/s390x/event-facility.c | 2 +
> > > hw/s390x/meson.build | 1 +
> > > hw/s390x/s390-virtio-ccw.c | 14 +++++
> > > hw/s390x/sclpcpi.c | 92
> > > +++++++++++++++++++++++++++++++
> > > include/hw/s390x/event-facility.h | 13 +++++
> > > 5 files changed, 122 insertions(+)
> > > create mode 100644 hw/s390x/sclpcpi.c
> > >
> > > diff --git a/hw/s390x/event-facility.c b/hw/s390x/event-facility.c
> > > index 2b0332c20e..60237b8581 100644
> > > --- a/hw/s390x/event-facility.c
> > > +++ b/hw/s390x/event-facility.c
[...]
> It is possible to add the identifiers directly as the properties of
> sclpcpi (eg. system type as shown below) and remove the
> control-program-id.
This is what I meant, drop it from qom.
>
> virsh # qemu-monitor-command vm --pretty
> '{"execute":"qom-list","arguments": {"path":
> "/machine/sclp/s390-sclp-event-facility/sclpcpi"}}'
> {
> "return": [
> {
> "name": "type",
> "type": "string"
> },
> {
> "name": "parent_bus",
> "type": "link<bus>"
> },
> {
> "name": "realized",
> "type": "bool"
> },
> {
> "name": "hotplugged",
> "type": "bool"
> },
> {
> "name": "hotpluggable",
> "type": "bool"
> },
> {
> "name": "system_type",
> "type": "string"
> },
> {
> "name": "control-program-id",
> "type": "S390ControlProgramId"
> }
> ],
> "id": "libvirt-16"
> }
>
> virsh # qemu-monitor-command vm --pretty '{"execute":"qom-get",
> "arguments":{"path":"/machine/sclp/s390-sclp-event-facility/sclpcpi",
> "property":"system_type"}}'
> {
> "return": "LINUX ",
> "id": "libvirt-17"
> }
>
> However, Hendrik Brückner suggested to group the identifiers together
> during the initial discussion of this line item. So, I would prefer to
They are grouped together under "sclpcpi", no?
> leave this as it is. Please let me know if you still think otherwise.
I don't have a strong opinion on this, just wanted to mention it and see what other people say.
>
> > > +}
> >
> > [...]
> >
> > > diff --git a/include/hw/s390x/event-facility.h
> > > b/include/hw/s390x/event-facility.h
> > > index ff874e792d..ef469e62ae 100644
> > > --- a/include/hw/s390x/event-facility.h
> > > +++ b/include/hw/s390x/event-facility.h
> >
> > [...]
> > I.
> > > +struct SCLPEventCPI {
> > > + DeviceState qdev;
> > > + SCLPEvent event;
> >
> > I think you should just inherit from SCLPEvent, which in turn inherits
> > from DeviceState.
> > So without the qdev.
> >
>
> Ok, I will do so. Thank you very much for the review.
>
> > > +};
> > > +
> > > #define TYPE_SCLP_EVENT_FACILITY "s390-sclp-event-facility"
> > > typedef struct SCLPEventFacility SCLPEventFacility;
> > > typedef struct SCLPEventFacilityClass SCLPEventFacilityClass;
>
--
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-05-06 6:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-05 6:55 [PATCH v4 1/4] hw/s390x: add SCLP event type CPI Shalini Chellathurai Saroja
2025-05-06 6:48 ` Nina Schoetterl-Glausch [this message]
2025-05-06 7:48 ` Thomas Huth
2025-05-06 12:16 ` Shalini Chellathurai Saroja
2025-05-23 12:07 ` Hendrik Brueckner
2025-05-28 12:11 ` Shalini Chellathurai Saroja
-- strict thread matches above, loose matches on Subject: below --
2025-04-10 15:09 [PATCH v4 0/4] Add " Shalini Chellathurai Saroja
2025-04-10 15:09 ` [PATCH v4 1/4] hw/s390x: add " Shalini Chellathurai Saroja
2025-04-28 9:22 ` Janis Schoetterl-Glausch
2025-04-29 9:20 ` Nina Schoetterl-Glausch
2025-05-05 6:58 ` Shalini Chellathurai Saroja
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=db6dbf5b1baf3a6ada04168ecf9fde24890cc1c1.camel@linux.ibm.com \
--to=nsg@linux.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).