Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Cc: linux-mips@linux-mips.org
Subject: Re: flush_kernel_dcache_page() not needed ?
Date: Tue, 04 Sep 2007 16:05:10 +0200	[thread overview]
Message-ID: <46DD6616.6030303@gmail.com> (raw)
In-Reply-To: <20070904.225402.106261140.anemo@mba.ocn.ne.jp>

Atsushi Nemoto wrote:
> On Tue, 04 Sep 2007 14:46:54 +0200, Franck Bui-Huu <vagabon.xyz@gmail.com> wrote:
>>> I'll look at it further, but any testcase are welcome.
> 
> I found the reason.
> 
> do_execve()
>   copy_strings()
>     flush_kernel_dcache_page()
>   search_binary_handler()
>     load_elf_binary()
>       setup_arg_pages()
>         shift_arg_pages()
>           move_page_tables()
>             flush_cache_range()
> 
> And MIPS flush_cache_range() blasts whole dcache!  That's why empty
> flush_kernel_dcache_page() was enough for now.  

Yeah, that what I think too and that's also why I was suggesting to
test a plain 2.6.23-rc5 with the randomize_va_space=0. Please see my
previous reply...

Could you give it a try ?

		Franck

  reply	other threads:[~2007-09-04 14:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 12:25 flush_kernel_dcache_page() not needed ? Franck Bui-Huu
2007-08-31 14:50 ` Markus Gothe
2007-08-31 15:04   ` Franck Bui-Huu
2007-08-31 23:42   ` Ralf Baechle
2007-09-02 21:12     ` Markus Gothe
2007-08-31 14:54 ` Markus Gothe
2007-09-03 13:52 ` Atsushi Nemoto
2007-09-03 15:36   ` Franck Bui-Huu
2007-09-03 15:54     ` Atsushi Nemoto
2007-09-04 12:46       ` Franck Bui-Huu
2007-09-04 13:54         ` Atsushi Nemoto
2007-09-04 14:05           ` Franck Bui-Huu [this message]
2007-09-04 14:16             ` Atsushi Nemoto
2007-09-04 14:17               ` Franck Bui-Huu
2007-09-05 15:33         ` Atsushi Nemoto
2007-09-07  9:00           ` Franck Bui-Huu
2007-09-14  8:32           ` Franck Bui-Huu
2007-09-14 14:29             ` Atsushi Nemoto
2007-09-14 15:47               ` Franck Bui-Huu

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=46DD6616.6030303@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=anemo@mba.ocn.ne.jp \
    --cc=linux-mips@linux-mips.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