public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjanv@redhat.com>
To: Andi Kleen <ak@muc.de>
Cc: linux-scsi@vger.kernel.org, gibbs@scsiguy.com
Subject: Re: aic7xxx strange code
Date: Thu, 1 Jan 2004 23:34:52 +0100	[thread overview]
Message-ID: <20040101223452.GA16369@devserv.devel.redhat.com> (raw)
In-Reply-To: <m3vfnvi9my.fsf@averell.firstfloor.org>

[-- Attachment #1: Type: text/plain, Size: 1592 bytes --]

On Thu, Jan 01, 2004 at 11:31:17PM +0100, Andi Kleen wrote:
> Arjan van de Ven <arjanv@redhat.com> writes:
> >
> > This is the first time I've seen this bug (thanks again for reporting it)
> > and it's clearly an API violation of the ONE API in linux which is very well
> > documented so no other platform will have copied this bad bug... Adaptect
> 
> It may be well documented, but ports do not follow the documentation
> very well in that area. In particular i386 handles the consistent dma mask
> completely different than all the 64bit ports. Small overview:
> 
> Architecture                  pci_alloc_consistent uses
> i386                          normal dma mask
				.... but clipped to 32 bit

> most 64bit archs/old x86-64   hardcoded 0xffffffff
> newer IA64/some x86-64        consistent dma mask (2) 
> newest x86-64                 normal dma mask & consistent dma mask (1) (2)
> old redhat IA64               hardcoded 0xffffffffffffffff (?)

not just old RH; At least one old SuSE too :0 (in fact I found a previous
report claiming this only affected SuSE but it seems we're in the same boat
now)

> 
> (1) to be bug-to-bug compatible with i386, some drivers rely on that.
> (2) consistent dma mask is normally equivalent to hardcoded 0xffffffff
> because that is the default value
>                                     
> It's quite a mess unfortunately. Due to (2) the 64bit architectures
> are consistent, except for that old IA64. But i386 doing something
> different is quite a problem.

but i386 will *never* return > 32 bit at least.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-01-01 22:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-31 15:46 aic7xxx strange code Arjan van de Ven
2003-12-31 18:36 ` Justin T. Gibbs
2004-01-01 10:08   ` Arjan van de Ven
2004-01-01 16:16     ` Justin T. Gibbs
2004-01-01 16:17       ` Arjan van de Ven
2004-01-01 16:21         ` Justin T. Gibbs
2004-01-01 16:28           ` Arjan van de Ven
2004-01-01 22:31             ` Andi Kleen
2004-01-01 22:34               ` Arjan van de Ven [this message]
2004-01-01 23:14                 ` Andi Kleen

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=20040101223452.GA16369@devserv.devel.redhat.com \
    --to=arjanv@redhat.com \
    --cc=ak@muc.de \
    --cc=gibbs@scsiguy.com \
    --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