[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210928150507.GM964074@nvidia.com>
Date: Tue, 28 Sep 2021 12:05:07 -0300
From: Jason Gunthorpe <jgg@...dia.com>
To: "Wang, Zhi A" <zhi.a.wang@...el.com>
Cc: Luis Chamberlain <mcgrof@...nel.org>, Jessica Yu <jeyu@...nel.org>,
"De Marchi, Lucas" <lucas.demarchi@...el.com>,
Zhenyu Wang <zhenyuw@...ux.intel.com>,
Christoph Hellwig <hch@....de>,
"dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
Greg KH <gregkh@...uxfoundation.org>,
"intel-gfx@...ts.freedesktop.org" <intel-gfx@...ts.freedesktop.org>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Jani Nikula <jani.nikula@...ux.intel.com>,
Gerd Hoffmann <kraxel@...hat.com>,
"Vivi, Rodrigo" <rodrigo.vivi@...el.com>,
"intel-gvt-dev@...ts.freedesktop.org"
<intel-gvt-dev@...ts.freedesktop.org>,
"Nikula, Jani" <jani.nikula@...el.com>
Subject: Re: refactor the i915 GVT support
On Tue, Sep 28, 2021 at 02:35:06PM +0000, Wang, Zhi A wrote:
> Yes. I was thinking of the possibility of putting off some work later so
> that we don't need to make a lot of changes. GVT-g needs to take a
> snapshot of GPU registers as the initial virtual states for other vGPUs,
> which requires the initialization happens at a certain early time of
> initialization of i915. I was thinking maybe we can take other patches
> from Christoph like "de-virtualize*" except this one because currently
> we have to maintain a TEST-ONLY patch on our tree to prevent i915 built
> as kernel module.
How about just capture these registers in the main module/device and
not try so hard to isolate it to the gvt stuff?
Jason
Powered by blists - more mailing lists