Re: memory descriptor of threads

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

 



On Thursday 10 November 2005 09:32, Thomas Petazzoni wrote:

> > I mean local variable allocated inside each function!!!
> 
> Ok, so it has nothing to do with TLS. They are allocated on the stack.
> 
> What do you want to do, and why ? I don't understand what's the goal of
> what you exposed in your original mail. Can you provide us more details ?

I try to better explain my goal.
I'm developing a LKM to monitor threads sharing the same memory descriptor.
I set this descriptor (or parts of it) as not writable and then catch the page 
fault exception caused by one (or more) threads when trying to write on it.
The problem is that I've to catch only page fault exception caused by accesses 
to global variable and not by accesses to local variables of each thread.
To do this, I've to know precisely what are the vmas of the shared memory 
descriptor in which are stored the local data of threads.
I've thought that these vmas are the ones that begin with 'b' character but 
I'm not really sure.

I hope my explanation is clear.
Thanks.
Vincenzo Mallozzi.

	

	
		
___________________________________ 
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB 
http://mail.yahoo.it


--
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