Skip to contentSkip to conversation

Problem with map_user_kiobuf() not mapping to physical memory

DISCUSSION Terry Barnaby 3 participants 3 messages May 2, 2001

lore
Share & tools
lore
#0 lore raw

We are developing a Linux driver which allows a device to read/write directly
into a processes virtual memory space.
I have a question on using map_user_kiobuf() as we are having problems. I was under the impression that if I used map_user_kiobuf() this would map
the users virtual address space into locked physical memory pages so that
I/O could be performed.
However, I note that if the user just mallocs memory and does not access it
(No physical memory pages created) and then passes this virtual address space
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 ?
Should I call some function to map the virtual address space into physical memory
or at least pages before I call map_user_kiobuf() ?

Cheers

Terry

--

  Dr Terry Barnaby                     BEAM Ltd
  Phone: +44 1454 324512               Northavon Business Center, Dean Rd
  Fax:   +44 1454 313172               Yate, Bristol, BS37 5NH, UK
  Email: [email protected]        Web: www.beam.demon.co.uk

BEAM for: Visually Impaired X-Terminals, Parallel Processing, Software Dev
"Tandems are twice the fun !"

#1 lore raw
Quoted 7 lines · Terry Barnaby

However, I note that if the user just mallocs memory and does not access it
(No physical memory pages created) and then passes this virtual address space
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

Quoted 8 lines

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 ?
Should I call some function to map the virtual address space into physical memory
or at least pages before I call map_user_kiobuf() ?

No.. but you might just have done something wrong.

See the example in arch/cris/drivers/examples/kiobuftest.c

(that example does not deallocate the vectors properly IIRC, but the actual kiobuf mapping sequence should work)

/BW

#2 lore raw
In reply to Terry Barnaby
Quoted 8 lines

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

Signature · 1 line
sigfault (core dumped)