From: Chris Wilson <chris@chris-wilson.co.uk>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Jaswinder Singh Rajput <jaswinderlinux@gmail.com>,
dri-devel@lists.freedesktop.org, Dave Airlie <airlied@linux.ie>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Keith Packard <keithp@keithp.com>, Eric Anholt <eric@anholt.net>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: DRM Error on Acer Aspire One
Date: Tue, 11 May 2010 19:52:31 +0100 [thread overview]
Message-ID: <89kc63$grv1m8@fmsmga002.fm.intel.com> (raw)
In-Reply-To: <20100511113555.a78c9c8e.akpm@linux-foundation.org>
On Tue, 11 May 2010 11:35:55 -0400, Andrew Morton <akpm@linux-foundation.org> wrote:
> No, io_mapping_map_atomic_wc() cannot be used from [soft]irq context:
> it hardwires use of KM_USER0. I suggest that io_mapping_create_wc(),
> io_mapping_map_atomic_wc() etc be changed so that the caller passes in the
> KM_foo kmap slot index.
Argh, sorry for the noise, read the mail in the wrong order. Thanks for
the review. It would be sensible to go with your simpler patch whilst
io_mapping_map_atomic_wc() is improved.
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2010-05-11 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 15:00 DRM Error on Acer Aspire One Jaswinder Singh Rajput
2010-05-11 16:10 ` Chris Wilson
2010-05-11 14:48 ` Andrew Morton
2010-05-11 18:18 ` Jaswinder Singh Rajput
2010-05-11 18:19 ` Chris Wilson
2010-05-11 15:35 ` Andrew Morton
2010-05-11 18:52 ` Chris Wilson [this message]
2010-05-11 19:10 ` Andrew Morton
2010-05-11 19:57 ` Chris Wilson
2010-05-11 22:22 ` Dave Airlie
2010-05-11 22:32 ` Andrew Morton
2010-05-11 22:51 ` Dave Airlie
2010-05-11 22:56 ` Andrew Morton
2010-05-11 23:17 ` Dave Airlie
2010-05-11 23:24 ` Andrew Morton
2010-05-11 22:40 ` Chris Wilson
2010-05-11 17:39 ` Jaswinder Singh Rajput
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='89kc63$grv1m8@fmsmga002.fm.intel.com' \
--to=chris@chris-wilson.co.uk \
--cc=airlied@linux.ie \
--cc=akpm@linux-foundation.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=jaswinderlinux@gmail.com \
--cc=keithp@keithp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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