From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Travis <travis@sgi.com>
Cc: mingo@redhat.com, tglx@linutronix.de, hpa@zytor.com,
msalter@redhat.com, dyoung@redhat.com, riel@redhat.com,
peterz@infradead.org, mgorman@suse.de,
linux-kernel@vger.kernel.org, x86@kernel.org, linux-mm@kvack.org,
Alex Thorlton <athorlton@sgi.com>
Subject: Re: [PATCH 1/2] x86: Optimize resource lookups for ioremap
Date: Wed, 27 Aug 2014 17:21:28 -0700 [thread overview]
Message-ID: <20140827172128.93feef68.akpm@linux-foundation.org> (raw)
In-Reply-To: <53FE6FAA.6010806@sgi.com>
On Wed, 27 Aug 2014 16:54:18 -0700 Mike Travis <travis@sgi.com> wrote:
> > If we're still at 1+ hours then little bodges like this are nowhere
> > near sufficient and sterner stuff will be needed.
> >
> > Do we actually need the test? My googling turns up zero instances of
> > anyone reporting the "ioremap on RAM pfn" warning.
>
> We get them more than we like, mostly from 3rd party vendors, and
> esp. those that merely port their windows drivers to linux.
Dang. So wrapping the check in CONFIG_DEBUG_VM would be problematic?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2014-08-28 0:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-27 22:59 [PATCH 0/2] x86: Speed up ioremap operations Mike Travis
2014-08-27 22:59 ` [PATCH 1/2] x86: Optimize resource lookups for ioremap Mike Travis
2014-08-27 23:05 ` Andrew Morton
2014-08-27 23:09 ` Mike Travis
2014-08-27 23:18 ` Andrew Morton
2014-08-27 23:25 ` Mike Travis
2014-08-27 23:37 ` Andrew Morton
2014-08-27 23:54 ` Mike Travis
2014-08-28 0:21 ` Andrew Morton [this message]
2014-08-27 22:59 ` [PATCH 2/2] x86: Use optimized ioresource lookup in ioremap function Mike Travis
2014-08-27 23:06 ` [PATCH 0/2] x86: Speed up ioremap operations Andrew Morton
2014-08-27 23:15 ` Mike Travis
2014-08-27 23:20 ` Andrew Morton
2014-08-27 23:30 ` Mike Travis
2014-08-28 6:48 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2014-08-29 19:16 Mike Travis
2014-08-29 19:16 ` [PATCH 1/2] x86: Optimize resource lookups for ioremap Mike Travis
2014-08-29 19:53 [PATCH 0/2] x86: Speed up ioremap operations Mike Travis
2014-08-29 19:53 ` [PATCH 1/2] x86: Optimize resource lookups for ioremap Mike Travis
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=20140827172128.93feef68.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=athorlton@sgi.com \
--cc=dyoung@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=msalter@redhat.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--cc=x86@kernel.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;
as well as URLs for NNTP newsgroup(s).