All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: "Tigran Aivazian" <tigran_aivazian@symantec.com>
Cc: "Andrew Morton" <akpm@osdl.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] fix x86 microcode driver handling of multiple matching revisions
Date: Thu, 04 May 2006 10:00:34 +0200	[thread overview]
Message-ID: <4459D0C2.76E4.0078.0@novell.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0605040828230.2440@ezer.homenet>

Tigran,

>First of all, I would like to know why is it that you have several chunks 
>in your microcode data which correspond to the same CPU? In the normal 
>data files which come from Intel there are no such chunks. Are you 
>concatenating the new files with the old (just in case the new update is 
>no good, so you can fall back to the old)?

the update file is the one in microcode_ctl-1.13. CPUID 0x00000f48 can
be found twice in that file, once with product code bits 0x0000005f and
a second time with 0x00000002. Obviously these overlap for CPUs with
product code 1 (testing bit mask 0x00000002), which is what is the case
for the (Paxville) system I saw the ill behavior on.

Thanks, Jan

  reply	other threads:[~2006-05-04  7:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-26 14:17 [PATCH] fix x86 microcode driver handling of multiple matching revisions Jan Beulich
2006-05-04  7:28 ` Tigran Aivazian
2006-05-04  8:00   ` Jan Beulich [this message]
2006-05-05  7:55     ` Tigran Aivazian
2006-05-04 17:09 ` Siddha, Suresh B
2006-05-05  6:50   ` Jan Beulich
2006-05-05 11:26   ` [PATCH, updated] " Jan Beulich
2006-05-06 20:26     ` Tigran Aivazian

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=4459D0C2.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tigran_aivazian@symantec.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 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.