Re: [PATCH 1/9] ARM: Do early I/O mapping if spinlock debugging is enabled

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* David Brownell <david-b@xxxxxxxxxxx> [090128 15:51]:
> On Wednesday 28 January 2009, Russell King - ARM Linux wrote:
> > > 
> > > At least on OMAP, sched_clock() requires the I/O maps to be initialized.
> > > Spinlock debugging invokes sched_clock() very early.
> > 
> > NAK.  This doesn't and can't work on every platform out there.  The
> > only viable fix is that sched_clock() must NOT be used early.
> > 
> > If the kernel is using sched_clock() early, that's a bug.
> 
> So you're saying that spinlock debugging is buggy???

It used to be that CONFIG_PRINTK_TIME had a similar issue..
Anyways, dropping this patch from omap-fixes, sounds like
how to fix it needs to get sorted out on LKML.

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux