From: Joerg Bashir <brak@archive.org>
To: Muli Ben-Yehuda <mulix@mulix.org>
Cc: Robert Hancock <hancockr@shaw.ca>,
linux-kernel <linux-kernel@vger.kernel.org>,
ak@suse.de, jgarzik@pobox.com
Subject: Re: PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution
Date: Sun, 02 Apr 2006 00:24:26 -0800 [thread overview]
Message-ID: <442F8A3A.9000305@archive.org> (raw)
In-Reply-To: <20060402080035.GA7856@granada.merseine.nu>
Muli Ben-Yehuda wrote:
> On Sat, Apr 01, 2006 at 11:51:26PM -0800, Joerg Bashir wrote:
>
>
>>I saw a lot of patches come through by Muli but am not sure they address
>>this issue, do they?
>
>
> No, I'm afraid not - our patches are to support a different
> IOMMU, and it looks like this problem is gart specific. I'll go dig
> through the archive, but is there consensus on how to solve this bug
> and it's just a question of doing the work, or is the root cause
> unknown?
I'm unsure. Here is an earlier message from this thread with info and a
glimmer of hope.
------------------------------------
Andi Kleen wrote:
> On Friday 03 March 2006 22:27, Allen Martin wrote:
>
>
>> nForce4 has 64 bit (40 bit AMD64) DMA in the SATA controller. We gave
>> the docs to Jeff Garzik under NDA. He posted some non functional driver
>> code to linux-ide earlier this week that has the 64 bit registers and
>> structures although it doesn't make use of them. Someone could pick
>> this up if they wanted to work on it though.
>
>
>
> Thanks for the correction. Sounds nice - hopefully we'll get a driver
soon.
> I guess it's in good hands with Jeff for now.
I'll happen but not soon. Motivation is low at NV and here as well,
since newer NV is AHCI. The code in question, "NV ADMA", is essentially
legacy at this point -- though I certainly acknowledge the large current
installed base. Just being honest about the current state of things...
Jeff
>
> Cheers,
> Muli
next prev parent reply other threads:[~2006-04-02 8:24 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5Mq18-1Na-21@gated-at.bofh.it>
[not found] ` <5MqNc-2Y5-3@gated-at.bofh.it>
[not found] ` <5MqX4-39H-21@gated-at.bofh.it>
[not found] ` <5MyAS-5zh-5@gated-at.bofh.it>
2006-03-07 0:15 ` PCI-DMA: Out of IOMMU space on x86-64 (Athlon64x2), with solution Robert Hancock
2006-04-02 7:51 ` Joerg Bashir
2006-04-02 8:00 ` Muli Ben-Yehuda
2006-04-02 8:24 ` Joerg Bashir [this message]
2006-04-02 11:16 ` Andi Kleen
2006-03-03 21:27 Allen Martin
2006-03-03 22:12 ` Andi Kleen
2006-03-03 22:23 ` Jeff Garzik
2006-03-03 22:32 ` Andi Kleen
2006-03-04 6:34 ` Michael Monnerie
-- strict thread matches above, loose matches on Subject: below --
2006-03-01 23:23 Michael Monnerie
2006-03-02 1:03 ` Andi Kleen
2006-03-02 9:59 ` Jens Axboe
2006-03-03 8:16 ` Chris Wedgwood
2006-03-03 11:00 ` Andi Kleen
[not found] ` <200603021316.38077.ak@suse.de>
[not found] ` <4406E226.4050806@pobox.com>
2006-03-02 12:26 ` Andi Kleen
2006-03-02 12:31 ` Jens Axboe
2006-03-02 12:33 ` Jeff Garzik
[not found] ` <20060302123033.GL4329@suse.de>
2006-03-02 13:09 ` Andi Kleen
2006-03-02 13:10 ` Jens Axboe
2006-03-02 13:33 ` Andi Kleen
2006-03-02 13:33 ` Jens Axboe
2006-03-02 13:46 ` Andi Kleen
2006-03-02 13:49 ` Jens Axboe
2006-03-02 13:58 ` Andi Kleen
2006-03-02 14:14 ` Jens Axboe
2006-03-02 14:35 ` Andi Kleen
2006-03-02 14:38 ` Jens Axboe
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=442F8A3A.9000305@archive.org \
--to=brak@archive.org \
--cc=ak@suse.de \
--cc=hancockr@shaw.ca \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mulix@mulix.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