Ingo Molnar <[email protected]> wrote:
> i agree that we should do this in one go and in Linus' tree. I suspect
> David has a script for this, so we can do it anytime for any tree,
> right?
I wish. No, it's not simple enough to script. All the usages of struct
pt_regs have to be eyeballed and have to be poked with the compiler. The
problem is when an interrupt handler passes regs down to someone else - that I
can't find.
However, I'm now in a position that I can just keep pulling Linus's GIT tree
with StGIT and fixing up the wibbly bits and grepping for new instances of
pt_regs and of course compile testing on a bunch of arches for which I have
compilers.
> the amount of code that truly relies on regs being present is very low.
The same goes for the IRQ number itself too. Very few things actually use
that, mostly they just use the arbitrary data argument. I'm not sure we want
to do the same to that, though, since it makes cascaded PIC processing more
interesting as the IRQ number changes.
David
-
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]
