From: Ilari Stenroth <ilari.stenroth@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: "H. Peter Anvin" <h.peter.anvin@intel.com>,
Alex Shi <alex.shi@intel.com>
Subject: Re: arch/x86/kernel/cpu/intel.c needs an update for Haswell?
Date: Sat, 17 Aug 2013 23:53:31 +0300 [thread overview]
Message-ID: <520FE2CB.3070302@gmail.com> (raw)
In-Reply-To: <51FF150D.8000103@intel.com>
On 5.8.2013 5.59, H. Peter Anvin wrote:
> On 08/04/2013 07:48 PM, Alex Shi wrote:
>>
>> Any comments on this, Peter? :)
>>
>
> Sounds like you have done the measurements, so it seems fine.
>
> -hpa
>
I've been using these patches. No compalints.
Should the patches get pulled to linux-next tree for wider testing?
--
Ilari Stenroth
prev parent reply other threads:[~2013-08-17 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-30 18:50 arch/x86/kernel/cpu/intel.c needs an update for Haswell? Ilari Stenroth
2013-07-30 19:35 ` Borislav Petkov
2013-07-30 19:44 ` Ilari Stenroth
2013-07-30 19:54 ` Borislav Petkov
2013-08-01 8:53 ` Alex Shi
2013-08-01 9:07 ` Alex Shi
2013-08-05 2:47 ` Alex Shi
2013-08-05 2:48 ` Alex Shi
2013-08-05 2:59 ` H. Peter Anvin
2013-08-17 20:53 ` Ilari Stenroth [this message]
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=520FE2CB.3070302@gmail.com \
--to=ilari.stenroth@gmail.com \
--cc=alex.shi@intel.com \
--cc=h.peter.anvin@intel.com \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).