On 2/8/08, Andi Kleen <andi@firstfloor.org> wrote:Yes, this is true. I cannot guarantee that there are no other instructions that could access more than one memory location but only take one page fault. However, since the kernel does boot, we at least know that these instructions are not very frequently used. (If you know of any other instructions we might be missing, I'll be happy to know about it!) There is also the point that if kmemcheck doesn't handle all the faulting addresses, it will simply fault again and again, without making any progress. I mean, it won't go unnoticed for very long :-) This is also why we depend on M386 and !X86_GENERIC, to avoid those MMX, etc. instructions, as we have no support for those currently. Sincerely, Vegard Nossum --
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Steven Rostedt | Re: Major regression on hackbench with SLUB |
| Nick Piggin | 2.6.24-rc2 slab vs slob tbench numbers |
| Paul Jackson | Re: cpuset-remove-sched-domain-hooks-from-cpusets |
git: | |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
