From: "David S. Miller" <davem@redhat.com>
To: adam@yggdrasil.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kmalloc always return address below 4GB?
Date: Tue, 05 Mar 2002 07:15:14 -0800 (PST) [thread overview]
Message-ID: <20020305.071514.127196960.davem@redhat.com> (raw)
In-Reply-To: <200203051443.GAA05242@adam.yggdrasil.com>
In-Reply-To: <200203051443.GAA05242@adam.yggdrasil.com>
From: "Adam J. Richter" <adam@yggdrasil.com>
Date: Tue, 5 Mar 2002 06:43:35 -0800
Just to be clear, I assume that you mean that you cannot
simply cast these virtual addresses to dma_addr_t and that the
underlying physical memory is not guaranteed to be below 4GB,
but that you can use that memory with pci_map_single if your
PCI device can handle 64 bit addresses.
If I got it right, then here is some proposed replacement
text, to possibly save you a little effort:
You haven't got it right. Physical address > 4GB does not mean
your 32-bit device cannot DMA to it. Stop thinking about
implementation, that's the whole point of the abstraction :-)
On 64-bit platforms that don't set CONFIG_HIGHMEM, they have MMU's on
the PCI bus that can map arbitrary 64-bit physical addresses to 32-bit
PCI bus addresses. So on these platforms you may pass any pointer
from kmalloc()/alloc_page() whatsoever into the pci_map_foo()
routines.
In order to handle highmem pages, you have to set your DMA mask
appropriately (to indicate 64-bit addressing capability) and
use pci_map_page() instead of pci_map_single().
Look at other drivers using the DMA interfaces like the two aic7xxx
and all of the sym53c8xx drivers, they get it right.
next prev parent reply other threads:[~2002-03-05 15:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 14:43 Adam J. Richter
2002-03-05 15:15 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-03-06 2:28 Adam J. Richter
2002-03-05 17:08 Adam J. Richter
2002-03-06 1:13 ` David S. Miller
2002-03-05 16:39 Adam J. Richter
2002-03-05 17:00 ` Gerd Knorr
2002-03-05 21:57 ` Steffen Persvold
2002-03-06 7:22 ` David S. Miller
2002-03-05 11:52 Adam J. Richter
2002-03-05 11:59 ` David S. Miller
2002-03-05 11:12 Adam J. Richter
2002-03-05 11:16 ` David S. Miller
2002-03-05 15:43 ` Steffen Persvold
2002-03-05 16:44 ` David Mosberger
2002-03-06 1:31 ` David Mosberger
2002-03-06 2:04 ` David Mosberger
2002-03-05 15:47 ` David S. Miller
2002-03-06 1:09 ` David S. Miller
2002-03-06 1:52 ` David S. Miller
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=20020305.071514.127196960.davem@redhat.com \
--to=davem@redhat.com \
--cc=adam@yggdrasil.com \
--cc=linux-kernel@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®