From: Gerd Knorr <kraxel@bytesex.org>
To: linux-kernel@vger.kernel.org
Subject: Re: Problem with map_user_kiobuf() not mapping to physical memory
Date: 2 May 2001 19:17:51 GMT [thread overview]
Message-ID: <slrn9f0nav.18a.kraxel@bytesex.org> (raw)
In-Reply-To: <3AF028D3.8EE24BE1@beam.demon.co.uk>
> to the driver which performs a map_user_kiobuf() on it, the resulting
> kiobuf
> structure has all of the pagelist[] physical address entries set to the
> same value
> and the maplist[] entries set to 0. The devices access to this memory
> now
> causes system problems.
> Is map_user_kiobuf() working correctly ?
Yes, it is. You have to lock down the pages for I/O with
lock_kiovec() before using the maplist. The locking will
also fault the pages if needed.
Gerd
--
sigfault (core dumped)
prev parent reply other threads:[~2001-05-02 20:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 15:33 Problem with map_user_kiobuf() not mapping to physical memory Terry Barnaby
2001-05-02 14:34 ` Bjorn Wesen
2001-05-02 19:17 ` Gerd Knorr [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=slrn9f0nav.18a.kraxel@bytesex.org \
--to=kraxel@bytesex.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox