public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Krowiak <akrowiak@linux.ibm.com>
To: freude@linux.ibm.com
Cc: Rorie Reyes <rreyes@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, hca@linux.ibm.com, borntraeger@de.ibm.com,
	agordeev@linux.ibm.com, gor@linux.ibm.com, pasic@linux.ibm.com,
	jjherne@linux.ibm.com, alex.williamson@redhat.com
Subject: Re: [PATCH v1] s390/vfio-ap: Signal eventfd when guest AP configuration is changed
Date: Fri, 17 Jan 2025 07:42:04 -0500	[thread overview]
Message-ID: <99bc2df0-ffd2-4aaa-b658-de5ac3a77b40@linux.ibm.com> (raw)
In-Reply-To: <105ff0df576ac86c1cd2edd4e1a6478c@linux.ibm.com>




On 1/17/25 3:30 AM, Harald Freudenberger wrote:
> On 2025-01-16 17:46, Anthony Krowiak wrote:
>>>
>>> Rorie, this is to inform listeners on the host of the guest.
>>> The guest itself already sees this "inside" with uevents triggered
>>> by the AP bus code.
>>>
>>> Do you have a consumer for these events?
>>
>> There is a series of QEMU patches that register a notification 
>> handler for this
>> event. When that handler gets called, it generates and queues a CRW 
>> to the guest
>> indicating there is event information pending which will cause the AP 
>> bus driver
>> to get notified of the AP configuration change via its ap_bus_cfg_chg
>> notifier call.
>>
>> The QEMU series can be seen at:
>> https://lore.kernel.org/qemu-devel/7171c479-5cb4-4748-ba37-da4cf2fac35b@linux.ibm.com/T/ 
>>
>>
>>
>> Kind regards,
>> A Krowiak
>
> Ok, so this way the AP bus of the guest finally get's it's config 
> change callback invoked :-)

Yes, and it happens pretty quickly; at least in the test environment.



  reply	other threads:[~2025-01-17 12:42 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-07 18:36 [PATCH v1] s390/vfio-ap: Signal eventfd when guest AP configuration is changed Rorie Reyes
2025-01-13 16:08 ` Alexander Gordeev
2025-02-05 17:33   ` Rorie Reyes
2025-02-05 17:47     ` Anthony Krowiak
2025-02-06  7:40       ` Alexander Gordeev
2025-02-06 14:12         ` Rorie Reyes
2025-02-11  7:58           ` Alexander Gordeev
2025-02-11 15:02             ` Rorie Reyes
2025-02-11 20:24               ` Anthony Krowiak
2025-02-12 10:55                 ` Vasily Gorbik
2025-01-14  9:03 ` Harald Freudenberger
2025-01-16 16:46   ` Anthony Krowiak
2025-01-17  8:30     ` Harald Freudenberger
2025-01-17 12:42       ` Anthony Krowiak [this message]
2025-01-14 20:05 ` Alex Williamson
2025-01-15 19:35   ` Anthony Krowiak
2025-01-16  0:17     ` Halil Pasic
2025-01-16 15:38       ` Anthony Krowiak
2025-01-16 16:52         ` Alex Williamson
2025-01-16 19:18           ` Halil Pasic
2025-01-17 12:50             ` Anthony Krowiak
2025-01-17 12:55           ` Anthony Krowiak
2025-01-16 19:30         ` Halil Pasic
2025-01-17 12:53           ` Anthony Krowiak

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=99bc2df0-ffd2-4aaa-b658-de5ac3a77b40@linux.ibm.com \
    --to=akrowiak@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=freude@linux.ibm.com \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=jjherne@linux.ibm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=rreyes@linux.ibm.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