mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen.5i5j@gmail.com>
To: Hans-Christian Egtvedt <egtvedt@samfundet.no>
Cc: "Håvard Skinnemoen" <hskinnemoen@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arch/avr32/mm/cache.c: export symbol flush_icache_range() for module using
Date: Sun, 23 Mar 2014 07:12:46 +0800	[thread overview]
Message-ID: <532E18EE.3090008@gmail.com> (raw)
In-Reply-To: <5324C3B2.1000802@gmail.com>


Is this patch OK?

If it is necessary to continue analysing more details, please let me
know, and I will/should continue.

Thanks.

On 03/16/2014 05:18 AM, Chen Gang wrote:
> On 03/09/2014 11:19 PM, Chen Gang wrote:
>> On 03/09/2014 06:17 AM, Hans-Christian Egtvedt wrote:
>>> Around Sun 09 Mar 2014 05:47:04 +0800 or thereabout, Chen Gang wrote:
>>>>
>>>> After this patch, our linux kernel can pass "avr32-linux-" allmodconfig
>>>> (it contents quite a few of warnings, but after check, I guess they are
>>>> not kernel's issue).
>>>
>>> That sounds great, I am a bit surprised however that the lkdtm module need
>>> flush_icache_range. Would have been interesting to look into what causes this
>>> dependency.
>>>
> 
> After read a little more details for lkdtm, I guess "after overwrite an
> executable area by do_nothing(), it needs flush_icache_range() to be
> sure the new instructions/data must have effect with all cpu".
> 
> Welcome any additional information for it.
> 
> Thanks.
> 
>>
>> "driver/misc/lkdtm.c" will use this flush_icache_range().
>>
>> And some architectures export it to modules.
>>
>>   [root@gchen arch]# grep -rn flush_icache_range * | grep EXPORT
>>   arm64/mm/flush.c:105:EXPORT_SYMBOL(flush_icache_range);
>>   avr32/mm/cache.c:114:EXPORT_SYMBOL(flush_icache_range);
>>   m68k/mm/cache.c:106:EXPORT_SYMBOL(flush_icache_range);
>>   mn10300/mm/cache-inv-icache.c:129:EXPORT_SYMBOL(flush_icache_range);
>>   mn10300/mm/cache-flush-icache.c:155:EXPORT_SYMBOL(flush_icache_range);
>>   sparc/mm/init_64.c:435:EXPORT_SYMBOL(flush_icache_range);
>>
>>
>> Welcome any more details information by any other members, thanks.
>>
>>
> 
> Thanks.
> 


-- 
Chen Gang

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

  reply	other threads:[~2014-03-22 23:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-08 21:35 Chen Gang
2014-03-08 21:47 ` Chen Gang
2014-03-08 22:17   ` Hans-Christian Egtvedt
2014-03-09 15:19     ` Chen Gang
2014-03-15 21:18       ` Chen Gang
2014-03-22 23:12         ` Chen Gang [this message]
2014-03-25  8:48           ` Hans-Christian Egtvedt
2014-03-25  8:51             ` 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=532E18EE.3090008@gmail.com \
    --to=gang.chen.5i5j@gmail.com \
    --cc=egtvedt@samfundet.no \
    --cc=hskinnemoen@gmail.com \
    --cc=linux-kernel@vger.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

Powered by JetHome