All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: George Spelvin <linux@horizon.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: Wed, 01 Oct 2008 12:57:46 +0900	[thread overview]
Message-ID: <48E2F53A.6000104@gmail.com> (raw)
In-Reply-To: <20080930020002.26564.qmail@science.horizon.com>

George Spelvin wrote:
> 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)

This is determined by the BIOS and I don't think it ever puts it over
32bit boundary.

> - 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)

The first three are controlled by consistent_dma_mask while the last
one is controlled by dma_mask, so maybe setting only
consistent_dma_mask to 32bit could help.  The problem is how to verify
them.  You'll need to dig the list and bugzilla to look for reporters
who reported failure on 64bit DMA and verify it actually fixes the
problem.  It can be tricky as the problem doesn't seem to appear for
all users.

> 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

Where are these numbers from?

-- 
tejun

  reply	other threads:[~2008-10-01  3:59 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
2008-10-01  3:57                         ` Tejun Heo [this message]
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=48E2F53A.6000104@gmail.com \
    --to=htejun@gmail.com \
    --cc=Shane.Huang@amd.com \
    --cc=grundler@google.com \
    --cc=jgarzik@redhat.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux@horizon.com \
    --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.