From: Nina Schoetterl-Glausch <nsg@linux.ibm.com>
To: Thomas Huth <thuth@redhat.com>,
Shalini Chellathurai Saroja <shalini@linux.ibm.com>,
qemu-s390x mailing list <qemu-s390x@nongnu.org>
Cc: Daniel Berrange <berrange@redhat.com>,
qemu-devel mailing list <qemu-devel@nongnu.org>,
Hendrik Brueckner <brueckner@linux.ibm.com>
Subject: Re: [PATCH v5 2/3] hw/s390x: add Control-Program Identification to QOM
Date: Thu, 05 Jun 2025 15:19:36 +0200 [thread overview]
Message-ID: <64495f006100dfd615009a0862a5e6aab6a697b1.camel@linux.ibm.com> (raw)
In-Reply-To: <00c7e7f0-1c94-4f6f-aa08-5e557bbb91aa@redhat.com>
On Thu, 2025-06-05 at 14:03 +0200, Thomas Huth wrote:
> On 05/06/2025 13.56, 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>
> > > > ---
[...]
>
> PS: FWIW, Markus recently also provided a nice summery about the different
> property types here:
> https://lore.kernel.org/qemu-devel/87o6vfzdig.fsf@pond.sub.org/
Thanks!
> This Property part of qdev isn't actually device-specific. We could
> lift it into Object. But would that be an improvement? I'm not sure;
> QOM is confusing enough as it is.
:D indeed it is.
--
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 13:20 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 [this message]
2025-06-16 7:21 ` Shalini Chellathurai Saroja
2025-06-05 13:16 ` Nina Schotterl-Glausch
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=64495f006100dfd615009a0862a5e6aab6a697b1.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).