mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Ilari Stenroth <ilari.stenroth@gmail.com>
Cc: linux-kernel@vger.kernel.org, Alex Shi <alex.shi@intel.com>
Subject: Re: arch/x86/kernel/cpu/intel.c needs an update for Haswell?
Date: Tue, 30 Jul 2013 21:54:02 +0200	[thread overview]
Message-ID: <20130730195402.GD23299@pd.tnic> (raw)
In-Reply-To: <kt951r$m5m$1@ger.gmane.org>

On Tue, Jul 30, 2013 at 10:44:02PM +0300, Ilari Stenroth wrote:
> On 30.7.2013 22.35, Borislav Petkov wrote:
> > On Tue, Jul 30, 2013 at 09:50:49PM +0300, Ilari Stenroth wrote:
> >> Does somebody know why arch/x86/kernel/cpu/intel.c has
> >> tlb_flushall_shift detection logic for Ivy Bridge CPU family but not
> >> for Haswell? Maybe intel_cacheinfo.c needs to be checked for Haswell
> >> updates too.
> > 
> > Because someone needs to sit down and write it. Oh, and more
> > importantly, test it on real hardware.
> > 
> > :-)
> > 
> Right :-) Can volunteer to test, only once I get a motherboard bug
> fixed. It runs only one core. Poor Supermicro X10SLH-F thinks Xeon
> E3-1265Lv3 has 1C2T :-/

Yeah, if I had to guess, I'd say the highest probability is for patches
about it to be coming from Alex. :)

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--

  reply	other threads:[~2013-07-30 19:54 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-30 18:50 Ilari Stenroth
2013-07-30 19:35 ` Borislav Petkov
2013-07-30 19:44   ` Ilari Stenroth
2013-07-30 19:54     ` Borislav Petkov [this message]
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

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=20130730195402.GD23299@pd.tnic \
    --to=bp@alien8.de \
    --cc=alex.shi@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

Powered by JetHome