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 2/5] hw/vfio/ap: notification handler for AP config changed event
Date: Fri, 7 Mar 2025 06:34:51 -0500 [thread overview]
Message-ID: <4d1188c1-c48c-4c37-9a67-623875988b9e@linux.ibm.com> (raw)
In-Reply-To: <20250204170759.36540-3-rreyes@linux.ibm.com>
On 2/4/25 12:07 PM, Rorie Reyes wrote:
> Register an event notifier handler to process AP configuration
> change events by queuing the event and generating a CRW to let
> the guest know its AP configuration has changed
>
> Signed-off-by: Rorie Reyes <rreyes@linux.ibm.com>
> ---
> hw/vfio/ap.c | 29 +++++++++++++++++++++++++++++
> 1 file changed, 29 insertions(+)
>
> diff --git a/hw/vfio/ap.c b/hw/vfio/ap.c
> index 30b08ad375..a2b3735349 100644
> --- a/hw/vfio/ap.c
> +++ b/hw/vfio/ap.c
> @@ -18,6 +18,7 @@
> #include "hw/vfio/vfio-common.h"
> #include "system/iommufd.h"
> #include "hw/s390x/ap-device.h"
> +#include "hw/s390x/css.h"
> #include "qemu/error-report.h"
> #include "qemu/event_notifier.h"
> #include "qemu/main-loop.h"
> @@ -37,6 +38,7 @@ struct VFIOAPDevice {
> APDevice apdev;
> VFIODevice vdev;
> EventNotifier req_notifier;
> + EventNotifier cfg_notifier;
> };
>
> OBJECT_DECLARE_SIMPLE_TYPE(VFIOAPDevice, VFIO_AP_DEVICE)
> @@ -70,6 +72,16 @@ static void vfio_ap_req_notifier_handler(void *opaque)
> }
> }
>
> +static void vfio_ap_cfg_chg_notifier_handler(void *opaque)
> +{
> + VFIOAPDevice *vapdev = opaque;
> +
> + if (!event_notifier_test_and_clear(&vapdev->cfg_notifier)) {
> + css_generate_css_crws(0);
In patch 3/5, you move the css_generate_css_crws() function outside
of this if block and replace it with a return here. That is the right thing
to do, but you should do it here in this patch.
> + }
> +
> +}
> +
> static bool vfio_ap_register_irq_notifier(VFIOAPDevice *vapdev,
> unsigned int irq, Error **errp)
> {
> @@ -85,6 +97,10 @@ static bool vfio_ap_register_irq_notifier(VFIOAPDevice *vapdev,
> notifier = &vapdev->req_notifier;
> fd_read = vfio_ap_req_notifier_handler;
> break;
> + case VFIO_AP_CFG_CHG_IRQ_INDEX:
> + notifier = &vapdev->cfg_notifier;
> + fd_read = vfio_ap_cfg_chg_notifier_handler;
> + break;
> default:
> error_setg(errp, "vfio: Unsupported device irq(%d)", irq);
> return false;
> @@ -136,6 +152,9 @@ static void vfio_ap_unregister_irq_notifier(VFIOAPDevice *vapdev,
> case VFIO_AP_REQ_IRQ_INDEX:
> notifier = &vapdev->req_notifier;
> break;
> + case VFIO_AP_CFG_CHG_IRQ_INDEX:
> + notifier = &vapdev->cfg_notifier;
> + break;
> default:
> error_report("vfio: Unsupported device irq(%d)", irq);
> return;
> @@ -175,6 +194,15 @@ static void vfio_ap_realize(DeviceState *dev, Error **errp)
> warn_report_err(err);
> }
>
> + if (!vfio_ap_register_irq_notifier(vapdev, VFIO_AP_CFG_CHG_IRQ_INDEX, &err))
> + {
> + /*
> + * Report this error, but do not make it a failing condition.
> + * Lack of this IRQ in the host does not prevent normal operation.
> + */
> + warn_report_err(err);
> + }
> +
> return;
>
> error:
> @@ -187,6 +215,7 @@ static void vfio_ap_unrealize(DeviceState *dev)
> VFIOAPDevice *vapdev = VFIO_AP_DEVICE(dev);
>
> vfio_ap_unregister_irq_notifier(vapdev, VFIO_AP_REQ_IRQ_INDEX);
> + vfio_ap_unregister_irq_notifier(vapdev, VFIO_AP_CFG_CHG_IRQ_INDEX);
> vfio_detach_device(&vapdev->vdev);
> g_free(vapdev->vdev.name);
> }
next prev parent reply other threads:[~2025-03-07 11:36 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 [this message]
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
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=4d1188c1-c48c-4c37-9a67-623875988b9e@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).