Quoting Christoph Hellwig (2021-11-09 09:59:57)
> On Thu, Nov 04, 2021 at 02:59:18PM +0200, Joonas Lahtinen wrote:
> > The minimal we should do is to eliminate the double underscore
> > prefixed functions. But I would prefer to have the symbol exports by
> > default so that we can enable the functi
On Thu, Nov 04, 2021 at 02:51:28PM +, Wang, Zhi A wrote:
> Is it possible to separate the refactor part from the using new mdev API
> stuff? So that the design opens in the re-factor patches wouldn’t block the
> process of mdev API improvement?
Jason had an early patch for it, but it looks s
On Thu, Nov 04, 2021 at 02:59:18PM +0200, Joonas Lahtinen wrote:
> The minimal we should do is to eliminate the double underscore
> prefixed functions. But I would prefer to have the symbol exports by
> default so that we can enable the functionality just by loading the
> module.
I'm fine with exp
Hi Joonas and Christoph:
We were testing the patch series since Monday and planning to reply after we
get the test result. Mostly, we are concerned about patch 6 and how it would
affect the test result. Patch 6 changes the timing of loading GVT-g. According
to the discussion in the last email,
Hi Zhenyu and Zhi,
Can you have somebody from the GVT team to review the patches that
are fully contained in gvt/ ?
I also started discussion on patch 6 which is about defining the
interface between the modules. I remember there is prior work to shrink
the interface. Do you have links to such pat
Hi all,
the GVT code in the i915 is a bit of a mess right now due to strange
abstractions and lots of indirect calls. This series refactors various
bits to clean that up. The main user visible change is that almost all
of the GVT code moves out of the main i915 driver and into the kvmgt
module.
