From: "Bob Picco" <bob.picco@hp.com>
To: john stultz <johnstul@us.ibm.com>
Cc: "Luck, Tony" <tony.luck@intel.com>,
Paolo Ornati <ornati@fastwebnet.it>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Bob Picco <bob.picco@hp.com>
Subject: Re: "double" hpet clocksource && hard freeze [bisected]
Date: Thu, 23 Aug 2007 17:38:49 -0400 [thread overview]
Message-ID: <20070823213849.GA7617@localhost> (raw)
In-Reply-To: <1187903135.6024.18.camel@localhost.localdomain>
john stultz wrote: [Thu Aug 23 2007, 05:05:35PM EDT]
> On Thu, 2007-08-23 at 13:41 -0700, Luck, Tony wrote:
> > > I have a double "hpet" entry in "available_clocksource":
> > > $ cat /sys/devices/system/clocksource/clocksource0/available_clocksource
> > > tsc hpet hpet acpi_pm jiffies
> >
> > Oops. If seems that both drivers/char/hpet.c and arch/x86_64/kernel/hpet.c
> > both register a clocksource named "hpet". Probably a result of bringing
> > back to life a long lost patch, and having someone else (John Stultz, according
> > to git blame) make a similar change to a different file in the intervening
> > time.
> >
> > Presumably the thing to do would be merge the x86_64 specific version
> > into the drivers/char/hpet.c version?
>
> Ugh. Yea. i386 has an hpet clocksource as well. We should kill the
> duplication, but at the moment I'm not comfortable that the
> driver/char/hpet.c is ok to be used for i386/x86_64 (Bob: Do you know
> why the shift value is only 10?).
No I don't have a clue why Pete chose this value.
>
>
> I'm a little surprised by this, as the clocksource code use to prevent
> duplicate named clocksources from being registered, so I'm not sure how
> that check got dropped. Also I'm not quite sure I see where the hard
> freeze is coming from.
>
> My initial reaction would be to either ifdef ia64 implementation in
> drivers/char/hpet.c or move the code under the ia64 arch dir until it is
> really usable by all arches.
>
> Bob, your thoughts?
It appears the ACPI for this platform might work. We don't know because
of a hpet driver probe error discussed below. I assume you're suggesting
the driver is only required by ia64? I think that might not be true.
Well I'm slightly confused. The fs_initcall was first into hpet_alloc.
It appears ACPI discovery failed during driver initialization because
of:
hpet_resources: 0xfed00000 is busy
from dmesg. So why do we have a second hpet registered? Also hpet_alloc
is suspose to check for redundant registration. I need to look more
tomorrow.
>
bob
next prev parent reply other threads:[~2007-08-23 21:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 20:21 "double" hpet clocksource && hard freeze [bisected] Paolo Ornati
2007-08-23 20:22 ` Paolo Ornati
2007-08-23 20:41 ` Luck, Tony
2007-08-23 21:05 ` john stultz
2007-08-23 21:38 ` Bob Picco [this message]
2007-08-24 7:03 ` Paolo Ornati
2007-08-23 21:41 ` john stultz
2007-08-24 7:01 ` Paolo Ornati
2007-08-24 12:46 ` Bob Picco
2007-08-24 13:27 ` Paolo Ornati
2007-08-24 16:04 ` Luck, Tony
2007-08-24 16:13 ` Paolo Ornati
2007-08-24 18:17 ` john stultz
2007-08-27 20:34 ` Luiz Fernando N. Capitulino
2007-08-27 21:39 ` john stultz
2007-08-28 6:07 ` Paolo Ornati
2007-08-24 9:03 ` Paolo Ornati
2007-08-24 18:43 ` john stultz
-- strict thread matches above, loose matches on Subject: below --
2007-08-28 8:27 Clemens Ladisch
2007-08-28 20:21 ` Paolo Ornati
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070823213849.GA7617@localhost \
--to=bob.picco@hp.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ornati@fastwebnet.it \
--cc=tony.luck@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox