qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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: [PATCH v1 3/5] hw/vfio/ap: store object indicating AP config changed in a queue
Date: Mon, 3 Feb 2025 11:50:42 -0500	[thread overview]
Message-ID: <d80b686c-71ee-4a25-82bf-5cf96c43975d@linux.ibm.com> (raw)
In-Reply-To: <20250107184354.91079-4-rreyes@linux.ibm.com>




On 1/7/25 1:43 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>
> Reviewed-by: Anthony Krowiak <akrowiak@linux.ibm.com>
> Tested-by: Anthony Krowiak <akrowiak@linux.ibm.com>
> ---
>   hw/vfio/ap.c | 10 ++++++++++
>   1 file changed, 10 insertions(+)
>
> diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
> index 533cadb2dd..508c6eed7a 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)
> @@ -76,6 +83,9 @@ static void vfio_ap_cfg_chg_notifier_handler(void *opaque)
>   {
>       VFIOAPDevice *vapdev = opaque;
>   
> +    APConfigChgEvent *new_event = g_new0(APConfigChgEvent, 1);
> +
> +    QTAILQ_INSERT_TAIL(&cfg_chg_events, new_event, next);

I didn't notice this before giving my r-b, but I don't think new_event 
should be
inserted into the queue until the 'event_notifier_test_and_clear' below
passes.

>       if (!event_notifier_test_and_clear(&vapdev->cfg_notifier)) {
>           warn_report("Event notifier not initialized");
>           return;



  parent reply	other threads:[~2025-02-03 16:51 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 [this message]
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
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=d80b686c-71ee-4a25-82bf-5cf96c43975d@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).