From: Burt Triplett <burt@pbjtriplett.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Seth Forshee <seth.forshee@canonical.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Arjan van de Ven <arjan@infradead.org>,
Venkatesh Pallipadi <venki@google.com>,
Len Brown <lenb@kernel.org>
Subject: Re: Performance/resume issues on Toshiba NB305
Date: Fri, 25 Feb 2011 21:58:25 -0800 [thread overview]
Message-ID: <4D689681.1030301@pbjtriplett.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1102252330290.2701@localhost6.localdomain6>
On 02/25/2011 02:40 PM, Thomas Gleixner wrote:
> On Fri, 25 Feb 2011, Seth Forshee wrote:
>> On Fri, Feb 25, 2011 at 10:47:16PM +0100, Thomas Gleixner wrote:
>>> Let's wait for the intel and acpi folks. It would be interesting what
>>> the new intel toy says to your BIOS.
>>>
>>> http://biosbits.org/
>>
>> Not much because it doesn't know about my processor. About all I could
>> get out of it is that my MSRs are inconsistent, SMI latency is bad, and
>> the round-trip latency via MWAIT test gives elapsed time = 285ms with
>> 229 iterations/ms.
>
> Ouch.
Looks like the Toshiba NB305 has an Intel Atom processor in it.
bits-327, released today, now detects Intel Atom processors, and no
longer shows them as unknown. We don't have any processor-specific
tests for Atom yet, though we may add some in the future. All of the
general tests should work, however.
Can you provide more details on which MSRs show up as inconsistent on
your system? They might represent actual bugs in your BIOS, but we
might just need to add a few more entries to the Atom CPU-specific MSR
blacklist as expected inconsistencies.
- Burt
next prev parent reply other threads:[~2011-02-26 5:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 16:42 Performance/resume issues on Toshiba NB305 Seth Forshee
2011-02-25 20:17 ` Steven Rostedt
2011-02-25 20:27 ` Seth Forshee
2011-02-25 22:11 ` Thomas Gleixner
2011-02-25 22:33 ` Seth Forshee
2011-02-25 20:37 ` Thomas Gleixner
2011-02-25 21:21 ` Seth Forshee
2011-02-25 21:47 ` Thomas Gleixner
2011-02-25 22:29 ` Seth Forshee
2011-02-25 22:40 ` Thomas Gleixner
2011-02-26 5:58 ` Burt Triplett [this message]
2011-02-26 15:00 ` Seth Forshee
2011-02-27 20:17 ` Burt Triplett
2011-02-28 15:10 ` Seth Forshee
2011-03-05 5:55 ` Burt Triplett
2011-02-26 8:49 ` [tip:timers/urgent] clockevents: Prevent oneshot mode when broadcast device is periodic tip-bot for Thomas Gleixner
2011-03-01 20:04 ` Performance/resume issues on Toshiba NB305 Seth Forshee
2011-03-01 20:22 ` 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=4D689681.1030301@pbjtriplett.org \
--to=burt@pbjtriplett.org \
--cc=arjan@infradead.org \
--cc=hpa@zytor.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=tglx@linutronix.de \
--cc=venki@google.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