From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Zhenyu Wang <zhenyuw@linux.intel.com>, Tina Zhang <tina.zhang@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH v4] drm/i915: Enable guest i915 full ppgtt functionality
Date: Thu, 08 Jun 2017 13:20:43 +0300 [thread overview]
Message-ID: <1496917243.2924.20.camel@linux.intel.com> (raw)
In-Reply-To: <20170607093053.6ncyqlak7xbl7huw@zhen-hp.sh.intel.com>
On ke, 2017-06-07 at 17:30 +0800, Zhenyu Wang wrote:
> On 2017.06.05 14:55:41 +0800, Tina Zhang wrote:
> >
> > @@ -53,12 +53,18 @@ enum vgt_g2v_type {
> > VGT_G2V_MAX,
> > };
> >
> > +/*
> > + * VGT capabilities type
> > + */
> > +#define VGT_CAPS_FULL_PPGTT BIT(2)
> > +
>
> As I think your gvt change will depend on this bit too, so have to merge
> them in order, right? Joonas, ok for me to merge through gvt tree together
> for -next pull?
Yes, that way the ordering gets right. As mentioned in IRC, the
major/minor version checking should be merged first, and this updated
to use that.
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
prev parent reply other threads:[~2017-06-08 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-05 6:55 [PATCH v4] drm/i915: Enable guest i915 full ppgtt functionality Tina Zhang
2017-06-05 8:43 ` ✓ Fi.CI.BAT: success for drm/i915: Enable guest i915 full ppgtt functionality (rev2) Patchwork
2017-06-07 9:30 ` [PATCH v4] drm/i915: Enable guest i915 full ppgtt functionality Zhenyu Wang
2017-06-08 10:20 ` Joonas Lahtinen [this message]
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=1496917243.2924.20.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=tina.zhang@intel.com \
--cc=zhenyuw@linux.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