public inbox for linux-ia64@vger.kernel.org
 help / color / mirror / Atom feed
From: Robin Holt <holt@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [rfc] generic allocator and mspec driver
Date: Tue, 15 Feb 2005 19:49:42 +0000	[thread overview]
Message-ID: <20050215194942.GD24401@lnx-holt.americas.sgi.com> (raw)
In-Reply-To: <16897.9640.160896.31584@jaguar.mkp.net>

On Tue, Feb 15, 2005 at 11:19:40AM -0800, David Mosberger wrote:
> >>>>> On Tue, 15 Feb 2005 13:11:20 -0600, Robin Holt <holt@sgi.com> said:
> 
>   Robin> We saw many silent data corruptions. The SN2 hardware will
>   Robin> give an MCA if both types of references are made by the cpu
>   Robin> at about the same time, but that depends on both transactions
>   Robin> being on the bus in close relationship to each other.
> 
> Yes, but the point is it affects _most_ of today's machines, including
> x86.  A while ago, there were some nasty data corruption issues on AMD
> chips caused by the AGP GART and the large mappings used by the Linux
> kernel, for example.

One thing I had not thought about before this is SN2 hardware will also
allow us to change the memory protections for the cachelines in the pages
of this granule to not allow cached references.  I am not sure if this
has been tested aside from design verification testing and probably some
of the offline diagnostic tests.

Would anybody have a concern with marking those cache lines as processor
uncached only?  Would there ever be a time that we would expect _ANY_
type of cached reference when the granule is being used for uncached
that would be an acceptable use?

Thanks,
Robin

  parent reply	other threads:[~2005-02-15 19:49 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-02 19:10 [rfc] generic allocator and mspec driver Jes Sorensen
2005-02-02 19:46 ` Jesse Barnes
2005-02-02 23:33 ` Jack Steiner
2005-02-03  7:47 ` Jes Sorensen
2005-02-03  8:38 ` Jes Sorensen
2005-02-03 11:19 ` Robin Holt
2005-02-03 14:55 ` Jes Sorensen
2005-02-03 17:06 ` Jesse Barnes
2005-02-03 17:31 ` Dean Roe
2005-02-03 17:31 ` Robin Holt
2005-02-03 17:41 ` Jesse Barnes
2005-02-03 18:54 ` Jack Steiner
2005-02-03 19:39 ` David Mosberger
2005-02-03 20:58 ` Jes Sorensen
2005-02-03 21:40 ` Luck, Tony
2005-02-04  1:00 ` David Mosberger
2005-02-13 21:57 ` Jes Sorensen
2005-02-14 19:12 ` Luck, Tony
2005-02-14 19:17 ` David Mosberger
2005-02-15  8:43 ` Jes Sorensen
2005-02-15  8:44 ` Jes Sorensen
2005-02-15 17:35 ` Grant Grundler
2005-02-15 18:04 ` David Mosberger
2005-02-15 18:05 ` David Mosberger
2005-02-15 19:11 ` Robin Holt
2005-02-15 19:19 ` David Mosberger
2005-02-15 19:49 ` Robin Holt [this message]
2005-02-15 19:59 ` Jes Sorensen
2005-02-15 20:02 ` Jes Sorensen
2005-02-15 20:24 ` Robin Holt
2005-02-16  7:32 ` Jes Sorensen
2005-02-16 14:17 ` Jes Sorensen
2005-02-16 17:50 ` Luck, Tony
2005-02-16 18:18 ` Luck, Tony
2005-02-16 19:10 ` Jes Sorensen
2005-02-16 21:02 ` David Mosberger

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=20050215194942.GD24401@lnx-holt.americas.sgi.com \
    --to=holt@sgi.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