lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f1af50b3-f966-445d-ab89-3d213f55b93a@linux.ibm.com>
Date: Wed, 5 Feb 2025 12:47:55 -0500
From: Anthony Krowiak <akrowiak@...ux.ibm.com>
To: Rorie Reyes <rreyes@...ux.ibm.com>,
        Alexander Gordeev <agordeev@...ux.ibm.com>
Cc: linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org,
        kvm@...r.kernel.org, hca@...ux.ibm.com, borntraeger@...ibm.com,
        gor@...ux.ibm.com, pasic@...ux.ibm.com, jjherne@...ux.ibm.com,
        alex.williamson@...hat.com
Subject: Re: [PATCH v1] s390/vfio-ap: Signal eventfd when guest AP
 configuration is changed




On 2/5/25 12:33 PM, Rorie Reyes wrote:
>
> On 1/13/25 11:08 AM, Alexander Gordeev wrote:
>> On Tue, Jan 07, 2025 at 01:36:45PM -0500, Rorie Reyes wrote:
>>
>> Hi Rorie, Antony,
>>
>>> Note that there are corresponding QEMU patches that will be shipped 
>>> along
>>> with this patch (see vfio-ap: Report vfio-ap configuration changes) 
>>> that
>>> will pick up the eventfd signal.
>> How this patch is synchronized with the mentioned QEMU series?
>> What is the series status, especially with the comment from Cédric Le 
>> Goater [1]?
>>
>> 1. 
>> https://lore.kernel.org/all/20250107184354.91079-1-rreyes@linux.ibm.com/T/#mb0d37909c5f69bdff96289094ac0bad0922a7cce
>>
>> Thanks!
>
> Hey Alex, sorry for the long delay. This patch is synchronized with 
> the QEMU series by registering an event notifier handler to process AP 
> configuration
>
> change events. This is done by queuing the event and generating a CRW. 
> The series status is currently going through a v2 RFC after 
> implementing changes
>
> requested by Cedric and Tony.
>
> Let me know if there's anything else you're concerned with
>
> Thanks!

I don't think that is what Alex was asking. I believe he is asking how 
the QEMU and kernel patch series are going to be synchronized.
Given the kernel series changes a value in vfio.h which is used by QEMU, 
the two series need to be coordinated since the vfio.h file
used by QEMU can not be updated until the kernel code is available. So 
these two sets of code have
to be merged upstream during a merge window. which is different for the 
kernel and QEMU. At least I think that is what Alex is asking.



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ