From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/3] drm/i915: Embed the scratch page struct into each VM
Date: Mon, 22 Aug 2016 13:21:51 +0300 [thread overview]
Message-ID: <1471861311.3601.7.camel@linux.intel.com> (raw)
In-Reply-To: <20160822074431.26872-2-chris@chris-wilson.co.uk>
On ma, 2016-08-22 at 08:44 +0100, Chris Wilson wrote:
> As the scratch page is no longer shared between all VM, and each has
> their own, forgo the small allocation and simply embed the scratch page
> struct into the i915_address_space.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
A fairly mechanical change.
Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
For dropping the use of px_dma & friend macros, maybe an A-b from Mika.
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-08-22 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 7:44 [PATCH 1/3] drm/i915: Stop marking the unaccessible scratch page as UC Chris Wilson
2016-08-22 7:44 ` [PATCH 2/3] drm/i915: Embed the scratch page struct into each VM Chris Wilson
2016-08-22 10:21 ` Joonas Lahtinen [this message]
2016-08-22 11:01 ` Mika Kuoppala
2016-08-22 7:44 ` [PATCH 3/3] drm/i915: Allow DMA pagetables to use highmem Chris Wilson
2016-08-22 11:04 ` Joonas Lahtinen
2016-08-22 8:39 ` ✗ Ro.CI.BAT: failure for series starting with [1/3] drm/i915: Stop marking the unaccessible scratch page as UC Patchwork
2016-08-22 9:34 ` [PATCH 1/3] " 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=1471861311.3601.7.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--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.