* Ingo Molnar ([email protected]) 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).
Mathieu
OpenPGP public key: http://krystal.dyndns.org:8080/key/compudj.gpg
Key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
