Re: why "__put_user_8" but no "__get_user_8" on i386?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 7 Jan 2007, Mulyadi Santosa wrote:

> Hi...
>
> >   is there some reason that include/asm-i386/uaccess.h defines
> > __get_user_x up to 4, but __put_user_x up to 8?  why no __get_user_8?
> > just curious.
>
> Sure about that? Maybe the get_user 64 bit can do 8 byte transfer? I
> have no source in hand right now, so I just give ideas...
>
> Another possibilty is, there isn't one, since the kernel assume it
> can't do 8 bytes transfer atomically at once. But the kernel can
> assume it can safely do so since it *knows* the proper locking has
> been done.

i have no idea, i'm just pointing out what i can read in that header
file.

rday

p.s.  i'm also amused by the fact that the generic routine for
*getting* is "get_user_x", but for *putting* is "put_user_X" (note
difference in case for that last character).

is that difference supposed to mean something?

rday

--
Kernelnewbies: Help each other learn about the Linux kernel.
Archive:       http://mail.nl.linux.org/kernelnewbies/
FAQ:           http://kernelnewbies.org/faq/


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux