Cc: Chris Wright <chrisw@...>, Andi Kleen <andi@...>, Ingo Molnar <mingo@...>, Andrew Morton <akpm@...>, <linux-kernel@...>, Thomas Gleixner <tglx@...>, Arjan van de Ven <arjan@...>
I think it should be.
That big patch really does do a *lot* more than just the "clockevents
conversion". It does all the hpet clock setup changes etc that are about
the hardware, and have *nothing* to do with actually changing the
interfaces.
For example, look at the hpet.c part of that patch. Totally independent
cleanups of everything else.
Or look at the changes to __setup_APIC_LVTT(). Same thing.
All the actual hardware interface changes are *totally* independent of the
software interface changes, and a lot of them are just cleanups.
But those hardware interface changes are easily the things that can break,
where some cleanup results in register writes being done in a different
order or something, and so if there's a bug there (and it's not visible on
most setups), now you cannot tell where the bug is.
Another example: setup_APIC_timer() used to wait for a timer interrupt
trigger to happen on the i8259 timer (or HPET). That code just got
removed (or maybe it got moved so subtly that I just don't see it).
What has that got to do with switching from the old timer interface to the
new one?
NOTHING.
So those kinds of changes that change hardware access functions should
have been done separately. Maybe there's a machine where that early
synchronization was necessary for some subtle timing reason. If so,
removing it sounds like a bug, no? Wouldn't it have been nice to see that
removal as a separate patch that was independent of the interface switch-
over?
I'd be a *lot* happier with switching over interfaces if I thought that
the low-level hardware drivers didn't change at the same time. But they
*do* change, afaik.
Linus
-
