From: David Miller <davem@davemloft.net>
To: johnstul@us.ibm.com
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
andreas.friedrich@fujitsu-siemens.com, tglx@linutronix.de,
dwalker@mvista.com
Subject: Re: [PATCH -mm][Take 2] clocksource init adjustments (fix bug #7426)
Date: Fri, 02 Mar 2007 15:30:45 -0800 (PST) [thread overview]
Message-ID: <20070302.153045.71090285.davem@davemloft.net> (raw)
In-Reply-To: <1172877840.5449.39.camel@localhost.localdomain>
From: john stultz <johnstul@us.ibm.com>
Date: Fri, 02 Mar 2007 15:24:00 -0800
> On Fri, 2007-03-02 at 12:32 -0800, David Miller wrote:
> > From: john stultz <johnstul@us.ibm.com>
> > Date: Fri, 02 Mar 2007 11:58:11 -0800
> >
> > > Oh! Sorry! Yea, looking at it more the ioremap isn't actually necessary,
> > > as we can use hpet_readl() instead of re-calculating the hpet base
> > > address pointer.
> > >
> > > I'll fix this up (and find an HPET enabled x86_64 box to test it on) and
> > > get a patch to you shortly.
> >
> > Not to pressure you John but I'd really like to see this go
> > in soon, it does fix real bugs such as the Radeon FB issue
> > I pointed out the other week.
>
> Here's my second try at this. This time I caught three bugs from the
> last patch (all in x86_64):
> 1) Calling ioremap too early in the HPET code (which is unnecessary)
> 2) hpet_period local variable aliasing
> 3) forgot to re-add call to init_tsc_clocksource()
>
> I boot tested on two x86_64 boxes (one ACPI PM and the other HPET).
> However it probably should still go through a bit of testing in -mm to
> make sure all the quirks are shaken out.
Agreed and it looks good to me after going over it a few times.
next prev parent reply other threads:[~2007-03-02 23:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 0:13 [PATCH -mm] clocksource init adjustments (fix bug #7426) john stultz
2007-03-02 10:18 ` Andrew Morton
2007-03-02 19:58 ` john stultz
2007-03-02 20:32 ` David Miller
2007-03-02 23:24 ` [PATCH -mm][Take 2] " john stultz
2007-03-02 23:30 ` David Miller [this message]
2007-03-04 16:25 ` Daniel Walker
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=20070302.153045.71090285.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@osdl.org \
--cc=andreas.friedrich@fujitsu-siemens.com \
--cc=dwalker@mvista.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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