On Wednesday 23 August 2006 11:01, Zachary Amsden wrote:
> Andi Kleen wrote:
> >> Yes, after discussion with Rusty, it appears that beefing up
> >> stop_machine_run is the right way to go. And it has benefits for
> >> non-paravirt code as well, such as allowing plug-in kprobes or oprofile
> >> extension modules to be loaded without having to deal with a debug
> >> exception or NMI during module load/unload.
> >>
> >
> > I'm still unclear where you think those debug exceptions will come from
>
> kprobes set in the stop_machine code - which is probably a really bad
> idea, but nothing today actively stops kprobes from doing that.
kprobes don't cause any debug exceptions. You mean int3?
Anyways this can be fixed by marking the stop machine code __kprobes
-Andi
-
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]
