From: Chen Gang <gang.chen.5i5j@gmail.com>
To: 管雪涛 <gxt@pku.edu.cn>
Cc: Guan Xuetao <gxt@mprc.pku.edu.cn>,
akpm@linux-foundation.org, liuj97@gmail.com, rientjes@google.com,
dhowells@redhat.com, mhocko@suse.cz, mgorman@suse.de,
linux-kernel@vger.kernel.org
Subject: Re: 回复: [PATCH] arch:unicore32:mm: add devmem_is_allowed() to support STRICT_DEVMEM
Date: Tue, 08 Apr 2014 12:54:14 +0800 [thread overview]
Message-ID: <534380F6.7090703@gmail.com> (raw)
In-Reply-To: <629583968.18592.1396927216694.JavaMail.root@bj-mail03.pku.edu.cn>
On 04/08/2014 11:20 AM, 管雪涛 wrote:
> I'd like to put the code into asm/io.h, and make it static.
>
It sounds OK to me, but I don't know why the other architectures (e.g.
arm, powerpc, x86) put them into ".c".
iomem_is_exclusive() and page_is_ram() are all extern functions, so for
me, devmem_is_allowed() is shot enough to be as inline function.
>> +#ifdef CONFIG_STRICT_DEVMEM
>> +/*
>> + * devmem_is_allowed() checks to see if /dev/mem access to a certain
>> + * address is valid. The argument is a physical page number.
>> + * We mimic x86 here by disallowing access to system RAM as well as
>> + * device-exclusive MMIO regions. This effectively disable read()/write()
>> + * on /dev/mem.
>> + */
>> +static int devmem_is_allowed(unsigned long pfn)
How about "static inline int devmem_is_allowed(unsigned long pfn)"?
>> +{
>> + if (iomem_is_exclusive(pfn << PAGE_SHIFT))
>> + return 0;
>> + if (!page_is_ram(pfn))
>> + return 1;
>> + return 0;
>> +}
>> +#endif /* CONFIG_STRICT_DEVMEM */
>
> Thanks,
>
> Acked-by: Xuetao Guan <gxt@mprc.pku.edu.cn>
>
[...]
Thanks.
--
Chen Gang
Open, share, and attitude like air, water, and life which God blessed
next prev parent reply other threads:[~2014-04-08 4:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-07 11:28 [PATCH] arch:unicore32:mm: add devmem_is_allowed() to support STRICT_DEVMEM Chen Gang
2014-04-08 3:20 ` 回复: " 管雪涛
2014-04-08 4:54 ` Chen Gang [this message]
2014-04-15 0:14 ` Chen Gang
2014-04-15 0:28 ` [PATCH v2] " Chen Gang
2014-04-15 0:42 ` Chen Gang
2014-04-15 1:21 ` [PATCH v3] " Chen Gang
2014-04-16 5:15 ` 回复: " 管雪涛
2014-04-16 5:43 ` Chen Gang
2014-04-16 9:05 ` Michal Hocko
2014-04-16 10:11 ` Chen Gang
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=534380F6.7090703@gmail.com \
--to=gang.chen.5i5j@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=gxt@mprc.pku.edu.cn \
--cc=gxt@pku.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=liuj97@gmail.com \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=rientjes@google.com \
/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).