public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Vasily Gorbik <gor@linux.ibm.com>
To: Anthony Krowiak <akrowiak@linux.ibm.com>
Cc: Rorie Reyes <rreyes@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Heiko Carstens <hca@linux.ibm.com>,
	linux-s390@vger.kernel.org, linux-kernel@vger.kernel.org,
	kvm@vger.kernel.org, borntraeger@de.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: Wed, 12 Feb 2025 11:55:19 +0100	[thread overview]
Message-ID: <your-ad-here.call-01739357719-ext-1861@work.hours> (raw)
In-Reply-To: <8767c6ce-28cf-4e23-baf8-e6c9ec854c60@linux.ibm.com>

On Tue, Feb 11, 2025 at 03:24:05PM -0500, Anthony Krowiak wrote:
> 
> 
> 
> On 2/11/25 10:02 AM, Rorie Reyes wrote:
> > 
> > On 2/11/25 2:58 AM, Alexander Gordeev wrote:
> > > On Thu, Feb 06, 2025 at 09:12:27AM -0500, Rorie Reyes wrote:
> > > 
> > > Hi Rorie,
> > > 
> > > > On 2/6/25 2:40 AM, Alexander Gordeev wrote:
> > > > > On Wed, Feb 05, 2025 at 12:47:55PM -0500, Anthony Krowiak wrote:
> > > > > > > > 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
> > > ...
> > > > > > 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.
> > > > > Correct.
> > > > > Thanks for the clarification, Anthony!
> > > > Tony, thank you for the back up!
> > > > 
> > > > Alexander, is there anything else you need from my end for
> > > > clarification?
> > > The original question still stays - is it safe to pull this patch now,
> > > before the corresponding QEMU change is integrated?
> 
> This patch has to be pulled before the QEMU patches are integrated. The
> change to the
> include/uapi/linux/vfio.h file needs to be merged before the QEMU version of
> that file
> can be generated for a QEMU build. I have given my r-b for this patch, so I
> think it is
> safe to pull it now.

Ok, applied, thank you!

  reply	other threads:[~2025-02-12 10:55 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 [this message]
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
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=your-ad-here.call-01739357719-ext-1861@work.hours \
    --to=gor@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akrowiak@linux.ibm.com \
    --cc=alex.williamson@redhat.com \
    --cc=borntraeger@de.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