From: Thomas Huth <thuth@redhat.com>
To: Shalini Chellathurai Saroja <shalini@linux.ibm.com>,
qemu-s390x mailing list <qemu-s390x@nongnu.org>
Cc: Sebastian Mitterle <smitterl@redhat.com>,
qemu-devel mailing list <qemu-devel@nongnu.org>,
Nina Schoetterl-Glausch <nsg@linux.ibm.com>,
Hendrik Brueckner <brueckner@linux.ibm.com>,
Michael Mueller <mimu@linux.ibm.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [PATCH v3 1/2] qapi/machine-s390x: add QAPI event SCLP_CPI_INFO_AVAILABLE
Date: Mon, 20 Oct 2025 18:34:50 +0200 [thread overview]
Message-ID: <747f25fd-aa88-4117-a92c-04769f650b32@redhat.com> (raw)
In-Reply-To: <20251016121708.334133-1-shalini@linux.ibm.com>
On 16/10/2025 14.17, Shalini Chellathurai Saroja wrote:
> Add QAPI event SCLP_CPI_INFO_AVAILABLE to notify the availability
> of Control-Program Identification data in QOM.
>
> Signed-off-by: Shalini Chellathurai Saroja <shalini@linux.ibm.com>
> Suggested-by: Thomas Huth <thuth@redhat.com>
> ---
> hw/s390x/sclpcpi.c | 4 ++++
> qapi/machine-s390x.json | 21 +++++++++++++++++++++
> 2 files changed, 25 insertions(+)
>
> diff --git a/hw/s390x/sclpcpi.c b/hw/s390x/sclpcpi.c
> index 7aa039d510..68fc1b809b 100644
> --- a/hw/s390x/sclpcpi.c
> +++ b/hw/s390x/sclpcpi.c
> @@ -54,6 +54,7 @@
> #include "hw/s390x/event-facility.h"
> #include "hw/s390x/ebcdic.h"
> #include "qapi/qapi-visit-machine.h"
> +#include "qapi/qapi-events-machine-s390x.h"
> #include "migration/vmstate.h"
>
> typedef struct Data {
> @@ -106,6 +107,9 @@ static int write_event_data(SCLPEvent *event, EventBufferHeader *evt_buf_hdr)
> e->timestamp = qemu_clock_get_ns(QEMU_CLOCK_HOST);
>
> cpim->ebh.flags = SCLP_EVENT_BUFFER_ACCEPTED;
> +
> + qapi_event_send_sclp_cpi_info_available();
> +
> return SCLP_RC_NORMAL_COMPLETION;
> }
>
> diff --git a/qapi/machine-s390x.json b/qapi/machine-s390x.json
> index 966dbd61d2..8412668b67 100644
> --- a/qapi/machine-s390x.json
> +++ b/qapi/machine-s390x.json
> @@ -119,3 +119,24 @@
> { 'command': 'query-s390x-cpu-polarization', 'returns': 'CpuPolarizationInfo',
> 'features': [ 'unstable' ]
> }
> +
> +##
> +# @SCLP_CPI_INFO_AVAILABLE:
> +#
> +# Emitted when the Control-Program Identification data is available
> +# in the QOM tree.
> +#
> +# Features:
> +#
> +# @unstable: This event is experimental.
> +#
> +# Since: 10.2
> +#
> +# .. qmp-example::
> +#
> +# <- { "event": "SCLP_CPI_INFO_AVAILABLE",
> +# "timestamp": { "seconds": 1401385907, "microseconds": 422329 } }
> +##
> +{ 'event': 'SCLP_CPI_INFO_AVAILABLE',
> + 'features': [ 'unstable' ]
> +}
Reviewed-by: Thomas Huth <thuth@redhat.com>
next prev parent reply other threads:[~2025-10-20 16:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 12:17 [PATCH v3 1/2] qapi/machine-s390x: add QAPI event SCLP_CPI_INFO_AVAILABLE Shalini Chellathurai Saroja
2025-10-16 12:17 ` [PATCH v3 2/2] tests/functional: add tests for SCLP event CPI Shalini Chellathurai Saroja
2025-10-20 16:36 ` Thomas Huth
2025-10-21 12:52 ` Hendrik Brueckner
2025-10-20 16:34 ` Thomas Huth [this message]
2025-10-21 12:51 ` [PATCH v3 1/2] qapi/machine-s390x: add QAPI event SCLP_CPI_INFO_AVAILABLE Hendrik Brueckner
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=747f25fd-aa88-4117-a92c-04769f650b32@redhat.com \
--to=thuth@redhat.com \
--cc=armbru@redhat.com \
--cc=brueckner@linux.ibm.com \
--cc=mimu@linux.ibm.com \
--cc=nsg@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=shalini@linux.ibm.com \
--cc=smitterl@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).