All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Sexton <sexton@mc.com>
To: linux-kernel@vger.kernel.org
Subject: DRAM and PCI devices at same physical address
Date: 25 Jun 2004 17:23:00 -0400	[thread overview]
Message-ID: <1088198580.29697.62.camel@dhcp_client-120-140> (raw)

I have a dual Xeon system with the Lindenhurst (E7710) chip set and 1 GB
of memory.  In order to reserve a very large block of memory for a
(user-space) device driver I am writing, I pass "mem=XX" to the kernel
at boot time.  Unfortunately, /proc/pci shows two devices now appearing
in the reserved upper memory range.  

For instance, if I set "mem=768M", the following two entries appear in
/proc/pci:

  Bus  0, device   1, function  0:
    System peripheral: PCI device 8086:3594 (Intel Corp.) (rev 4).
      Non-prefetchable 32 bit memory at 0x30000000 [0x30000fff].

  Bus  0, device  31, function  1:
    IDE interface: Intel Corp. 82801EB Ultra ATA Storage Controller (rev
2).
      IRQ 18.
      I/O at 0x14a0 [0x14af].
      Non-prefetchable 32 bit memory at 0x30001000 [0x300013ff].


The devices always appear right after the limit I specify on the kernel
boot line.  If I specify "mem=512M", then the first device appears at
0x20000000.  If I specify nothing, then it appears at 0x40000000.  All
other PCI devices show up at addresses of 0xDD000000 and above.

Is there any way to prevent these devices from showing up in the
physical address range of my reserved memory?

Should they be appearing there at all?  Does Linux make any guarantees
when there is more physical memory than specified by "mem=" ?

Please CC me on any responses.

Thank you,
Matt Sexton
sexton@mc.com



             reply	other threads:[~2004-06-25 21:23 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-25 21:23 Matt Sexton [this message]
2004-06-27  3:26 ` DRAM and PCI devices at same physical address Matt Porter
2004-06-28 15:51   ` Matt Sexton
2004-06-28 16:22     ` Matt Porter
2004-06-28 19:27 ` Ross Biro
2004-06-29 14:31   ` Matt Sexton

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=1088198580.29697.62.camel@dhcp_client-120-140 \
    --to=sexton@mc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.