This is the mail archive of the mailing list for the systemtap project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Linux Kernel Markers 0.5 for Linux 2.6.17 (with probe management)

* Ingo Molnar ( wrote:
> > 
> > Yes, sorry, my mistake. This kind of fault is not as infrequent as you 
> > may think, as every newly allocated vmalloc region will cause vmalloc 
> > faults on every processes on the system that are trying to access 
> > them. I agree that it should not be a standard event people would be 
> > interested in.
> most of the vmalloc area that is allocated on a typical system are 
> modules - and they get loaded on bootup and rarely unloaded. Even for 
> other vmalloc-ed areas like netfilter, the activation of them is during 
> bootup. So from that point on the number of vmalloc faults is quite low. 
> (zero on most systems) If you still want to trace it i'd suggest a 
> separate type of event for it.

Yes, with this typical vmalloc usage pattern in perspective, we completely
agree. We also agree on having a separate kind of event for this, as it requires
the tracer code to be vmalloc-fault-reentrant (very tricky).


OpenPGP public key:    
Key fingerprint:     8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68 

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]