From: Arjan van de Ven <arjan@infradead.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>
Subject: Re: RFC: banning device driver reserved resources from /dev/mem
Date: Sun, 5 Oct 2008 22:26:00 -0700 [thread overview]
Message-ID: <20081005222600.11121739@infradead.org> (raw)
In-Reply-To: <20081006052337.GE2186@elte.hu>
On Mon, 6 Oct 2008 07:23:37 +0200
Ingo Molnar <mingo@elte.hu> wrote:
>
> > +int iomem_is_reserved(u64 addr)
> > +{
> > + struct resource *p = &iomem_resource;
...
> > + */
> > + if (p->start >= addr + size)
> > + continue;
>
> do we want to skip all resources that are not IORESOURCE_MEM? Same
> holds for iomem_map_sanity_check(), introduced in tip/core/resources:
if we have non-IORESOURCE_MEM resources in the iomem_resource tree....
then we have bigger problems.
--
Arjan van de Ven Intel Open Source Technology Centre
For development, discussion and tips for power savings,
visit http://www.lesswatts.org
next prev parent reply other threads:[~2008-10-06 5:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-06 1:01 Arjan van de Ven
2008-10-06 5:23 ` Ingo Molnar
2008-10-06 5:26 ` Arjan van de Ven [this message]
2008-10-06 9:27 ` Alan Cox
2008-10-06 13:40 ` Maxim Levitsky
2008-10-06 13:48 ` Alan Cox
2008-10-06 13:52 ` Arjan van de Ven
2008-10-06 14:01 ` Alan Cox
2008-10-06 14:05 ` Arjan van de Ven
2008-10-06 14:14 ` Alan Cox
2008-10-06 14:24 ` Arjan van de Ven
2008-10-06 14:38 ` Alan Cox
2008-10-06 14:57 ` Arjan van de Ven
2008-10-06 15:29 ` Alan Cox
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=20081005222600.11121739@infradead.org \
--to=arjan@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=yinghai@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
all inboxes | Powered by JetHome®