From: Randy Dunlap <randy.dunlap@oracle.com>
To: jacob pan <jacob.jun.pan@linux.intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@elte.hu>,
Alan Cox <alan@linux.intel.com>
Subject: Re: [PATCH 2/2] x86/mrst: add more timer config options
Date: Mon, 17 May 2010 13:28:42 -0700 [thread overview]
Message-ID: <4BF1A6FA.4090801@oracle.com> (raw)
In-Reply-To: <20100517132642.000073d4@unknown>
On 05/17/10 13:26, jacob pan wrote:
> Randy Dunlap Mon, 17 May 2010 12:56:19 -0700
>
>>> Manual override is possible via cmdline option x86_mrst_timer.
>>
>> which is documented where??
> It is documented in Documentation/kernel-parameters.txt, the option has not changed but the impact has been extended to the new Medfield platforms.
>
> x86_mrst_timer= [X86-32,APBT]
> Choose timer option for x86 Moorestown MID platform.
> Two valid options are apbt timer only and lapic timer
> plus one apbt timer for broadcast timer.
> x86_mrst_timer=apbt_only | lapic_and_apbt
Thanks. I missed seeing that somehow. Sorry about that.
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2010-05-17 20:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 19:23 [PATCH 0/2] v3 Moorestown updated patches 2,3,4 of v2 Jacob Pan
2010-05-17 19:23 ` [PATCH 1/2] x86/mrst: add cpu type detection Jacob Pan
2010-05-17 19:23 ` [PATCH 2/2] x86/mrst: add more timer config options Jacob Pan
2010-05-17 19:56 ` Randy Dunlap
2010-05-17 20:26 ` jacob pan
2010-05-17 20:28 ` Randy Dunlap [this message]
2010-05-17 20:27 ` 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=4BF1A6FA.4090801@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=alan@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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