From: Andrew Morton <akpm@linux-foundation.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: alexisb@us.ibm.com, linux-kernel@vger.kernel.org,
muli@il.ibm.com, mingo@elte.hu
Subject: Re: [PATCH -mm] fix per-device dma_mapping_ops support
Date: Tue, 1 Jul 2008 21:06:20 -0700 [thread overview]
Message-ID: <20080701210620.1e90e1fd.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080702124328B.fujita.tomonori@lab.ntt.co.jp>
On Wed, 2 Jul 2008 12:43:39 +0900 FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp> wrote:
> My initial patch has some bugs (wasn't tested because I don't have
> Calgary hardware) but Alexis fixed the problems and submitted new one
> (he successfully tested it). I had one minor comment about it then he
> submitted another one.
>
> http://marc.info/?l=linux-kernel&m=121329005131176&w=2
>
> I think that it can get into mainline with the dma-mapping-per-device
> patchset.
>
> As we discussed, we could do better but it takes some time. I think
> that it's better to fix Calgary problems now. Then I'll try to improve
> dma-mapping-per-device stuff.
>
> Here's a repost of Alexis's latest patch.
>
> Thanks,
>
> =
> From: Alexis Bruemmer <alexisb@us.ibm.com>
> Subject: [PATCH] x86 calgary: fix handling of devces that aren't behind the Calgary
>
> The calgary code can give drivers addresses above 4GB which is very
> bad for hardware that is only 32bit DMA addressable.
>
> With this patch, the calgary code sets the global dma_ops to swiotlb
> or nommu properly, and the dma_ops of devices behind the
> Calgary/CalIOC2 to calgary_dma_ops. So the calgary code can handle
> devices safely that aren't behind the Calgary/CalIOC2.
>
OK.. Looks like this needs to be folded into
dma-mapping-x86-per-device-dma_mapping_ops-support prior to merging to
keep everything bisect-happy.
> + if(translation_enabled(tbl))
checkpatch?
btw, x86_64 allmodconfig says:
arch/x86/kernel/pci-calgary_64.c: In function 'build_detail_arrays':
arch/x86/kernel/pci-calgary_64.c:1263: warning: comparison is always false due t
which is
if (rio_table_hdr->num_scal_dev > MAX_NUMNODES){
so I'll cancel that order for a 512-node Calgary machine ;)
next prev parent reply other threads:[~2008-07-02 4:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 8:21 [PATCH -mm] fix per-device dma_mapping_ops support FUJITA Tomonori
2008-07-01 21:52 ` Alexis Bruemmer
2008-07-02 2:37 ` FUJITA Tomonori
2008-07-02 2:48 ` Andrew Morton
2008-07-02 3:43 ` FUJITA Tomonori
2008-07-02 4:06 ` Andrew Morton [this message]
2008-07-02 4:29 ` FUJITA Tomonori
2008-07-02 4:46 ` Andrew Morton
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=20080701210620.1e90e1fd.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=alexisb@us.ibm.com \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=muli@il.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox