From: Anthony Krowiak <akrowiak@linux.ibm.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, clg@redhat.com, thuth@redhat.com
Subject: Re: [RFC PATCH v2 3/5] hw/vfio/ap: store object indicating AP config changed in a queue
Date: Fri, 7 Mar 2025 06:46:15 -0500 [thread overview]
Message-ID: <9f2e7a33-9fa7-4391-a3df-8bcee757a222@linux.ibm.com> (raw)
In-Reply-To: <20250204170759.36540-4-rreyes@linux.ibm.com>
On 2/4/25 12:07 PM, Rorie Reyes wrote:
> Creates an object indicating that an AP configuration change event
> has been received and stores it in a queue. These objects will later
> be used to store event information for an AP configuration change
> when the CHSC instruction is intercepted.
>
> Signed-off-by: Rorie Reyes <rreyes@linux.ibm.com>
> ---
> hw/vfio/ap.c | 14 +++++++++++++-
> 1 file changed, 13 insertions(+), 1 deletion(-)
>
> diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
> index a2b3735349..396fcf87de 100644
> --- a/hw/vfio/ap.c
> +++ b/hw/vfio/ap.c
> @@ -41,6 +41,13 @@ struct VFIOAPDevice {
> EventNotifier cfg_notifier;
> };
>
> +typedef struct APConfigChgEvent {
> + QTAILQ_ENTRY(APConfigChgEvent) next;
> +} APConfigChgEvent;
> +
> +QTAILQ_HEAD(, APConfigChgEvent) cfg_chg_events =
> + QTAILQ_HEAD_INITIALIZER(cfg_chg_events);
> +
> OBJECT_DECLARE_SIMPLE_TYPE(VFIOAPDevice, VFIO_AP_DEVICE)
>
> static void vfio_ap_compute_needs_reset(VFIODevice *vdev)
> @@ -75,11 +82,16 @@ static void vfio_ap_req_notifier_handler(void *opaque)
> static void vfio_ap_cfg_chg_notifier_handler(void *opaque)
> {
> VFIOAPDevice *vapdev = opaque;
> + APConfigChgEvent *cfg_chg_event = g_new0(APConfigChgEvent, 1);
>
> if (!event_notifier_test_and_clear(&vapdev->cfg_notifier)) {
> - css_generate_css_crws(0);
> + return;
As I stated in my review of patch 2/5, the change above should have
been done there.
> }
>
> + QTAILQ_INSERT_TAIL(&cfg_chg_events, cfg_chg_event, next);
> +
> + css_generate_css_crws(0);
Ditto.
> +
> }
>
> static bool vfio_ap_register_irq_notifier(VFIOAPDevice *vapdev,
next prev parent reply other threads:[~2025-03-07 11:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 17:07 [RFC PATCH v2 0/5] Report vfio-ap configuration changes Rorie Reyes
2025-02-04 17:07 ` [RFC PATCH v2 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change Rorie Reyes
2025-02-05 8:38 ` Cédric Le Goater
2025-03-10 14:20 ` Rorie Reyes
2025-03-10 14:38 ` Cédric Le Goater
2025-03-10 15:23 ` Rorie Reyes
2025-03-10 14:47 ` Vasily Gorbik
2025-03-10 15:29 ` Rorie Reyes
2025-02-04 17:07 ` [RFC PATCH v2 2/5] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-03-07 11:34 ` Anthony Krowiak
2025-02-04 17:07 ` [RFC PATCH v2 3/5] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-03-07 11:46 ` Anthony Krowiak [this message]
2025-02-04 17:07 ` [RFC PATCH v2 4/5] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-02-04 17:07 ` [RFC PATCH v2 5/5] s390: implementing CHSC SEI for AP config change 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=9f2e7a33-9fa7-4391-a3df-8bcee757a222@linux.ibm.com \
--to=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.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 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).