intel-gfx.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
	Zhenyu Wang <zhenyuw@linux.intel.com>
Cc: "Zhao, Yan Y" <yan.y.zhao@intel.com>,
	intel-gvt-dev <intel-gvt-dev@lists.freedesktop.org>,
	intel-gfx <intel-gfx@lists.freedesktop.org>,
	"Yuan,  Hang" <hang.yuan@intel.com>,
	"Lv, Zhiyuan" <zhiyuan.lv@intel.com>,
	"Vetter, Daniel" <daniel.vetter@intel.com>
Subject: Re: [Intel-gfx] [PULL] gvt-next-fixes
Date: Tue, 07 Apr 2020 16:53:19 +0300	[thread overview]
Message-ID: <87wo6rier4.fsf@intel.com> (raw)
In-Reply-To: <20200407133559.GB4170610@intel.com>

On Tue, 07 Apr 2020, Rodrigo Vivi <rodrigo.vivi@intel.com> 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

  reply	other threads:[~2020-04-07 13:53 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-31  7:00 [Intel-gfx] [PULL] gvt-next-fixes Zhenyu Wang
2020-03-31 16:26 ` Rodrigo Vivi
2020-04-03  3:05   ` Zhenyu Wang
2020-04-03 17:50     ` Rodrigo Vivi
2020-04-07  8:02       ` Zhenyu Wang
2020-04-07 13:35         ` Rodrigo Vivi
2020-04-07 13:53           ` Jani Nikula [this message]
2020-04-07 23:36             ` Zhenyu Wang
  -- strict thread matches above, loose matches on Subject: below --
2023-04-28  7:47 Zhenyu Wang
2023-02-23  8:50 Zhenyu Wang
2023-02-23 12:11 ` Jani Nikula
2021-04-29  8:51 Zhenyu Wang
2021-04-29 11:12 ` Jani Nikula
2021-04-21  9:45 Zhenyu Wang
2021-04-21 10:51 ` Jani Nikula
2021-02-22  8:34 Zhenyu Wang
2021-02-23 14:42 ` Rodrigo Vivi
2020-12-25  2:20 Zhenyu Wang
2021-01-05  7:54 ` Zhenyu Wang
2021-01-05  8:36   ` Jani Nikula
2021-01-05 20:44     ` Rodrigo Vivi
2020-08-05  8:02 Zhenyu Wang
2020-08-06 15:17 ` Jani Nikula
2020-05-28  3:35 Zhenyu Wang
2020-06-02 14:04 ` Joonas Lahtinen
2019-12-02  5:17 Zhenyu Wang
2019-12-02  5:17 ` [Intel-gfx] " Zhenyu Wang
2019-12-05  6:11 ` Zhenyu Wang
2019-12-05  8:14   ` Joonas Lahtinen
2019-12-05  8:49     ` Zhenyu Wang
2019-11-12  6:20 Zhenyu Wang
2019-11-12  6:20 ` [Intel-gfx] " Zhenyu Wang
2019-11-20 11:25 ` Joonas Lahtinen
2019-11-20 11:25   ` [Intel-gfx] " Joonas Lahtinen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wo6rier4.fsf@intel.com \
    --to=jani.nikula@intel.com \
    --cc=daniel.vetter@intel.com \
    --cc=hang.yuan@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-gvt-dev@lists.freedesktop.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=yan.y.zhao@intel.com \
    --cc=zhenyuw@linux.intel.com \
    --cc=zhiyuan.lv@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).