From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 659A1C433EF for ; Tue, 15 Mar 2022 07:52:24 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id BEA1A10E3CE; Tue, 15 Mar 2022 07:52:23 +0000 (UTC) Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by gabe.freedesktop.org (Postfix) with ESMTPS id C024A10E3CE; Tue, 15 Mar 2022 07:52:22 +0000 (UTC) Received: by verein.lst.de (Postfix, from userid 2407) id B152768AFE; Tue, 15 Mar 2022 08:52:17 +0100 (CET) Date: Tue, 15 Mar 2022 08:52:17 +0100 From: Christoph Hellwig To: "Wang, Zhi A" Message-ID: <20220315075217.GA2830@lst.de> References: <20220208111151.13115-1-zhi.a.wang@intel.com> <871r0dqtjf.fsf@intel.com> <20220209072805.GA9050@lst.de> <4e2faf7b-383e-58b3-8ae9-8f8d25c64420@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4e2faf7b-383e-58b3-8ae9-8f8d25c64420@intel.com> User-Agent: Mutt/1.5.17 (2007-11-01) Subject: Re: [Intel-gfx] [PATCH v6 1/3] i915/gvt: Introduce the mmio table to support VFIO new mdev API X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Zhi Wang , "intel-gfx@lists.freedesktop.org" , "linux-kernel@vger.kernel.org" , "Xu, Terrence" , "dri-devel@lists.freedesktop.org" , "jgg@nvidia.com" , "Vivi, Rodrigo" , "intel-gvt-dev@lists.freedesktop.org" , Christoph Hellwig Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" Just curious, what is the state of this seris? It would be good to have it ready early on for the next merge window as there is quite a backlog that depends on it.