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: [RFC PATCH v4 0/5] Report vfio-ap configuration changes
Date: Wed, 12 Mar 2025 14:48:37 +0100 [thread overview]
Message-ID: <3137b135-6db6-4c41-929c-2ef4b86d66dc@redhat.com> (raw)
In-Reply-To: <20250311151616.98244-1-rreyes@linux.ibm.com>
On 3/11/25 16:16, Rorie Reyes wrote:
> Changelog:
>
> v4:
> - allocating cfg_chg_event before inserting into the queue
> - calling nt0_have_event in if loop to check if there are any
> elemenets in the queue, then calling QTAILQ_FIRST when the check
> passes
> - moving memset() after the check
>
> v3:
> - changes that were made to patch 3/5 should have been made in
> patch 2/5
>
> v2:
> - removed warnings that weren't needed
> - added unregister function
> - removed whitelines
> - changed variable names for consistency
> - removed rc variable and returning 1 or 0 outright
> - reversed logics for if statements
> - using g_free() instead of free()
> - replaced hardcoded numeric values by defining them with #define
> in the header
>
> --------------------------------------------------------------------------
> This patch series creates and registers a handler that is called when
> userspace is notified by the kernel that a guest's AP configuration has
> changed. The handler in turn notifies the guest that its AP configuration
> has changed. This allows the guest to immediately respond to AP
> configuration changes rather than relying on polling or some other
> inefficient mechanism for detecting config changes.
>
> Rorie Reyes (5):
> linux-headers: NOTFORMERGE - placeholder uapi updates for AP config
> change
> hw/vfio/ap: notification handler for AP config changed event
> hw/vfio/ap: store object indicating AP config changed in a queue
> hw/vfio/ap: Storing event information for an AP configuration change
> event
> s390: implementing CHSC SEI for AP config change
>
> hw/vfio/ap.c | 82 ++++++++++++++++++++++++++++++++++++
> include/hw/s390x/ap-bridge.h | 22 ++++++++++
> linux-headers/linux/vfio.h | 1 +
> target/s390x/ioinst.c | 11 ++++-
> 4 files changed, 114 insertions(+), 2 deletions(-)
Queued 2-5. linux-headers should be updated in the QEMU 10.1 cycle.
Thanks,
C.
prev parent reply other threads:[~2025-03-12 13:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 15:16 [RFC PATCH v4 0/5] Report vfio-ap configuration changes Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 2/5] hw/vfio/ap: notification handler for AP config changed event Rorie Reyes
2025-03-11 15:16 ` [RFC PATCH v4 3/5] hw/vfio/ap: store object indicating AP config changed in a queue Rorie Reyes
2025-03-12 11:24 ` Anthony Krowiak
2025-03-11 15:16 ` [RFC PATCH v4 4/5] hw/vfio/ap: Storing event information for an AP configuration change event Rorie Reyes
2025-03-12 13:14 ` Anthony Krowiak
2025-03-11 15:16 ` [RFC PATCH v4 5/5] s390: implementing CHSC SEI for AP config change Rorie Reyes
2025-03-17 13:41 ` Thomas Huth
2025-03-25 13:47 ` Rorie Reyes
2025-04-10 20:31 ` Rorie Reyes
2025-04-11 6:45 ` Thomas Huth
2025-04-14 14:37 ` Rorie Reyes
2025-04-14 14:54 ` Thomas Huth
2025-04-14 14:57 ` Rorie Reyes
2025-03-12 13:48 ` Cédric Le Goater [this message]
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=3137b135-6db6-4c41-929c-2ef4b86d66dc@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 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).