From: Alex Shi <alex.shi@intel.com>
To: Borislav Petkov <bp@alien8.de>,
"H. Peter Anvin" <h.peter.anvin@intel.com>
Cc: Ilari Stenroth <ilari.stenroth@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: arch/x86/kernel/cpu/intel.c needs an update for Haswell?
Date: Mon, 05 Aug 2013 10:48:29 +0800 [thread overview]
Message-ID: <51FF127D.4030004@intel.com> (raw)
In-Reply-To: <51FA220B.5070307@intel.com>
On 08/01/2013 04:53 PM, Alex Shi wrote:
> From 1322ea9e17ad4d9e49e2d93cfc04805368e28273 Mon Sep 17 00:00:00 2001
> From: Alex Shi <alex.shi@intel.com>
> Date: Thu, 1 Aug 2013 16:30:23 +0800
> Subject: [PATCH 2/2] tlb/tlb_flushall_shift: add haswell tlb_flush_shift
>
> Tested on i5 4350U with munmap case, https://lkml.org/lkml/2012/5/17/59
> The best performance is tlb_flush_shift = 1.
> The balance point is 256 entries.
>
> Signed-off-by: Alex Shi <alex.shi@intel.com>
Any comments on this, Peter? :)
> ---
> arch/x86/kernel/cpu/intel.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kernel/cpu/intel.c b/arch/x86/kernel/cpu/intel.c
> index 9a4bc51..ac9b83a 100644
> --- a/arch/x86/kernel/cpu/intel.c
> +++ b/arch/x86/kernel/cpu/intel.c
> @@ -627,6 +627,7 @@ static void intel_tlb_flushall_shift_set(struct cpuinfo_x86 *c)
> tlb_flushall_shift = 5;
> break;
> case 0x63a: /* Ivybridge */
> + case 0x645: /* Haswell */
> tlb_flushall_shift = 1;
> break;
> case 0x63e: /* Ivybridge EP */
--
Thanks
Alex
next prev parent reply other threads:[~2013-08-05 2:49 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 [this message]
2013-08-05 2:59 ` H. Peter Anvin
2013-08-17 20:53 ` Ilari Stenroth
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=51FF127D.4030004@intel.com \
--to=alex.shi@intel.com \
--cc=bp@alien8.de \
--cc=h.peter.anvin@intel.com \
--cc=ilari.stenroth@gmail.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).