From: Rorie Reyes <rreyes@linux.ibm.com>
To: "Cédric Le Goater" <clg@redhat.com>,
qemu-devel@nongnu.org, qemu-s390x@nongnu.org,
"Vasily Gorbik" <gor@linux.ibm.com>
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 v2 1/5] linux-headers: NOTFORMERGE - placeholder uapi updates for AP config change
Date: Mon, 10 Mar 2025 11:23:54 -0400 [thread overview]
Message-ID: <c0730cdd-e37d-49f3-bfe7-240cd0a887c1@linux.ibm.com> (raw)
In-Reply-To: <b274c191-36db-4671-8361-59d2688d16de@redhat.com>
On 3/10/25 10:38 AM, Cédric Le Goater wrote:
> Hello Rorie,
>
>
>
> On 3/10/25 15:20, Rorie Reyes wrote:
>> On 2/5/25 3:38 AM, Cédric Le Goater wrote:
>>
>>>
>>> Are the kernel changes planned for 6.14 ?
>>>
>>> FYI, QEMU 10.0 hard freeze is scheduled for 2025-03-18 which is
>>> approximately when 6.14-rc7 will be released.
>>>
>>> Thanks,
>>>
>>> C.
>>
>> Vasily - Since you applied my kernel patches already ([RFC PATCH v2]
>> s390/vfio-ap: Notify userspace that guest's AP config changed when
>> mdev removed), would you be able to answer Cedric's
>>
>> a question?
>>
>> Cedric - I have some changes I need to make based on Tony's review
>> comments from Friday, but I'll wait to post it once you get an answer
>> for your question. Sorry I took a while to respond. I had to
>>
>> make some changes for my kernel code this past month.
>>
>
> AFAICT, the changes were merged in the s390 sub-maintainer tree,
> 07d89045bffea30ef08b902c2441a3329e44f29d, and they haven't reached
> Linux master yet. Seems a bit late for the 6.14 cycle now.
>
> linux-headers in QEMU are in sync with version 6.14-rc3 and that
> should the last update before QEMU 10.0 soft-freeze tomorrow.
>
> Most likely, this series should now target the next cycles:
> Linux 6.15 and QEMU 10.1. We have time.
>
>
> Thanks,
>
> C.
Thanks Cedric! I'll post the v3 patch from Tony's review
next prev parent reply other threads:[~2025-03-10 15:24 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 [this message]
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
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=c0730cdd-e37d-49f3-bfe7-240cd0a887c1@linux.ibm.com \
--to=rreyes@linux.ibm.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=clg@redhat.com \
--cc=cohuck@redhat.com \
--cc=gor@linux.ibm.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.