From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: drm-intel-fixes@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Don't clflush before release phys object
Date: Thu, 22 Dec 2016 14:40:02 +0200 [thread overview]
Message-ID: <1482410402.7292.15.camel@linux.intel.com> (raw)
In-Reply-To: <20161222120007.28590-2-chris@chris-wilson.co.uk>
On to, 2016-12-22 at 12:00 +0000, Chris Wilson wrote:
> When we teardown the backing storage for the phys object, we copy from
> the coherent contiguous block back to the shmemfs object, clflushing as
> we go. Trying to clflush the invalid sg beforehand just oops and would
> be redundant (due to it already being coherent, and clflushed
> afterwards).
>
> Reported-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
> Cc: <drm-intel-fixes@lists.freedesktop.org>
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
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
next prev parent reply other threads:[~2016-12-22 12:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-22 12:00 [PATCH 1/3] drm/i915: Repeat flush of idle work during suspend Chris Wilson
2016-12-22 12:00 ` [PATCH 2/3] drm/i915: Don't clflush before release phys object Chris Wilson
2016-12-22 12:40 ` Joonas Lahtinen [this message]
2016-12-22 12:00 ` [PATCH 3/3] drm/i915: Silence allocation failure during sg_trim() Chris Wilson
2016-12-22 12:02 ` Joonas Lahtinen
2016-12-22 12:19 ` [PATCH 1/3] drm/i915: Repeat flush of idle work during suspend Joonas Lahtinen
2016-12-22 18:26 ` ✗ Fi.CI.BAT: warning for series starting with [1/3] " 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=1482410402.7292.15.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=drm-intel-fixes@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.