From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, htejun@gmail.com
Cc: Shane.Huang@amd.com, mdnelson8@gmail.com,
linux-ide@vger.kernel.org, jgarzik@redhat.com,
grundler@google.com
Subject: Re: What's the SB600 64-bit DMA problem?
Date: Mon, 29 Sep 2008 22:00:02 -0400 [thread overview]
Message-ID: <20080930020002.26564.qmail@science.horizon.com> (raw)
In-Reply-To: <48E058D2.7050704@gmail.com>
Tejun Heo <htejun@gmail.com> wrote:
> George Spelvin wrote:
>> ATM I'm just recompiling the kernel from -rc6 to -rc7.
>>
>> It's in single-user mode so I can't ssh over the boot messages, but
>> they definitely included "64bit" from ahci_print_info().
>
> Thanks for verifying. I would love to lift the 32 restriction from
> SB600 but it's been quite a rocky ride and I still can't tell what's
> the determining factor. :-(
H'm.... 64-bit support comes through in multiple places.
I wonder if it's just one of them?
- HBA memory-mapped registers (which are in fact limited to 32 bits)
- Port x command list base address
- Port x FIS base address
- Command table base address (command header, offset 8)
- Data base address (physical region descriptor, offset 0)
What we really care about is that the data physical regions can
be anywhere in 64-bit space. If any of the others were limited to
32 bits, that would only be slightly annoying.
But...
The base addresses are already above 4G. Aobve 8G, actually.
Port 0 base addresses: 02 1f1e 0000, 02 1f1e 0400
Port 1 base addresses: 02 1f1a 0000, 02 1f1a 0400
Port 2 base addresses: 02 1f98 0000, 02 1f98 0400
Port 3 base addresses: 02 1f9e 0000, 02 1f9e 0400
/proc/iomem looks like:
00000000-0009fbff : System RAM
0009fc00-0009ffff : reserved
000c0000-000cffff : pnp 00:0e
000e4000-000fffff : reserved
00100000-dffbffff : System RAM
00200000-005187db : Kernel code
005187dc-006c310f : Kernel data
0073f000-007bb4cf : Kernel bss
20000000-23ffffff : GART
dffc0000-dffcdfff : ACPI Tables
dffce000-dffeffff : ACPI Non-volatile Storage
dfff0000-dfffdfff : reserved
e0000000-efffffff : PCI MMCONFIG 0
fc000000-fdffffff : PCI Bus 0000:03
fc000000-fdffffff : 0000:03:00.0
fe7f4000-fe7f7fff : 0000:00:14.2
fe7fa000-fe7fafff : 0000:00:13.4
fe7fa000-fe7fafff : ohci_hcd
fe7fb000-fe7fbfff : 0000:00:13.3
fe7fb000-fe7fbfff : ohci_hcd
fe7fc000-fe7fcfff : 0000:00:13.2
fe7fc000-fe7fcfff : ohci_hcd
fe7fd000-fe7fdfff : 0000:00:13.1
fe7fd000-fe7fdfff : ohci_hcd
fe7fe000-fe7fefff : 0000:00:13.0
fe7fe000-fe7fefff : ohci_hcd
fe7ff000-fe7ff0ff : 0000:00:13.5
fe7ff000-fe7ff0ff : ehci_hcd
fe7ff800-fe7ffbff : 0000:00:12.0
fe7ff800-fe7ffbff : ahci
fe800000-fe8fffff : PCI Bus 0000:01
fe8c0000-fe8dffff : 0000:01:00.0
fe8ff000-fe8fffff : 0000:01:00.0
fe8ff000-fe8fffff : r8169
fe900000-fe9fffff : PCI Bus 0000:02
fe9c0000-fe9dffff : 0000:02:00.0
fe9c0000-fe9dffff : ahci
fe9fc000-fe9fdfff : 0000:02:00.0
fe9fc000-fe9fdfff : ahci
fe9ff000-fe9fffff : 0000:02:00.0
fe9ff000-fe9fffff : ahci
fea00000-feafffff : PCI Bus 0000:03
feac0000-feadffff : 0000:03:00.0
feae0000-feaeffff : 0000:03:00.1
feaf0000-feafffff : 0000:03:00.0
feb00000-febfffff : PCI Bus 0000:04
febff800-febfffff : 0000:04:00.0
fec00000-fec00fff : IOAPIC 0
fed00000-fed003ff : HPET 2
fee00000-fee00fff : Local APIC
fff00000-ffffffff : reserved
100000000-21fffffff : System RAM
next prev parent reply other threads:[~2008-09-30 2:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-20 15:17 What's the SB600 64-bit DMA problem? George Spelvin
2008-09-20 22:28 ` Grant Grundler
2008-09-21 0:15 ` George Spelvin
2008-09-24 0:30 ` Mark Nelson
2008-09-24 9:46 ` Tejun Heo
2008-09-24 10:19 ` Huang, Shane
2008-09-25 3:24 ` George Spelvin
2008-09-26 14:06 ` Tejun Heo
2008-09-28 21:04 ` George Spelvin
2008-09-28 23:20 ` Tejun Heo
2008-09-29 4:08 ` George Spelvin
2008-09-29 4:25 ` Tejun Heo
2008-09-30 2:00 ` George Spelvin [this message]
2008-10-01 3:57 ` Tejun Heo
2008-10-01 13:26 ` George Spelvin
2008-09-26 16:04 ` Grant Grundler
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=20080930020002.26564.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=Shane.Huang@amd.com \
--cc=grundler@google.com \
--cc=htejun@gmail.com \
--cc=jgarzik@redhat.com \
--cc=linux-ide@vger.kernel.org \
--cc=mdnelson8@gmail.com \
/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.