Re: [Intel-gfx] [PULL] gvt-next-fixes

[Zhenyu Wang <zhenyuw@linux.intel.com>]

[-- Attachment #1.1: Type: text/plain, Size: 3271 bytes --]

On 2020.04.07 16:53:19 +0300, Jani Nikula wrote:
> On Tue, 07 Apr 2020, Rodrigo Vivi <rodrigo.vivi@intel.com> wrote:
> > On Tue, Apr 07, 2020 at 04:02:56PM +0800, Zhenyu Wang wrote:
> >> On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote:
> >> > 
> >> > +Dave and Daniel,
> >> > 
> >> > > 
> >> > > I forgot to mention one thing for 5.7. We've fixed to change guest mem r/w
> >> > > from KVM to use new VFIO dma r/w instead in this series: https://patchwork.freedesktop.org/series/72038/
> >> > > 
> >> > > As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down
> >> > > yet, we'd need to backmerge and send pull against vfio merge for 5.7.
> >> > 
> >> > I'm not sure if I'm following on which backmerge you are willing
> >> > us to do here. And for me it looks like late for 5.7 already.
> >> > 
> >> > Maybe you mean we ack all of this to go through vfio flow
> >> > then once that is settled drm backmerge and then drm-intel backmerge
> >> > and you backmerge...
> >> > 
> >> > Is that what you want?
> >> > 
> >> 
> >> My purpose is to get GVT side fixes of guest memory r/w through new
> >> vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been
> >> merged in linus master, looks just want drm-intel backmerge now then
> >> could send gvt side fixes. Ok for you?
> >
> > I'm afraid it is too late for that. That would depend on backmerge
> > of drm itself as well... And we are in a point that we are about to
> > move from drm-next to drm-fixes.
> 
> *If* they're fixes, drm-intel-fixes rebases on v5.7-rc1 or -rc2, and if
> they can send a gvt fixes pull based on that, it could work out.
> 

yeah, that's also what I'm thinking about. Here's more background.

In gvt we need to access guest pages in some places, our current way
is to call KVM interface, but it turns out later that this interface
is supposed to be used by arch code only and what we should actually
depend on is using IOVA for guest page access instead of using guest
physical address by KVM. So we tried to add IOVA based guest r/w
support for VFIO and change gvt to use that. In that way they're real
fixes to me.

> >
> > Also looking to the patches itself they look more content for -next
> > than -fixes and our window with drm closed on -rc6

I understand that but the patches mostly for vfio interface hadn't been
finalized during rc6 window..

> >
> > So it looks to me that this will have to wait for the 5.8.
> >
> > One good suggestion I heard from Daniel for cases like this in the
> > future is the use of topic branches so things don't get spread into
> > multiple versions like this.
> >

Good idea. Does that mean such topic branch could be merged during
e.g -rc1 merge window?

Thanks

> >> 
> >> Sorry for late reply, I was out for a short vacation.
> >
> > Sorry for not been able to help further here
> >
> > Thanks,
> > Rodrigo.
> >
> >> 
> >> Thanks
> >> 
> >> -- 
> >> Open Source Technology Center, Intel ltd.
> >> 
> >> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
> >
> >
> 
> -- 
> Jani Nikula, Intel Open Source Graphics Center

-- 
Open Source Technology Center, Intel ltd.

$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx