From: Zhenyu Wang <zhenyuw@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] Revert "drm/i915: Introduce private PAT management"
Date: Fri, 12 Jul 2019 16:28:51 +0800 [thread overview]
Message-ID: <20190712082851.GG9684@zhen-hp.sh.intel.com> (raw)
In-Reply-To: <156291876155.8011.12180387362444561726@jlahtine-mobl.fi.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 1310 bytes --]
On 2019.07.12 11:06:01 +0300, Joonas Lahtinen wrote:
> + Zhenyu as FYI
>
> Quoting Chris Wilson (2019-07-02 14:56:04)
> > Quoting Michał Winiarski (2019-07-02 12:31:48)
> > > This reverts commit 4395890a48551982549d222d1923e2833dac47cf.
> > >
> > > It's been over a year since this was merged, and the actual users of
> > > intel_ppat_get / intel_ppat_put never materialized.
> > >
> > > Time to remove it!
> > >
> > > v2: Unbreak suspend (Chris)
> > > v3: Rebase, drop fixes tag to avoid confusion
> > >
> > > Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> > > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > > Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Cc: Zhi Wang <zhi.a.wang@intel.com>
> > Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> >
> > While I would appreciate an ack from Zhi (being the original author),
> > since we've already sent this a few times, there's no reason to delay
> > waiting for a response.
Well I also depend on Zhi for comment here, as previous idea was to
manage PPAT allocation between VM/host, but I'm not sure what's left
work status there..
--
Open Source Technology Center, Intel ltd.
$gpg --keyserver wwwkeys.pgp.net --recv-keys 4D781827
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-12 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-02 11:31 [PATCH 1/2] Revert "drm/i915: Introduce private PAT management" Michał Winiarski
2019-07-02 11:31 ` [PATCH 2/2] drm/i915/gtt: Don't check PPGTT presence on PPGTT-only platforms Michał Winiarski
2019-07-02 11:54 ` Chris Wilson
2019-07-02 11:56 ` [PATCH 1/2] Revert "drm/i915: Introduce private PAT management" Chris Wilson
2019-07-12 8:06 ` Joonas Lahtinen
2019-07-12 8:28 ` Zhenyu Wang [this message]
2019-07-12 8:45 ` Wang, Zhi A
2019-07-02 16:00 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/2] " Patchwork
2019-07-02 16:02 ` ✗ Fi.CI.SPARSE: " Patchwork
2019-07-02 16:30 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-03 14:16 ` ✓ Fi.CI.IGT: " Patchwork
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=20190712082851.GG9684@zhen-hp.sh.intel.com \
--to=zhenyuw@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joonas.lahtinen@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