public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Philipp Rumpf <prumpf@parcelfarce.linux.theplanet.co.uk>
To: Anders Torger <torger@ludd.luth.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: How to transfer memory from PCI memory directly to user space safely and portable?
Date: Sun, 26 Nov 2000 15:11:20 +0000	[thread overview]
Message-ID: <20001126151120.V2272@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <00112614213105.05228@paganini>
In-Reply-To: <00112614213105.05228@paganini>; from torger@ludd.luth.se on Sun, Nov 26, 2000 at 02:21:31PM +0100

On Sun, Nov 26, 2000 at 02:21:31PM +0100, Anders Torger wrote:
> 	memcpy_toio(iobase, user_space_src, count);

I hope count isn't provided by userspace here ?

> 1. What happens if the user space memory is swapped to disk? Will 
> verify_area() make sure that the memory is in physical RAM when it returns, 
> or will it return -EFAULT, or will something even worse happen?

On i386, you'll sleep implicitly waiting for the page fault to be handled;  in
the generic case, anything could happen.

> 2. Is this code really portable? I currently have an I386 architecture, and I 
> could use copy_to/from_user on that instead, but that is not portable. Now, 
> by using memcpy_to/fromio instead, is this code fully portable?

No.  It would be portable if you were using memcpy_fromuser_toio and it
existed.

> 3. Will the current process always be the correct one? The copy functions is 
> directly initiated by the user, and not through an interrupt, so I think the 
> user space mapping will always be to the correct process. Is that correct?

current should be fine if you're not in a bh/interrupt/kernel thread.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-11-26 15:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 13:21 How to transfer memory from PCI memory directly to user space safely and portable? Anders Torger
2000-11-26 15:11 ` Philipp Rumpf [this message]
2000-11-26 15:36   ` Anders Torger
2000-11-27 18:36   ` H. Peter Anvin
2000-11-27 19:29     ` Philipp Rumpf
2000-11-27 19:30       ` H. Peter Anvin
2000-11-27 13:51 ` Richard B. Johnson
  -- strict thread matches above, loose matches on Subject: below --
2000-11-27 13:27 aprasad
2000-11-26 13:54 ` Anders Torger

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=20001126151120.V2272@parcelfarce.linux.theplanet.co.uk \
    --to=prumpf@parcelfarce.linux.theplanet.co.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torger@ludd.luth.se \
    /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