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: Mon, 03 Nov 2003 18:42:48 +0000	[thread overview]
Message-ID: <marc-linux-ia64-106788524101394@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106724227826901@msgid-missing>



> > Hi,
> > 
> > I just wondered if a speculative load hitting a cache or memory
> > error does cause an exception on IA64 ? 
> 
> I dont think a speculative load should cause a problem - at 
> least until 
> code tries to consume the data by transfering it to a 
> processor register.

If you are doing a read (which is what a speculative load will be
generating), the error will be generated by whatever part of the logic that
detects it. You cannot possible send poisoned data through a memory bus and a
system bus (at least not the Intel system buses I am familiar with) without
having some of the error checking logic (ECC or parity) complaining about it
(this means generating an MCA).

> As I understand the cpu architecture, an error that occurs 
> reading data
> will result in a poisoned cache line being delivered to the 
> cpu cache. 
> The poisoned cache line can stay in the cache forever. No MCA error is
> reported until the data is actually consumed by tranfering 
> the data from 
> cache to a cpu register. 

The problem is that the cache error checking logic has no way of knowing that
the data it is about to supply to some register is going to be used for a
speculative operation. The cache logic is pretty far away (in processor
terms) from the decoding logic.

Bert Munoz

> This requires some support from the chipset. Some chipsets dont fully
> support this error model.
> 
> 
> 
> 
> -- 
> Thanks
> 
> Jack Steiner (steiner@sgi.com)          651-683-5302
> Principal Engineer                      SGI - Silicon Graphics, Inc.
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe 
> linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 
> 



  parent reply	other threads:[~2003-11-03 18:42 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 [this message]
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
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-106788524101394@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