[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220413232053.GA2120790@nvidia.com>
Date: Wed, 13 Apr 2022 20:20:53 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: "Wang, Zhi A" <zhi.a.wang@...el.com>
Cc: Jani Nikula <jani.nikula@...ux.intel.com>,
Christoph Hellwig <hch@....de>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
"Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
Zhenyu Wang <zhenyuw@...ux.intel.com>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Alex Williamson <alex.williamson@...hat.com>
Subject: Re: refactor the i915 GVT support and move to the modern mdev API v3
On Wed, Apr 13, 2022 at 11:13:06PM +0000, Wang, Zhi A wrote:
> Hi folks:
>
> Thanks so much for the efforts. I prepared a branch which contains all our patches.The aim of the branch is for the VFIO maintainers to pull the whole bunch easily after the drm-intel-next got merged through drm (as one of the MMIO patches depends on a patch in drm-intel-next).
>
> I dropped patch 4 and patch 5 as they have been covered by Jani's patches. Some conflicts was solved.
> QA is going to test it today.
>
> You can find it here:
>
> git clone https://github.com/intel/gvt-linux -b for-christoph
There are alot of extra commits on there - is it possible to base this
straight on rc1 not on some kind of existing DRM tree?
Why did you choose drm/i915/fbc: Call intel_fbc_activate() directly
from frontbuffer flush as a base?
Jason
Powered by blists - more mailing lists