From: Andi Kleen <ak@suse.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>,
Ingo Molnar <mingo@elte.hu>, Tejun Heo <htejun@gmail.com>,
linux-ide@vger.kernel.org
Subject: Re: 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM
Date: Wed, 14 Nov 2007 17:46:26 +0100 [thread overview]
Message-ID: <200711141746.26793.ak@suse.de> (raw)
In-Reply-To: <alpine.LFD.0.9999.0711141633400.3265@localhost.localdomain>
> The AHCI code falls back to 32bit DMA in that case. Which in turn
> causes the problem seen by Srihari. There is not much printk sticking
> necessary, the code is simply not handling this.
What code is not handling what?
IOMMU merging should be always safe. If it is not the driver should
not submit things in a single SG list.
> So the main option
> right now seems to revert the iommu_merge patch.
I don't think that is the correct fix.
-Andi
next prev parent reply other threads:[~2007-11-14 16:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-14 11:55 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-14 12:17 ` Andi Kleen
2007-11-14 16:43 ` Thomas Gleixner
2007-11-14 16:46 ` Andi Kleen [this message]
2007-11-19 22:47 ` Srihari Vijayaraghavan
2007-11-20 1:03 ` Tejun Heo
2007-11-20 15:34 ` Thomas Gleixner
2007-11-20 15:44 ` Andi Kleen
2007-11-20 18:29 ` Thomas Gleixner
2007-11-20 18:43 ` Andi Kleen
2007-11-20 16:36 ` 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM II Andi Kleen
2007-11-20 19:07 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2007-11-08 22:41 2.6.24-rc & SB600 AHCI no go on >=4GB of RAM Srihari Vijayaraghavan
2007-11-09 4:00 ` Tejun Heo
2007-11-12 10:56 ` Srihari Vijayaraghavan
2007-11-13 0:06 ` Srihari Vijayaraghavan
2007-11-13 3:08 ` Tejun Heo
2007-11-13 11:17 ` Srihari Vijayaraghavan
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=200711141746.26793.ak@suse.de \
--to=ak@suse.de \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sriharivijayaraghavan@yahoo.com.au \
--cc=tglx@linutronix.de \
/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.