From: Matthew Wilcox <willy@debian.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Matthew Wilcox <willy@debian.org>,
"David S. Miller" <davem@redhat.com>,
rmk@arm.linux.org.uk, hugh@veritas.com, akpm@zip.com.au,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] shmem missing cache flush
Date: Mon, 28 Oct 2002 16:52:57 +0000 [thread overview]
Message-ID: <20021028165257.Q27461@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <1035824897.1945.29.camel@irongate.swansea.linux.org.uk>; from alan@lxorguk.ukuu.org.uk on Mon, Oct 28, 2002 at 05:08:17PM +0000
On Mon, Oct 28, 2002 at 05:08:17PM +0000, Alan Cox wrote:
> Suppose those addresses are already in the userspace icache from a
> different exec ?
Documentation/cachetlb.txt:
void flush_icache_range(unsigned long start, unsigned long end)
When the kernel stores into addresses that it will execute
out of (eg when loading modules), this function is called.
If the icache does not snoop stores then this routine will need
to flush it.
void flush_icache_user_range(struct vm_area_struct *vma,
struct page *page, unsigned long addr, int len)
This is called when the kernel stores into addresses that are
part of the address space of a user process (which may be some
other process than the current process). The addr argument
gives the virtual address in that process's address space,
page is the page which is being modified, and len indicates
how many bytes have been modified. The modified region must
not cross a page boundary. Currently this is only called from
kernel/ptrace.c.
so either they're using the wrong function or these calls aren't needed
for some other reason (eg, the update_mmu_cache() thing davem suggested
earlier).
--
Revolutions do not require corporate support.
next prev parent reply other threads:[~2002-10-28 16: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
2002-10-28 17:08 ` Alan Cox
2002-10-28 16:52 ` Matthew Wilcox [this message]
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=20021028165257.Q27461@parcelfarce.linux.theplanet.co.uk \
--to=willy@debian.org \
--cc=akpm@zip.com.au \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=davem@redhat.com \
--cc=hugh@veritas.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