[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v1 0/5] Report vfio-ap configuration changes
|
From: |
Alex Williamson |
|
Subject: |
Re: [PATCH v1 0/5] Report vfio-ap configuration changes |
|
Date: |
Tue, 7 Jan 2025 14:06:34 -0500 |
On Tue, 7 Jan 2025 13:43:49 -0500
Rorie Reyes <rreyes@linux.ibm.com> wrote:
> 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.
Why are configuration changes to the device allowed while the device is
in use?
Would a uevent be considered an inefficient mechanism? Why?
Thanks,
Alex
- [PATCH v1 0/5] Report vfio-ap configuration changes, Rorie Reyes, 2025/01/07
- Re: [PATCH v1 0/5] Report vfio-ap configuration changes,
Alex Williamson <=
- [PATCH v1 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change, Rorie Reyes, 2025/01/07
- [PATCH v1 4/5] hw/vfio/ap: Storing event information for an AP configuration change event, Rorie Reyes, 2025/01/07
- [PATCH v1 3/5] hw/vfio/ap: store object indicating AP config changed in a queue, Rorie Reyes, 2025/01/07
- [PATCH v1 5/5] s390: implementing CHSC SEI for AP config change, Rorie Reyes, 2025/01/07
- [PATCH v1 2/5] hw/vfio/ap: notification handler for AP config changed event, Rorie Reyes, 2025/01/07