[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20070201135936.GQ21755@dwarf.suse.cz>
Date: Thu, 1 Feb 2007 14:59:36 +0100
From: Jiri Bohac <jbohac@...e.cz>
To: Andi Kleen <ak@...e.de>
Cc: Jiri Bohac <jbohac@...e.cz>, linux-kernel@...r.kernel.org,
Vojtech Pavlik <vojtech@...e.cz>, ssouhlal@...ebsd.org,
arjan@...radead.org, tglx@...utronix.de, johnstul@...ibm.com,
zippel@...ux-m68k.org, andrea@...e.de
Subject: Re: [patch 2/9] Remove the support for the VXTIME_PMTMR timer mode
On Thu, Feb 01, 2007 at 02:13:00PM +0100, Andi Kleen wrote:
> On Thursday 01 February 2007 14:13, Jiri Bohac wrote:
> > On Thu, Feb 01, 2007 at 12:13:31PM +0100, Andi Kleen wrote:
> > > On Thursday 01 February 2007 10:59, jbohac@...e.cz wrote:
> > > > VXTIME_PMTMR will be replaced by a more generic "Master Timer"
> > >
> > > This means we have no fallback if something goes wrong with the Master timer?
> > >
> > > A little risky.
> >
> > No, either HPET or PM Timer will become the Master Timer (elected
> > on boot). Master timer is just an abstraction of these, so the
> > rest of the timekeeping code needn't care which hardware timer is
> > being used. That's why the VXTIME_PMTMR mode is not needed.
>
> But there is no option for the user to force so, is there?
HPET is the default. If it's not available or with the "nohpet"
commandline option, PM Timer will be used as the Master Timer.
If this is not enough, it can be easily fixed in time_init().
--
Jiri Bohac <jbohac@...e.cz>
SUSE Labs, SUSE CZ
-
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