From: Ingo Molnar <mingo@elte.hu>
To: Joerg Roedel <joerg.roedel@amd.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
mingo@redhat.com, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org
Subject: Re: [PATCH] x86: fix nommu_alloc_coherent allocation with NULL device argument
Date: Fri, 5 Sep 2008 12:49:10 +0200 [thread overview]
Message-ID: <20080905104910.GB17776@elte.hu> (raw)
In-Reply-To: <20080905104049.GY3189@amd.com>
* Joerg Roedel <joerg.roedel@amd.com> wrote:
> I agree with this patch in principle. It fixes the problem. But I
> think we should evaluate if we can change the dma_mask of the
> fallback_dev to 24 bit.
ok - i kept this commit for now in tip/x86/iommu:
# 551b454: x86: gart alloc_coherent doesn't need to check NULL device argument
and will let you guys sort out how to do the others.
Ingo
next prev parent reply other threads:[~2008-09-05 10:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 8:58 [PATCH 0/3] fix alloc_coherent allocation issues (tip/x86/iommu) FUJITA Tomonori
2008-09-05 8:58 ` [PATCH] x86: fix nommu_alloc_coherent allocation with NULL device argument FUJITA Tomonori
2008-09-05 8:58 ` [PATCH] x86: use __GFP_NORETRY in the case of GFP_DMA with pci-nommu FUJITA Tomonori
2008-09-05 8:58 ` [PATCH] x86: gart alloc_coherent doesn't need to check NULL device argument FUJITA Tomonori
2008-09-05 10:41 ` Joerg Roedel
2008-09-05 10:43 ` [PATCH] x86: use __GFP_NORETRY in the case of GFP_DMA with pci-nommu Joerg Roedel
2008-09-06 12:18 ` FUJITA Tomonori
2008-09-08 11:41 ` Joerg Roedel
2008-09-05 10:40 ` [PATCH] x86: fix nommu_alloc_coherent allocation with NULL device argument Joerg Roedel
2008-09-05 10:49 ` Ingo Molnar [this message]
2008-09-05 11:56 ` Joerg Roedel
2008-09-06 12:18 ` FUJITA Tomonori
2008-09-05 9:11 ` [PATCH 0/3] fix alloc_coherent allocation issues (tip/x86/iommu) FUJITA Tomonori
2008-09-05 10:45 ` Ingo Molnar
2008-09-08 17:35 ` Ingo Molnar
2008-09-08 18:06 ` FUJITA Tomonori
2008-09-08 18:15 ` Ingo Molnar
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=20080905104910.GB17776@elte.hu \
--to=mingo@elte.hu \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=iommu@lists.linux-foundation.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
all inboxes | Powered by JetHome®