From: Matthew Wilcox <willy@debian.org>
To: "David S. Miller" <davem@redhat.com>
Cc: willy@debian.org, alan@lxorguk.ukuu.org.uk, rmk@arm.linux.org.uk,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] shmem missing cache flush
Date: Tue, 29 Oct 2002 21:52:30 +0000 [thread overview]
Message-ID: <20021029215230.K27461@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <20021028.085851.94768450.davem@redhat.com>; from davem@redhat.com on Mon, Oct 28, 2002 at 08:58:51AM -0800
On Mon, Oct 28, 2002 at 08:58:51AM -0800, David S. Miller wrote:
> From: Matthew Wilcox <willy@debian.org>
> Date: Mon, 28 Oct 2002 17:06:33 +0000
>
> On Mon, Oct 28, 2002 at 08:55:36AM -0800, David S. Miller wrote:
> > Need to go into the revision history, discover who added these
> > calls, and ask them why they were added.
>
> They're in 2.2.20, if it helps...
>
> That's not so useful, it's the who and why that matters. :-)
Well, that's kind of hard... which revision history? They were
added at some point during 2.1, before anyone but sparc64 supported
flush_dcache_page, and certainly long before cachetlb.txt was written.
Arguably, cachetlb.txt is the buggy one since it coopted this interface
without reference to the current users.
PA-RISC doesn't use a.out in any way, shape or form, so it doesn't
matter to me, but m68k might like it fixed, i guess. Why the calls are
there seems fairly straightforward -- we're effectively doing a read()
of the text segment into the process' address space, and we're about to
execute it.
So flush_icache_user_range() seems like the right thing to do there.
Except that cachetlb says it can't cross a page boundary. Maybe the
right thing to do is to change the definition of flush_icache_range in
cachetlb to indicate that the addresses are user, not kernel, addresses;
remove the flush_icache_range() in kernel/module.c and put a #error into
every arch's module_arch_init() warning them they may need to flush the
range mod to mod->size.
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-10-29 21:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 18:26 [PATCH] shmem missing cache flush Matthew Wilcox
2002-10-16 23:57 ` Hugh Dickins
2002-10-16 23:58 ` David S. Miller
2002-10-17 0:19 ` Russell King
2002-10-17 0:16 ` David S. Miller
2002-10-21 15:04 ` Alan Cox
2002-10-21 15:21 ` David S. Miller
2002-10-21 16:12 ` Alan Cox
2002-10-28 14:10 ` David S. Miller
2002-10-28 14:32 ` Matthew Wilcox
2002-10-28 14:26 ` David S. Miller
2002-10-28 16:36 ` Matthew Wilcox
2002-10-28 16:55 ` David S. Miller
2002-10-28 17:06 ` Matthew Wilcox
2002-10-28 16:58 ` David S. Miller
2002-10-29 21:52 ` Matthew Wilcox [this message]
2002-10-28 17:08 ` Alan Cox
2002-10-28 16:52 ` Matthew Wilcox
2002-10-28 14:35 ` Hugh Dickins
2002-10-28 14:26 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2002-10-28 16:50 Manfred Spraul
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=20021029215230.K27461@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
/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