From: "Cédric Le Goater" <clg@redhat.com>
To: Rorie Reyes <rreyes@linux.ibm.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org
Cc: pbonzini@redhat.com, cohuck@redhat.com, pasic@linux.ibm.com,
jjherne@linux.ibm.com, borntraeger@linux.ibm.com,
alex.williamson@redhat.com, thuth@redhat.com,
akrowiak@linux.ibm.com
Subject: Re: [PATCH v1 4/5] hw/vfio/ap: Storing event information for an AP configuration change event
Date: Fri, 24 Jan 2025 09:43:32 +0100 [thread overview]
Message-ID: <83e92dbd-0ff2-41cd-995d-af55c72c711b@redhat.com> (raw)
In-Reply-To: <20250107184354.91079-5-rreyes@linux.ibm.com>
On 1/7/25 19:43, Rorie Reyes wrote:
> These functions can be invoked by the function that handles interception
> of the CHSC SEI instruction for requests indicating the accessibility of
> one or more adjunct processors has changed.
>
> Signed-off-by: Rorie Reyes <rreyes@linux.ibm.com>
> ---
> hw/vfio/ap.c | 37 ++++++++++++++++++++++++++++++++++++
> include/hw/s390x/ap-bridge.h | 17 +++++++++++++++++
> 2 files changed, 54 insertions(+)
>
> diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
> index 508c6eed7a..9d1e18f100 100644
> --- a/hw/vfio/ap.c
> +++ b/hw/vfio/ap.c
> @@ -94,6 +94,43 @@ static void vfio_ap_cfg_chg_notifier_handler(void *opaque)
> css_generate_css_crws(0);
> }
>
> +int ap_chsc_sei_nt0_get_event(void *res)
> +{
> + APConfigChgEvent *cfg_chg_event = QTAILQ_FIRST(&cfg_chg_events);
> + ChscSeiNt0Res *nt0_res = (ChscSeiNt0Res *)res;
> + memset(nt0_res, 0, sizeof(*nt0_res));
please put the memset after the variables.
> + int rc = 1;
'rc' is not very useful. Why not simply return 0 or 1 ?
> +
> + if (cfg_chg_event) {
I would reverse the logic and return early.
if (! cfg_chg_event) {
return 1;
}
> + QTAILQ_REMOVE(&cfg_chg_events, cfg_chg_event, next);
> + free(cfg_chg_event);
g_free()
> +
> + /*
> + * If there are any AP configuration change events in the queue,
> + * indicate to the caller that there is pending event info in
> + * the response block
> + */
> + if (!QTAILQ_EMPTY(&cfg_chg_events)) {
> + nt0_res->flags |= PENDING_EVENT_INFO_BITMASK;
> + }
> +
> + nt0_res->length = sizeof(ChscSeiNt0Res);
> + nt0_res->code = 1;
> + nt0_res->nt = 0;
> + nt0_res->rs = 5;
> + nt0_res->cc = 3;
The above values are cryptic. Can we have some define possibly ?
> + rc = 0;
> + }
> +
> + return rc;
> +}
> +
> +int ap_chsc_sei_nt0_have_event(void)
> +{
> + return !QTAILQ_EMPTY(&cfg_chg_events);
> +}
Why not use this routine in ap_chsc_sei_nt0_get_event() too ?
Thanks,
C.
> static bool vfio_ap_register_irq_notifier(VFIOAPDevice *vapdev,
> unsigned int irq, Error **errp)
> {
> diff --git a/include/hw/s390x/ap-bridge.h b/include/hw/s390x/ap-bridge.h
> index 470e439a98..c9beec3db4 100644
> --- a/include/hw/s390x/ap-bridge.h
> +++ b/include/hw/s390x/ap-bridge.h
> @@ -16,4 +16,21 @@
>
> void s390_init_ap(void);
>
> +typedef struct ChscSeiNt0Res {
> + uint16_t length;
> + uint16_t code;
> + uint8_t reserved1;
> + uint16_t reserved2;
> + uint8_t nt;
> +#define PENDING_EVENT_INFO_BITMASK 0x80;
> + uint8_t flags;
> + uint8_t reserved3;
> + uint8_t rs;
> + uint8_t cc;
> +} QEMU_PACKED ChscSeiNt0Res;
> +
> +int ap_chsc_sei_nt0_get_event(void *res);
> +
> +int ap_chsc_sei_nt0_have_event(void);
> +
> #endif
next prev parent reply other threads:[~2025-01-24 8:44 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-07 18:43 [PATCH v1 0/5] Report vfio-ap configuration changes Rorie Reyes
2025-01-07 18:43 ` [PATCH v1 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change Rorie Reyes
2025-01-08 7:29 ` Cédric Le Goater
2025-01-14 18:51 ` Rorie Reyes
2025-01-14 19:55 ` Eric Farman
2025-01-24 8:49 ` Cédric Le Goater
2025-01-24 14:45 ` Eric Farman
2025-01-07 18:43 ` [PATCH v1 2/5] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-01-08 7:34 ` Cédric Le Goater
2025-01-08 18:58 ` Rorie Reyes
2025-01-15 17:00 ` Anthony Krowiak
2025-01-24 8:31 ` Cédric Le Goater
2025-01-07 18:43 ` [PATCH v1 3/5] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-01-24 8:37 ` Cédric Le Goater
2025-01-27 19:12 ` Anthony Krowiak
2025-02-03 16:50 ` Anthony Krowiak
2025-02-04 13:22 ` Rorie Reyes
2025-01-07 18:43 ` [PATCH v1 4/5] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-01-24 8:43 ` Cédric Le Goater [this message]
2025-01-07 18:43 ` [PATCH v1 5/5] s390: implementing CHSC SEI for AP config change Rorie Reyes
2025-01-07 19:06 ` [PATCH v1 0/5] Report vfio-ap configuration changes Alex Williamson
2025-01-14 16:34 ` Rorie Reyes
2025-02-05 17:38 ` Rorie Reyes
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=83e92dbd-0ff2-41cd-995d-af55c72c711b@redhat.com \
--to=clg@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=jjherne@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rreyes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.