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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 56153C433ED for ; Fri, 14 May 2021 07:27:12 +0000 (UTC) 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 mail.kernel.org (Postfix) with ESMTPS id E13A2613CD for ; Fri, 14 May 2021 07:27:11 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org E13A2613CD Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=intel-gfx-bounces@lists.freedesktop.org Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 3C85B6EE19; Fri, 14 May 2021 07:27:11 +0000 (UTC) Received: from mga06.intel.com (mga06.intel.com [134.134.136.31]) by gabe.freedesktop.org (Postfix) with ESMTPS id A84C86EE19; Fri, 14 May 2021 07:27:09 +0000 (UTC) IronPort-SDR: dspuF2inPzbIrifYih81VvsA6WFYk0mbgG9I3hKmzmJwUjKe9FFNxVB7K4WjsxqLjCovaXDJ1b Os8ITNfF5yIg== X-IronPort-AV: E=McAfee;i="6200,9189,9983"; a="261369493" X-IronPort-AV: E=Sophos;i="5.82,299,1613462400"; d="asc'?scan'208";a="261369493" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 May 2021 00:27:08 -0700 IronPort-SDR: /2CUr416hsxZEFJzvNSSZcwQAXHG+hhttZBO66BpG2BgNVXcSBMxLuS2ocrAhR5kW8MwheJ5O4 u/Ev88EgzQgA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.82,299,1613462400"; d="asc'?scan'208";a="393529228" Received: from zhen-hp.sh.intel.com (HELO zhen-hp) ([10.239.160.147]) by orsmga006.jf.intel.com with ESMTP; 14 May 2021 00:27:07 -0700 Date: Fri, 14 May 2021 15:08:08 +0800 From: Zhenyu Wang To: Jason Gunthorpe Message-ID: <20210514070808.GW4589@zhen-hp.sh.intel.com> References: <20210511083332.1740601-1-zhenyuw@linux.intel.com> <20210511083332.1740601-2-zhenyuw@linux.intel.com> <20210511155446.GB1096940@ziepe.ca> <20210512023141.GN4589@zhen-hp.sh.intel.com> <20210512124739.GC1096940@ziepe.ca> <20210513045647.GQ4589@zhen-hp.sh.intel.com> <20210513120249.GH1096940@ziepe.ca> MIME-Version: 1.0 In-Reply-To: <20210513120249.GH1096940@ziepe.ca> Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915/gvt: Move mdev attribute groups into kvmgt module 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: , Reply-To: Zhenyu Wang Cc: Arnd Bergmann , intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org Content-Type: multipart/mixed; boundary="===============1664463436==" Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" --===============1664463436== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="0z5c7mBtSy1wdr4F" Content-Disposition: inline --0z5c7mBtSy1wdr4F Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On 2021.05.13 09:02:49 -0300, Jason Gunthorpe wrote: > On Thu, May 13, 2021 at 12:56:47PM +0800, Zhenyu Wang wrote: > > On 2021.05.12 09:47:39 -0300, Jason Gunthorpe wrote: > > > On Wed, May 12, 2021 at 10:31:41AM +0800, Zhenyu Wang wrote: > > >=20 > > > > > This need to go into the vfio tree in some way, either directly > > > > > through it, via rc or otherwise > > > >=20 > > > > As this is only for i915/gvt, once drm/i915 backmerge with linus ma= ster, > > > > it should still go through normal i915/gvt merge path. > > >=20 > > > Don't do this, you will create conflicts with ongoing vfio work. > > >=20 > >=20 > > Sure, there always could be conflict, which means you need to rebase on= to > > this cleanup. Would that a problem?=20 >=20 > Yes. >=20 > > I'd want to fix current workaround in 5.13-rc. >=20 > This doesn't seem like a rc candiate to me, but going to -rc is also > fine. >=20 > > Merging i915/gvt only change through vfio doesn't make sense to me, >=20 > You need to do it to avoid major conflicts for stuff that will go into > the vfio tree this cycle. Looks apply to vfio/for-linus is fine, and vfio/next missed gvt change to apply...but not conflict with any new stuff. Alex, pls let me know if you have any concern of this. >=20 > VFIO drivers should not be outside drivers/vfio/ in the first place, > and this shows why. >=20 Well, I can't agree, otherwise that'll be dependency nightmare for device driver writer. ;) --0z5c7mBtSy1wdr4F Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iF0EARECAB0WIQTXuabgHDW6LPt9CICxBBozTXgYJwUCYJ4h0QAKCRCxBBozTXgY J5qhAJ4wnUbFCxgVPi7+gbWLXR4UFO0QBQCdGuqANsOlLWqyftWJYlUYabo/CDo= =YhZJ -----END PGP SIGNATURE----- --0z5c7mBtSy1wdr4F-- --===============1664463436== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx --===============1664463436==--