On Thu, Aug 04, 2005 at 04:06:20PM +0200, Andi Kleen wrote:
> On Thu, Aug 04, 2005 at 07:04:45AM -0700, Tom Rini wrote:
> > On Thu, Aug 04, 2005 at 02:39:00PM +0200, Andi Kleen wrote:
> > > > > That doesn't make much sense here. tasklet will only run when interrupts
> > > > > are enabled, and that is much later. You could move it to there.
> > > >
> > > > Where? Keep in mind it's really only x86_64 that isn't able to break
> > > > sooner.
> > >
> > > The local_irq_enable() call in init/main.c:start_kernel()
> >
> > But as I say, only x86_64 needs this kind of delay.
>
> I don't think that's correct. Interrupts should be disabled on all
> architectures until that.
Right, but we can run sooner elsewhere. It's only x86_64 where we can't
run when our commandline bits are parsed and need to wait.
--
Tom Rini
http://gate.crashing.org/~trini/
-
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]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
| |
 |