From: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: linux-mm@kvack.org
Subject: Re: [PATCH 1/2] io-mapping: Always create a struct to hold metadata about the io-mapping
Date: Fri, 19 Aug 2016 13:26:28 +0300 [thread overview]
Message-ID: <1471602388.3866.0.camel@linux.intel.com> (raw)
In-Reply-To: <1471261984-15756-1-git-send-email-chris@chris-wilson.co.uk>
On ma, 2016-08-15 at 12:53 +0100, Chris Wilson wrote:
> Currently, we only allocate a structure to hold metadata if we need to
> allocate an ioremap for every access, such as on x86-32. However, it
> would be useful to store basic information about the io-mapping, such as
> its page protection, on all platforms.
>
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
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
prev parent reply other threads:[~2016-08-19 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 11:53 [PATCH 1/2] io-mapping: Always create a struct to hold metadata about the io-mapping Chris Wilson
2016-08-15 11:53 ` [PATCH 2/2] drm/i915: Use remap_io_mapping() to prefault all PTE in a single pass Chris Wilson
2016-08-19 11:32 ` Joonas Lahtinen
2016-08-19 12:23 ` Chris Wilson
2016-08-15 12:27 ` ✗ Ro.CI.BAT: failure for series starting with [1/2] io-mapping: Always create a struct to hold metadata about the io-mapping Patchwork
2016-08-19 10:26 ` 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=1471602388.3866.0.camel@linux.intel.com \
--to=joonas.lahtinen@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox