[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lknsotnj.fsf@duaron.myhome.or.jp>
Date: Sun, 08 Oct 2006 03:41:36 +0900
From: OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
To: Daniel Walker <dwalker@...sta.com>
Cc: akpm@...l.org, linux-kernel@...r.kernel.org, johnstul@...ibm.com
Subject: Re: [PATCH 01/10] -mm: clocksource: increase initcall priority
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp> writes:
> Daniel Walker <dwalker@...sta.com> writes:
>
>> On Sun, 2006-10-08 at 00:40 +0900, OGAWA Hirofumi wrote:
>>> Daniel Walker <dwalker@...sta.com> writes:
>>>
>>> > Index: linux-2.6.17/drivers/clocksource/acpi_pm.c
>>> > ===================================================================
>>> > --- linux-2.6.17.orig/drivers/clocksource/acpi_pm.c
>>> > +++ linux-2.6.17/drivers/clocksource/acpi_pm.c
>>> > @@ -174,4 +174,4 @@ pm_good:
>>> > return clocksource_register(&clocksource_acpi_pm);
>>> > }
>>> >
>>> > -module_init(init_acpi_pm_clocksource);
>>> > +postcore_initcall(init_acpi_pm_clocksource);
>>>
>>> Current code is assumeing DECLARE_PCI_FIXUP_EARLY() is called before
>>> init_acpi_pm_clocksource().
>>>
>>> We'll need to change it.
>>
>> We can add a call to clocksource_rating_change() inside
>> acpi_pm_need_workaround(), are there deeper dependencies?
>
> There is no deeper dependencies. If it's meaning
> clocksource_reselect() in current git, it sounds good to me.
Ah, I was forgetting why I didn't before. If it's a buggy pmtmr, we'll
get corrupted time until re-selecting the clocksource.
If anybody doesn't care this will be good with it. If not, we would
need to back to old one. IIRC, John did it.
--
OGAWA Hirofumi <hirofumi@...l.parknet.co.jp>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists