On Sun, 2006-10-08 at 13:39 -0700, Daniel Walker wrote:
> > The reason why this was delayed into late boot is simply that the
> > unstable, unsynchronized TSC's made way too much trouble and the pmtimer
> > can not be initialized early.
> >
> > I'm not going to accept that. Your change might work on 5 machines you
> > have tested on, but we start over with the same breakage we solved
> > already.
>
> Your going to have to explain the breakage further. I don't recall
> seeing any discussion on this.
See above, but I'm happy to copy it.
> > The reason why this was delayed into late boot is simply that the
> > unstable, unsynchronized TSC's made way too much trouble and the pmtimer
> > can not be initialized early.
I don't have the bug reports handy, but they are in the LKML archives.
> > This early boot instrumentation code can work with low resolution time
> > information quite well and none of the boot code does need any high res
> > time information. Boot code is different from a running system and has
> > different requirements.
> >
> > This is a solution for a nonexisting problem, which just brings back
> > already solved ones.
>
> There is at least one existing problem which it does solve.
Which one exactly? I'm not aware of a problem with the existing code at
all.
> How about we
> discuss the early TSC boot breakage, which you mention above, so I can
> properly fix this situation.
See above. Also it interferes probably with the highres/dyntick code, as
we might switch over way too early. Have not looked into that yet.
tglx
-
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]
