Date: Mon, 22 Mar 2004 07:40:34 -0800 (PST)
From: Tigran Aivazian <tigran@veritas.com>
To: Timothy Miller <miller@techsource.com>
cc: David Schwartz <davids@webmaster.com>, Justin Piszcz <jpiszcz@hotmail.com>,
       linux-kernel@vger.kernel.org
Subject: Re: Linux Kernel Microcode Question
In-Reply-To: <405F0B8D.8040408@techsource.com>
Message-ID: <Pine.GSO.4.58.0403220736480.8694@south.veritas.com>
References: <Pine.LNX.4.44.0403191721110.3892-100000@einstein.homenet> 
    <405F0B8D.8040408@techsource.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1541
Lines: 34

On Mon, 22 Mar 2004, Timothy Miller wrote:
> I don't see anything wrong with what he said.  As I understand it,
> Pentium 4 CPUs don't use microcode for much of anything.  If an
> instruction which was done entirely in dedicated hardware was buggy, and
> it's replaced by microcode, then it will most certainly be slower.
>
> You seem to have missed where David used terms like "theoretically
> possible" and "an operation".

No, that is not what he said and that (what you say) is certainly wrong,
namely this bit:

  If an instruction which was done entirely in dedicated hardware was
  buggy, and it's replaced by microcode, then it will most certainly be
  slower.

All instructions are done by means of microcode of some sort, i.e. the
instructions are "compiled" as they are executed into a more primitive
instruction set (called "microcode" or "u-code"). If a buggy instruction
(or rather the sequence of microcode which corresponds to it) is replaced
by a fixed version (i.e. by some other sequence of microcode) then there
is no reason to say that the result will "most certainly be slower". For
some bugs the fix runs faster than the broken code, for others it may be
slower --- there is no way to tell apriori that it will always be slower.

Do you understand now?

Kind regards
Tigran
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/