public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: "Alberto Munoz" <amunoz@vmware.com>
To: linux-ia64@vger.kernel.org
Subject: RE: [RFC] Better MCA recovery on IPF
Date: Wed, 05 Nov 2003 17:37:51 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106805441113849@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106724227826901@msgid-missing>



> -----Original Message-----
> From: Matthew Wilcox [mailto:willy@debian.org]
> Sent: Wednesday, November 05, 2003 9:31 AM
> To: Alberto Munoz
> Cc: Luck, Tony; Jack Steiner; Matthias Fouquet-Lapar; Russ Anderson;
> linux-ia64@vger.kernel.org
> Subject: Re: [RFC] Better MCA recovery on IPF
> 
> 
> On Wed, Nov 05, 2003 at 09:14:08AM -0800, Alberto Munoz wrote:
> > What implementation of the Itanium processor supports 
> avoiding MCAs from
> > lfetch or code fetch operations? I don't think Itanium 1 or 
> 2 do this. How
> > about Madison?
> 
> Oops, misunderstanding here.  Madison and Deerfield are also 
> Itanium 2.
> It's like Coppermine and Tualatin are both Pentium 3.  When 
> the difference
> is only cache size, die size, clock frequency and so on, they're not
> going to change the number.  For bigger changes, they might ;-)

Not really a misunderstanding. I just got a little lose with the names. I
should have said Merced, McKinley instead of Itanium 1 and 2.

In any case, it has been my experience that some times there are fairly major
changes in RAS features (typically addressing shortcomings of a predecessor)
betweens processors of the same vintage (McKinley, Madison and Deerfield).

Bert Munoz
> -- 
> "It's not Hollywood.  War is real, war is primarily not about 
> defeat or
> victory, it is about death.  I've seen thousands and 
> thousands of dead bodies.
> Do you think I want to have an academic debate on this 
> subject?" -- Robert Fisk
> 
> 



  parent reply	other threads:[~2003-11-05 17:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-27  8:07 [RFC] Better MCA recovery on IPF Hidetoshi Seto
2003-10-27 16:58 ` Matthias Fouquet-Lapar
2003-10-31  5:09 ` Hidetoshi Seto
2003-10-31 17:14 ` Grant Grundler
2003-11-01  6:39 ` Matthias Fouquet-Lapar
2003-11-01  8:38 ` Keith Owens
2003-11-02 13:33 ` Matthias Fouquet-Lapar
2003-11-03 17:09 ` Russ Anderson
2003-11-03 17:37 ` Matthias Fouquet-Lapar
2003-11-03 17:51 ` Alberto Munoz
2003-11-03 17:53 ` Alberto Munoz
2003-11-03 18:23 ` Jack Steiner
2003-11-03 18:42 ` Alberto Munoz
2003-11-03 19:28 ` Jack Steiner
2003-11-03 23:09 ` Alberto Munoz
2003-11-05  4:11 ` Greg Banks
2003-11-05 17:00 ` Luck, Tony
2003-11-05 17:14 ` Alberto Munoz
2003-11-05 17:30 ` Matthew Wilcox
2003-11-05 17:37 ` Alberto Munoz [this message]
2003-11-06 12:03 ` Hidetoshi Seto
2003-11-06 14:23 ` Matthias Fouquet-Lapar
2003-11-06 19:09 ` Luck, Tony
2003-11-07  9:58 ` Hidetoshi Seto
2003-11-07 10:52 ` Matthias Fouquet-Lapar
2003-11-08  1:15 ` Luck, Tony
2003-11-08  7:36 ` Matthias Fouquet-Lapar
2003-11-10 10:33 ` Hidetoshi Seto

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=marc-linux-ia64-106805441113849@msgid-missing \
    --to=amunoz@vmware.com \
    --cc=linux-ia64@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