From: Jamie Lokier <jamie@shareable.org>
To: Jie Zhang <jie.zhang@analog.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
David Howells <dhowells@redhat.com>,
David McCullough <davidm@snapgear.com>,
Greg Ungerer <gerg@uclinux.org>, Paul Mundt <lethal@linux-sh.org>,
uclinux-dist-devel@blackfin.uclinux.org,
linux-kernel@vger.kernel.org
Subject: Re: [uClinux-dev] [PATCH] NOMMU: use copy_*_user_page() in access_process_vm()
Date: Wed, 25 Nov 2009 11:49:08 +0000 [thread overview]
Message-ID: <20091125114908.GA21778@shareable.org> (raw)
In-Reply-To: <4B0CCE4A.5000602@analog.com>
Jie Zhang wrote:
> On 11/25/2009 02:16 PM, Jamie Lokier wrote:
> >Mike Frysinger wrote:
> >>From: Jie Zhang<jie.zhang@analog.com>
> >>
> >>The mmu code uses the copy_*_user_page() variants in access_process_vm()
> >>rather than copy_*_user() as the former includes an icache flush. This is
> >>important when doing things like setting software breakpoints with gdb.
> >>So switch the nommu code over to do the same.
> >
> >Reasonable, but it's a bit subtle don't you think?
> >How about a one-line comment saying why it's using copy_*_user_page()?
> >
> >(If it was called copy_*_user_flush_icache() I wouldn't say anything,
> >but it isn't).
> >
> But I think it's well known in Linux kernel developers that
> copy_to_user_page and copy_from_user_page should do cache flushing. It's
> documented in Documentation/cachetlb.txt. I don't think it's necessary
> to replicate it here.
You're right, however I now think the commit message is misleading.
Since this is the *only place in the entire kernel* where these
functions are used (plus the mmu equivalent), I'm not sure I'd agree
about well known, and the name could be better (copy_*_user_ptrace()),
but I agree now, it doesn't need a comment.
It was the talk of icache flush which bothered me, as I (wrongly)
assumed copy_*_user_page() was used elsewhere, without knowledge of
icache vs non-icache differences - which are often the responsibility
of userspace to get right, so often the kernel does not care.
In fact, it's not just icache. copy_*_user_page() has to do some
*data* cache flushing too, on some architecures. For example, see
arch/sparc/include/asm/cacheflush_64.h:
#define copy_to_user_page(vma, page, vaddr, dst, src, len) \
do { \
flush_cache_page(vma, vaddr, page_to_pfn(page)); \
memcpy(dst, src, len); \
flush_ptrace_access(vma, page, vaddr, src, len, 0); \
} while (0)
#define copy_from_user_page(vma, page, vaddr, dst, src, len) \
do { \
flush_cache_page(vma, vaddr, page_to_pfn(page)); \
memcpy(dst, src, len); \
flush_ptrace_access(vma, page, vaddr, dst, len, 1); \
} while (0)
I'm not sure why I don't see the same dcache flushing on ARM, so I
wonder if the ARM implementation of these buggy.
Anyway, that means the commit message is a little misleading, saying
it's for the icache flush. It is for whatever icache and dcache
flushes are needed for a ptrace access.
Which is why, given they are only used for ptrace (have just grepped),
I'm inclined to think it'd be clearer to rename the functions to
copy_*_user_ptrace(). And make your no-mmu change of course :-)
Any thoughts on the rename?
-- Jamie
next prev parent reply other threads:[~2009-11-25 11:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 5:55 [PATCH] NOMMU: use copy_*_user_page() in access_process_vm() Mike Frysinger
2009-11-25 6:16 ` [uClinux-dev] " Jamie Lokier
2009-11-25 6:27 ` Jie Zhang
2009-11-25 6:51 ` Paul Mundt
2009-11-25 11:49 ` Jamie Lokier [this message]
2009-11-25 14:14 ` Jie Zhang
2009-11-25 18:39 ` Mike Frysinger
2009-11-25 6:19 ` David McCullough
2009-11-25 23:22 ` Greg Ungerer
2009-12-02 14:36 ` David Howells
2009-12-02 15:00 ` Jie Zhang
2009-12-02 14:45 ` David Howells
2009-12-02 15:07 ` Jie Zhang
2009-12-08 10:57 ` David Howells
2009-12-08 13:37 ` Jie Zhang
2009-12-08 14:19 ` David Howells
2009-12-08 14:30 ` Jie Zhang
2009-12-09 0:27 ` Mike Frysinger
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=20091125114908.GA21778@shareable.org \
--to=jamie@shareable.org \
--cc=davidm@snapgear.com \
--cc=dhowells@redhat.com \
--cc=gerg@uclinux.org \
--cc=jie.zhang@analog.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
--cc=uclinux-dist-devel@blackfin.uclinux.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.