linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Michal Hocko <mhocko@suse.cz>
Cc: 管雪涛 <gxt@pku.edu.cn>, "Guan Xuetao" <gxt@mprc.pku.edu.cn>,
	akpm@linux-foundation.org, liuj97@gmail.com, rientjes@google.com,
	dhowells@redhat.com, mgorman@suse.de,
	linux-kernel@vger.kernel.org, will.deacon@arm.com,
	linux@arm.linux.org.uk,
	"Geert Uytterhoeven" <geert@linux-m68k.org>,
	arnd@arndb.de
Subject: Re: [PATCH v3] arch:unicore32:mm: add devmem_is_allowed() to support STRICT_DEVMEM
Date: Wed, 16 Apr 2014 18:11:13 +0800	[thread overview]
Message-ID: <534E5741.8090908@gmail.com> (raw)
In-Reply-To: <20140416090511.GB12866@dhcp22.suse.cz>

On 04/16/2014 05:05 PM, Michal Hocko wrote:
> On Tue 15-04-14 09:21:30, Chen Gang wrote:
> [...]
>> diff --git a/arch/unicore32/include/asm/io.h b/arch/unicore32/include/asm/io.h
>> index 39decb6..ae327e4 100644
>> --- a/arch/unicore32/include/asm/io.h
>> +++ b/arch/unicore32/include/asm/io.h
> 
> There is already quite a mess where the function is defined. We have it
> in mmap.c, init.c, mem.c and s390 defines it in page.h. Is there any
> good reason to add yet another place and pull in additional header files
> dependencies?

It is short enough to be as static inline function. It also can bypass
choosing which ".c" file contents the implementation (arm{64} declare it
in "io.h").

So recommend devmem_is_allowed() in arm{64} are also "static inline".

Hmm... is it possible to move the static inline implementation from
"io.h" to "page.h", since all other archs declare or implement in
"page.h" related header file.


> Why not follow x86 here? Or even better git rid of the code duplication
> and provide generic implementation which different arches can reuse and
> extend? arm{64}, unicore32 seem to be identical. Powepc and x86 have an
> additional test to the core one used by the above arches. Only tile
> seems to be be doing something completely different.
> 

For me, need not put it in 'asm-generic':

 - 9/29 archs need it, so at present, it is not generic enough.

 - most of them are different, which hard to find generic one.

   - frv and m32r same, but different with others.

   - arm{64} and unicore32 same, but different with others.

   - powerpc, s390, tile, and x86 are different with each other.

If we are sure most new archs will support devmem_is_allowed(), and at
least, 40% are the same, we can continue to consider about whether put
it in 'asm-generic' or not.


Altogether, for me, let the related declaration/implementation in
"page.h" or related header file will be fine, at least present, it is
not need to put it in 'asm-generic'.


[...]

Thanks.
-- 
Chen Gang

Open, share, and attitude like air, water, and life which God blessed

      reply	other threads:[~2014-04-16 10:11 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
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 [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=534E5741.8090908@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=dhowells@redhat.com \
    --cc=geert@linux-m68k.org \
    --cc=gxt@mprc.pku.edu.cn \
    --cc=gxt@pku.edu.cn \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=liuj97@gmail.com \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.cz \
    --cc=rientjes@google.com \
    --cc=will.deacon@arm.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).