I sent 3 identical emails to the list because hotmail does not acknowledge them.
I am sorry.
PAP
___
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
http://lists.kernelnewbies.org/mailman/listinfo/kerne
Hi:
It is well know that is not recomended to keep a spinlock locked during
operations that can be preempted. Some of these operations are copy_to_user,
copy_from_user.
Below is the code of the write_lock() as a sample.
340 static inline void __write_lock(rwlock_t *lock)
341{
342pr
Hi:
It is well know that is not recomended to keep a spinlock locked during
operations that can be preempted. Some of these operations are copy_to_user,
copy_from_user.
Below is the code of the write_lock() as a sample.
340 static inline void __write_lock(rwlock_t *lock)
341{
342pr
Hi:
It is well know that is not recomended to keep a spinlock locked during
operations that can be preempted. Some of these operations are copy_to_user,
copy_from_user.
Below is the code of the write_lock() as a sample.
340 static inline void __write_lock(rwlock_t *lock)
341{
342pr
Hi:
I want to add a new a new kernel function:
get_user_pages_fast2() based on get_user_pages_fast() for other process than
"current". Does anybody has any consideration or warning to tell me.
Thanks in advance.
Pablo Pessolani
om
> To: ppessol...@hotmail.com
> Date: Thu, 6 Dec 2012 10:30:27 +0100
> CC: kernelnewbies@kernelnewbies.org
>
> Hi,
>
> Le mercredi 05 décembre 2012 à 22:47 -0300, Pablo Pessolani a écrit :
> > Hi:
> > I am working on a project to copy (page aligned) the
> &g
Hi:
> This sounds a lot like "Cross Memory Support" (eg CROSS_MEMORY_ATTACH
> option) introduced in Linux 3.2:
>
> http://kernelnewbies.org/Linux_3.2#head-a5e26c6275e85a5c9c41873fbab96bd38d934b72
>
> Cross Memory Support add two syscalls:
> - process_vm_readv() : read from a process memory
>
cribed to the mailing list, please CC: the answers to this email
account.
Thanks in Advance.
I apologize for my basic English.
Pablo Pessolani
PD: on
