mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net>
To: Andrew Morton <akpm@osdl.org>, jens.axboe@oracle.com
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH 2/2] cciss: disable dma prefetch for P600
Date: Fri, 20 Oct 2006 14:56:18 -0500	[thread overview]
Message-ID: <20061020195618.GA13181@beardog.cca.cpqcorp.net> (raw)
In-Reply-To: <20061018143723.48510ea7.akpm@osdl.org>

On Wed, Oct 18, 2006 at 02:37:23PM -0700, Andrew Morton wrote:
> 
> argh, you removed the mailing list from cc.

Sorry, I'm still lacking proper etiquette.

> 
> On Wed, 18 Oct 2006 11:54:53 -0500
> "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net> wrote:
> 
> > On Tue, Oct 17, 2006 at 05:10:21PM -0700, Andrew Morton wrote:
> > > On Tue, 17 Oct 2006 16:13:03 -0500
> > > "Mike Miller (OS Dev)" <mikem@beardog.cca.cpqcorp.net> wrote:
> > > 
> > > > PATCH 2/2
> > > > Turned off DMA prefetch for the P600 on systems which may present
> > > > discontiguous memory.
> > > > 
> > > 
> > > What do you mean by "discontiguous memory"?  CONFIG_DISCONTIGMEM?
> > 
> > The IPF memory map can have holes between the different regions. I've
> > been told by our HW guys that AMD may also have holes.
> 
> Pretty much all platforms/architectures have holes in their physical memory
> map.
> 
> 
> > > 
> > > What is the actual problem which is being fixed here?
> > 
> > Sorry, I should have been clearer. There is a bug in the DMA engine that
> > that may result in prefetching data from beyond the end of memory or
> > falling off into one the holes on IPF and AMD. It causes a machine check
> > when that happens.
> > It doesn't happen on Proliant because the last 4kB (or so) of memory is
> > mapped out by the BIOS and Pentium guarantees contiguous memory.
> 
> I think that this:
> 
> > > #if defined(CONFIG_IA64) || defined(CONFIG_X86_64)
> 
> is nowhere near strong enough and is probably inappropriate.
> 
> It _could_ be that CONFIG_DISCONTIGMEM|CONFIG_SPARSEMEM will be closer, but
> even CONFIG_FLATMEM systems can have holes.

I'm poking around on some IPF platforms. It looks like CONFIG_DISCONTIGMEM is
set on them, but not the others you mention. Would that be sufficient?

> 
> On what machines can/does this card exist?  Things like powerpc?

This problem was found on Itanium. We don't try to support powerpc.

Thanks,
mikem

  parent reply	other threads:[~2006-10-20 19:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 21:13 Mike Miller (OS Dev)
2006-10-18  0:10 ` Andrew Morton
     [not found]   ` <20061018165453.GA14255@beardog.cca.cpqcorp.net>
     [not found]     ` <20061018143723.48510ea7.akpm@osdl.org>
2006-10-20 19:56       ` Mike Miller (OS Dev) [this message]
2006-10-20 20:23         ` Andrew Morton

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=20061020195618.GA13181@beardog.cca.cpqcorp.net \
    --to=mikem@beardog.cca.cpqcorp.net \
    --cc=akpm@osdl.org \
    --cc=jens.axboe@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@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

all inboxes | Powered by JetHome®