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=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED 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 E2E2DC2BA80 for ; Tue, 7 Apr 2020 13:53:27 +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 C2EDF20731 for ; Tue, 7 Apr 2020 13:53:27 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org C2EDF20731 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=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 6B2156E887; Tue, 7 Apr 2020 13:53:27 +0000 (UTC) Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by gabe.freedesktop.org (Postfix) with ESMTPS id 4160D6E887; Tue, 7 Apr 2020 13:53:26 +0000 (UTC) IronPort-SDR: NQySUVHT36gblCj1po24BLgk246HUQUXCLjvZ4aBz2yUYx/ZWnBSeW0y2m6Lb1xxq7B6j5iuIu SWJ2Csp/F2SA== X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Apr 2020 06:53:25 -0700 IronPort-SDR: 5g18Bf4c6jossTx9xm8ozhK5EJOwo7QrEUUw81uEGwcQJ4xeJ3rINMxkO14+a3rnNGq3vGw+L8 /QLg5XPorELA== X-IronPort-AV: E=Sophos;i="5.72,354,1580803200"; d="scan'208";a="424754819" Received: from vogtstef-mobl3.ger.corp.intel.com (HELO localhost) ([10.249.40.153]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 07 Apr 2020 06:53:22 -0700 From: Jani Nikula To: Rodrigo Vivi , Zhenyu Wang In-Reply-To: <20200407133559.GB4170610@intel.com> Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo References: <20200331070025.GB16629@zhen-hp.sh.intel.com> <20200331162644.GA3779315@intel.com> <20200403030507.GQ16629@zhen-hp.sh.intel.com> <20200403175033.GA3997092@intel.com> <20200407080256.GU16629@zhen-hp.sh.intel.com> <20200407133559.GB4170610@intel.com> Date: Tue, 07 Apr 2020 16:53:19 +0300 Message-ID: <87wo6rier4.fsf@intel.com> MIME-Version: 1.0 Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes 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: "Zhao, Yan Y" , intel-gvt-dev , intel-gfx , "Yuan, Hang" , "Lv, Zhiyuan" , "Vetter, Daniel" Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Tue, 07 Apr 2020, Rodrigo Vivi wrote: > On Tue, Apr 07, 2020 at 04:02:56PM +0800, Zhenyu Wang wrote: >> On 2020.04.03 10:50:33 -0700, Rodrigo Vivi wrote: >> > >> > +Dave and Daniel, >> > >> > > >> > > I forgot to mention one thing for 5.7. We've fixed to change guest mem r/w >> > > from KVM to use new VFIO dma r/w instead in this series: https://patchwork.freedesktop.org/series/72038/ >> > > >> > > As this depends on VFIO tree and looks VFIO pull for 5.7 is not settled down >> > > yet, we'd need to backmerge and send pull against vfio merge for 5.7. >> > >> > I'm not sure if I'm following on which backmerge you are willing >> > us to do here. And for me it looks like late for 5.7 already. >> > >> > Maybe you mean we ack all of this to go through vfio flow >> > then once that is settled drm backmerge and then drm-intel backmerge >> > and you backmerge... >> > >> > Is that what you want? >> > >> >> My purpose is to get GVT side fixes of guest memory r/w through new >> vfio dma r/w interface in 5.7. As vfio 5.7-rc1 pull has already been >> merged in linus master, looks just want drm-intel backmerge now then >> could send gvt side fixes. Ok for you? > > I'm afraid it is too late for that. That would depend on backmerge > of drm itself as well... And we are in a point that we are about to > move from drm-next to drm-fixes. *If* they're fixes, drm-intel-fixes rebases on v5.7-rc1 or -rc2, and if they can send a gvt fixes pull based on that, it could work out. BR, Jani. > > Also looking to the patches itself they look more content for -next > than -fixes and our window with drm closed on -rc6 > > So it looks to me that this will have to wait for the 5.8. > > One good suggestion I heard from Daniel for cases like this in the > future is the use of topic branches so things don't get spread into > multiple versions like this. > >> >> Sorry for late reply, I was out for a short vacation. > > Sorry for not been able to help further here > > Thanks, > Rodrigo. > >> >> Thanks >> >> -- >> Open Source Technology Center, Intel ltd. >> >> $gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827 > > -- Jani Nikula, Intel Open Source Graphics Center _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx