mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: kraxel@bytesex.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: Does kmalloc always return address below 4GB?
Date: Tue, 05 Mar 2002 23:22:44 -0800 (PST)	[thread overview]
Message-ID: <20020305.232244.51840122.davem@redhat.com> (raw)
In-Reply-To: <slrna89ue7.4at.kraxel@bytesex.org>
In-Reply-To: <200203051639.IAA05629@adam.yggdrasil.com> <slrna89ue7.4at.kraxel@bytesex.org>

   From: Gerd Knorr <kraxel@bytesex.org>
   Date: 5 Mar 2002 17:00:55 GMT
   
   >  computer with >4GB of RAM (CONFIG_HIGHEM) talking to a PCI card
   >  that only does 32-bit addressing:
   >  
   >  		pci_set_dma_mask(pcidev, 0xffffffff);
   >  		addr = vmalloc(nbytes);
   >  		/* On an x86 with >4GB of RAM, addr will be <4GB, but
   >  	           __pa(addr) might be >4GB, and the system lacks
   >  	           PCI address mapping harware. */
   
   use vmalloc_32(), this one returns lowmem.

You can't use vmalloc() pointers as arguments to pci_map_single.
That is the point of what he's mentioning.
   
   >  		dma_addr = pci_map_single(pcidev, addr, nbytes, direction);
   
   This is illegal because addr is a kernel _virtual_ address.  You have to
   get the page using vmalloc_to_page() and feed this to pci_map_page()
   then. 

There is no such requirement that pci_map_page() only be used.
If you know you haven't got a HIGHMEM page, it is legal to
pass this to pci_map_single().

  parent reply	other threads:[~2002-03-06  7:25 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [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 14:43 Adam J. Richter
2002-03-05 15:15 ` 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.232244.51840122.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=kraxel@bytesex.org \
    --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®