qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>, shalini <shalini@imap.linux.ibm.com>
Cc: Shalini Chellathurai Saroja <shalini@linux.ibm.com>,
	qemu-s390x mailing list <qemu-s390x@nongnu.org>,
	qemu-devel mailing list <qemu-devel@nongnu.org>,
	Hendrik Brueckner <brueckner@linux.ibm.com>
Subject: Re: [PATCH qemu v2 1/3] hw/s390x: add CPI identifiers to QOM
Date: Thu, 06 Mar 2025 16:44:33 +0100	[thread overview]
Message-ID: <98ab6ad416f0dcf7d1beb5105cace9ca46ad3c84.camel@linux.ibm.com> (raw)
In-Reply-To: <f64b5ce4-8843-4d92-af97-24160f687698@redhat.com>

On Thu, 2025-03-06 at 15:55 +0100, Thomas Huth wrote:
> On 06/03/2025 13.23, shalini wrote:
> > On 2025-03-05 16:56, Thomas Huth wrote:
> > > On 24/02/2025 13.04, Shalini Chellathurai Saroja wrote:
> > > > Add Control-Program Identification (CPI) to the QEMU Object
> > > > Model (QOM). The CPI identifiers provide information about
> > > > the guest operating system. The CPI identifiers are:
> > > > system type, system name, system level and sysplex name.
> > > > 
> > > > The system type provides the OS type of the guest (e.g. LINUX).
> > > > The system name provides the name of the guest (e.g. TESTVM).
> > > > The system level provides the distribution and kernel version
> > > > of the guest OS (e.g. 0x50e00).
> > > > The sysplex name provides the sysplex name of the guest
> > > > (e.g. SYSPLEX).
> > > > 
> > > > Signed-off-by: Shalini Chellathurai Saroja <shalini@linux.ibm.com>
> > > > ---
> > > >   hw/s390x/s390-virtio-ccw.c         | 29 +++++++++++++++++++++++++++++
> > > >   include/hw/s390x/s390-virtio-ccw.h |  8 ++++++++
> > > >   qapi/machine.json                  | 24 ++++++++++++++++++++++++
> > > >   3 files changed, 61 insertions(+)
> > > > 
> > > > diff --git a/hw/s390x/s390-virtio-ccw.c b/hw/s390x/s390-virtio-ccw.c
> > > > index 51ae0c133d..13ea8db1b0 100644
> > > > --- a/hw/s390x/s390-virtio-ccw.c
> > > > +++ b/hw/s390x/s390-virtio-ccw.c
> > > > @@ -50,6 +50,7 @@

[...]

> > > > +##
> > > > +{ 'struct': 'S390ControlProgramId', 'data': {
> > > > +     'system-type': 'str',
> > > > +     'system-name': 'str',
> > > > +     'system-level': 'str',
> > > 
> > > Not sure, but would it make sense to use a number for the system-level
> > > instead? At least it's a number in ControlProgramId, not a string.
> > > 
> > 
> > The system-level, when interpreted as an int provides the output below
> > 
> > 'system-level': 74872343805430528
> > 
> > But the desired output below is obtained only when interpreted as a str. 
> > please refer https://www.ibm.com/docs/en/linux-on-systems? 
> > topic=identification-system-level for details on system-level. I will also 
> > document this in the description of system-level as suggested by Daniel. 
> > Thank you.
> > 
> > 'system-level': '0x10a000000060b00'
> 
> Well, the idea of QOM/QAPI is: It's an *API* for machines, not meant for 
> direct consumption by the end user. So passing an integer as a string is not 
> the right way here. For the user, you'd require some upper level instead 
> that renders the integer in the right shape for the user. So please don't 
> use a string for this at the QOM/QAPI level.

In a sense the system level is a bitfield.
So this could become a struct

{
	'hypervisor-use' : true,
	'distribution-id': 3,	// or an enum?
	'distribution-version-major: 24,
	...
}

Not sure how to handle the 3 undefined bits in the highest byte.

> 
>   Thanks,
>    Thomas
> 

-- 
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


  reply	other threads:[~2025-03-06 15:46 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-24 12:04 [PATCH qemu v2 1/3] hw/s390x: add CPI identifiers to QOM Shalini Chellathurai Saroja
2025-02-24 12:04 ` [PATCH qemu v2 2/3] hw/s390x: add SCLP event type CPI Shalini Chellathurai Saroja
2025-03-05 18:04   ` Thomas Huth
2025-03-05 19:00     ` Nina Schoetterl-Glausch
2025-03-06  8:07       ` shalini
2025-03-06  8:04     ` shalini
2025-02-24 12:04 ` [PATCH qemu v2 3/3] hw/s390x: support migration of CPI values Shalini Chellathurai Saroja
2025-03-05 18:33   ` Thomas Huth
2025-03-06 14:10     ` shalini
2025-03-06 15:08       ` Thomas Huth
2025-03-07  8:04         ` Shalini Chellathurai Saroja
2025-03-07 15:29     ` Shalini Chellathurai Saroja
2025-03-05 15:56 ` [PATCH qemu v2 1/3] hw/s390x: add CPI identifiers to QOM Thomas Huth
2025-03-06 12:23   ` shalini
2025-03-06 14:55     ` Thomas Huth
2025-03-06 15:44       ` Nina Schoetterl-Glausch [this message]
2025-03-06 16:05         ` Daniel P. Berrangé
2025-03-10 15:16           ` Shalini Chellathurai Saroja
2025-03-05 16:06 ` Daniel P. Berrangé
2025-03-06 13:55   ` shalini
2025-03-06 15:06     ` Daniel P. Berrangé
2025-03-06 15:36       ` Nina Schoetterl-Glausch
2025-03-07 15:22       ` Shalini Chellathurai Saroja
2025-03-05 18:05 ` Thomas Huth
2025-03-06 13:57   ` shalini

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=98ab6ad416f0dcf7d1beb5105cace9ca46ad3c84.camel@linux.ibm.com \
    --to=nsg@linux.ibm.com \
    --cc=brueckner@linux.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=shalini@imap.linux.ibm.com \
    --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).