From: Thomas Gleixner <tglx@linutronix.de>
To: Feng Tang <feng.tang@intel.com>
Cc: "mingo@elte.hu" <mingo@elte.hu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
shaohua.li@intel.com, jacob.jun.pan@intel.com
Subject: Re: [PATCH] tick: add check for the existence of broadcast clock event device
Date: Mon, 8 Jun 2009 07:43:43 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.00.0906080739020.3419@localhost.localdomain> (raw)
In-Reply-To: <20090608095730.0c945e78@feng-desktop>
On Mon, 8 Jun 2009, Feng Tang wrote:
> > 1) How do you calibrate the local APIC timer if you do not have some
> > initial timer device ?
> Yes, we have external timer device with the name "apbt"
So that timer is initialized and registered before the local apic,
right ?
Why is the local APIC timer used at all ? The apbt timer should have a
higher rating as the local APIC timer, so when APIC is registered it
is not selected and the check in the broadcast functions
!(dev->features & CLOCK_EVT_FEAT_C3STOP))
should protect you because that bit is not set on your apbt device.
Thanks,
tglx
next prev parent reply other threads:[~2009-06-08 5:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 3:27 [PATCH] tick: add check for the existence of broadcast clock event device Feng Tang
2009-06-06 9:24 ` Thomas Gleixner
2009-06-06 12:47 ` Feng Tang
2009-06-06 12:54 ` Thomas Gleixner
2009-06-06 16:18 ` Thomas Gleixner
2009-06-08 1:57 ` Feng Tang
2009-06-08 5:43 ` Thomas Gleixner [this message]
2009-06-08 6:12 ` Feng Tang
2009-06-08 6:33 ` Thomas Gleixner
2009-06-08 6:47 ` Feng Tang
2009-06-08 7:00 ` Thomas Gleixner
2009-06-08 7:47 ` Tang, Feng
2009-06-08 13:41 ` Thomas Gleixner
2009-06-09 0:21 ` Pan, Jacob jun
2009-06-09 8:18 ` Thomas Gleixner
2009-06-09 12:49 ` Pan, Jacob jun
2009-06-09 16:53 ` Thomas Gleixner
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=alpine.LFD.2.00.0906080739020.3419@localhost.localdomain \
--to=tglx@linutronix.de \
--cc=feng.tang@intel.com \
--cc=jacob.jun.pan@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=shaohua.li@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