From: Dan Malek <dan@netx4.com>
To: Tom Roberts <tjroberts@lucent.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Curious limitation in copy_from_user()
Date: Fri, 26 May 2000 16:54:55 -0400 [thread overview]
Message-ID: <392EE49F.234413C5@embeddededge.com> (raw)
In-Reply-To: 392EDED5.33749798@lucent.com
Tom Roberts wrote:
>
> While porting Linux PPC to my hardware, I discovered a curious
> limitation in copy_from_user() -- it cannot handle uncached memory.
Yeeup. We have discussed that before. The later/newer kernels trap
this fault and emulate the data move. Although there are some cases
as you just discovered, the larger sample indicated access to uncached
memory spaces required special handling so this wasn't going to be
a problem.
The only choice is to not take advantage of the performance enhancements,
which didn't seem like a good thing. In your case, you will have to write
your own function to validate the user buffer space and then copy the
data in a loop. Perhaps we need a copy_from_user_uncached() or
something.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2000-05-26 20:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-26 20:30 Curious limitation in copy_from_user() Tom Roberts
2000-05-26 20:54 ` Dan Malek [this message]
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=392EE49F.234413C5@embeddededge.com \
--to=dan@netx4.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=tjroberts@lucent.com \
/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;
as well as URLs for NNTP newsgroup(s).