From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
elliott@hpe.com, Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@ml01.01.org, x86@kernel.org
Subject: Re: [PATCH v10 4/4] x86: Create a new synthetic cpu capability for machine check recovery
Date: Thu, 11 Feb 2016 12:55:39 +0100 [thread overview]
Message-ID: <20160211115539.GD5565@pd.tnic> (raw)
In-Reply-To: <20160210192749.GA29493@agluck-desk.sc.intel.com>
On Wed, Feb 10, 2016 at 11:27:50AM -0800, Luck, Tony wrote:
> Digging in the data sheet I found the CAPID0 register which does
> indicate in bit 4 whether this is an "EX" (a.k.a. "E7" part). But
> we invent a new PCI device ID for this every generation (0x0EC3 in
> Ivy Bridge, 0x2fc0 in Haswell, 0x6fc0 in Broadwell). The offset
> has stayed at 0x84 through all this.
>
> I don't think that hunting the ever-changing PCI-id is a
> good choice ...
Right :-\
> the "E5/E7" naming convention has stuck for
> four generations[1] (Sandy Bridge, Ivy Bridge, Haswell, Broadwell).
>
> -Tony
>
> [1] Although this probably means that marketing are about to
> think of something new ... they generally do when people start
> understanding the model names :-(
Yeah, customers shouldn't slack and relax into even thinking they know
the model names. Fortunately there's wikipedia...
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: "Luck, Tony" <tony.luck@intel.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Dan Williams <dan.j.williams@intel.com>,
elliott@hpe.com, Brian Gerst <brgerst@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-nvdimm@ml01.01.org, x86@kernel.org
Subject: Re: [PATCH v10 4/4] x86: Create a new synthetic cpu capability for machine check recovery
Date: Thu, 11 Feb 2016 12:55:39 +0100 [thread overview]
Message-ID: <20160211115539.GD5565@pd.tnic> (raw)
In-Reply-To: <20160210192749.GA29493@agluck-desk.sc.intel.com>
On Wed, Feb 10, 2016 at 11:27:50AM -0800, Luck, Tony wrote:
> Digging in the data sheet I found the CAPID0 register which does
> indicate in bit 4 whether this is an "EX" (a.k.a. "E7" part). But
> we invent a new PCI device ID for this every generation (0x0EC3 in
> Ivy Bridge, 0x2fc0 in Haswell, 0x6fc0 in Broadwell). The offset
> has stayed at 0x84 through all this.
>
> I don't think that hunting the ever-changing PCI-id is a
> good choice ...
Right :-\
> the "E5/E7" naming convention has stuck for
> four generations[1] (Sandy Bridge, Ivy Bridge, Haswell, Broadwell).
>
> -Tony
>
> [1] Although this probably means that marketing are about to
> think of something new ... they generally do when people start
> understanding the model names :-(
Yeah, customers shouldn't slack and relax into even thinking they know
the model names. Fortunately there's wikipedia...
Thanks.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
next prev parent reply other threads:[~2016-02-11 11:55 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 20:36 [PATCH v10 0/4] Machine check recovery when kernel accesses poison Tony Luck
2016-02-04 20:36 ` Tony Luck
2015-12-31 19:40 ` [PATCH v10 2/4] x86, mce: Check for faults tagged in EXTABLE_CLASS_FAULT exception table entries Tony Luck
2015-12-31 19:40 ` Tony Luck
2016-01-08 20:49 ` [PATCH v10 1/4] x86: Expand exception table to allow new handling options Tony Luck
2016-01-08 20:49 ` Tony Luck
2016-01-08 21:18 ` [PATCH v10 3/4] x86, mce: Add __mcsafe_copy() Tony Luck
2016-01-08 21:18 ` Tony Luck
2016-02-07 16:49 ` Borislav Petkov
2016-02-07 16:49 ` Borislav Petkov
2016-02-09 23:15 ` Luck, Tony
2016-02-09 23:15 ` Luck, Tony
2016-02-10 10:58 ` Borislav Petkov
2016-02-10 10:58 ` Borislav Petkov
2016-02-10 19:39 ` Luck, Tony
2016-02-10 19:39 ` Luck, Tony
2016-02-10 20:50 ` Borislav Petkov
2016-02-10 20:50 ` Borislav Petkov
2016-02-07 16:55 ` Borislav Petkov
2016-02-07 16:55 ` Borislav Petkov
2016-02-07 20:54 ` Richard Weinberger
2016-02-07 20:54 ` Richard Weinberger
2016-01-30 0:00 ` [PATCH v10 4/4] x86: Create a new synthetic cpu capability for machine check recovery Tony Luck
2016-01-30 0:00 ` Tony Luck
2016-02-07 17:10 ` Borislav Petkov
2016-02-07 17:10 ` Borislav Petkov
2016-02-09 23:38 ` Luck, Tony
2016-02-09 23:38 ` Luck, Tony
2016-02-10 11:06 ` Borislav Petkov
2016-02-10 11:06 ` Borislav Petkov
2016-02-10 19:27 ` Luck, Tony
2016-02-10 19:27 ` Luck, Tony
2016-02-11 11:55 ` Borislav Petkov [this message]
2016-02-11 11:55 ` Borislav Petkov
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=20160211115539.GD5565@pd.tnic \
--to=bp@alien8.de \
--cc=akpm@linux-foundation.org \
--cc=brgerst@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=elliott@hpe.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-nvdimm@ml01.01.org \
--cc=luto@kernel.org \
--cc=mingo@kernel.org \
--cc=tony.luck@intel.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.