From: Jeremy Higdon <jeremy@sgi.com>
To: "Moore, Eric Dean" <Emoore@lsil.com>
Cc: Alex Williamson <alex.williamson@hp.com>,
jbarnes@sgi.com, bjorn.helgaas@hp.com, willy@debian.org,
James.Bottomley@steeleye.com, linux-scsi@vger.kernel.org
Subject: Re: mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!?
Date: Wed, 18 Feb 2004 17:09:39 -0800 [thread overview]
Message-ID: <20040219010939.GB502690@sgi.com> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E5703EF93EA@exa-atlanta.se.lsil.com>
On Wed, Feb 18, 2004 at 07:03:47PM -0500, Moore, Eric Dean wrote:
> Jeremy - thanks for your reply. Just wanted to clarify
> if this would work on your system:
>
>
> mptbase_probe(pdev,id) {
>
> u64 mask64 = 0xFFFFFFFFFFFFFFFF;
> u32 mask32 = 0xFFFFFFFF;
>
> pci_enable_device(pdev);
>
> ioc->pcidev32 = pdev;
> ioc->pcidev64 = pdev;
>
> r = pci_set_dma_mask(ioc->pcidev64, mask64 );
> r = pci_set_consistent_dma_mask(ioc->pcidev64, mask64 );
> r = pci_set_dma_mask(ioc->pcidev32, mask32 );
> r = pci_set_consistent_dma_mask(ioc->pcidev32, mask32 );
>
> /* use
> * ioc->pcidev32
> * for the three fifo memory allocations for < 4gb
> *
> * use
> * ioc->pcidev64
> * for all other allocations
> */
>
> }
I don't think so, for two reasons.
The first is that we require 64 bit PCI addresses for all PCI-X devices.
The second is that if I understand your pseudo-code correctly, the pcidev64
and pcidev32 pointers are both pointing to the same struct pci_dev, which
would mean that the second pci_set_consistent_dma_mask call would override
the first.
Hopefully it's not too much effort to change it to a single consistent
allocation for all three FIFO chunks. I don't see another way around
this.
jeremy
next prev parent reply other threads:[~2004-02-19 1:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 0:03 mpt sets 64bit consistent mask yet requires mapping in same 4 GB chunk?!? Moore, Eric Dean
2004-02-19 1:09 ` Jeremy Higdon [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-02-19 17:18 Moore, Eric Dean
2004-02-20 6:30 ` Jeremy Higdon
2004-02-18 18:41 Moore, Eric Dean
2004-02-18 18:52 ` Alex Williamson
2004-02-18 23:20 ` Jeremy Higdon
2004-02-13 23:23 Moore, Eric Dean
2004-02-13 21:20 Moore, Eric Dean
2004-02-13 21:30 ` Jesse Barnes
2004-02-13 22:52 ` Bjorn Helgaas
2004-02-13 23:08 ` Jeremy Higdon
2004-02-13 23:13 ` Matthew Wilcox
2004-02-13 23:39 ` Jeremy Higdon
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=20040219010939.GB502690@sgi.com \
--to=jeremy@sgi.com \
--cc=Emoore@lsil.com \
--cc=James.Bottomley@steeleye.com \
--cc=alex.williamson@hp.com \
--cc=bjorn.helgaas@hp.com \
--cc=jbarnes@sgi.com \
--cc=linux-scsi@vger.kernel.org \
--cc=willy@debian.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