mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yasunori Goto <y-goto@jp.fujitsu.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@elte.hu, tony.luck@intel.com, linux-kernel@vger.kernel.org,
	linux-ia64@vger.kernel.org
Subject: Re: [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices
Date: Fri, 30 Jan 2009 20:24:13 +0900	[thread overview]
Message-ID: <20090130184210.4A8E.E1E9C6FF@jp.fujitsu.com> (raw)
In-Reply-To: <20090130083654U.fujita.tomonori@lab.ntt.co.jp>

> On Fri, 30 Jan 2009 07:54:07 +0900
> Yasunori Goto <y-goto@jp.fujitsu.com> wrote:
> 
> > > On Thu, 29 Jan 2009 20:41:07 +0900
> > > Yasunori Goto <y-goto@jp.fujitsu.com> wrote:
> > > 
> > > > > Before the dma ops unification, IA64 always uses GFP_DMA for
> > > > > dma_alloc_coherent like:
> > > > > 
> > > > > #define dma_alloc_coherent(dev, size, handle, gfp)	\
> > > > > 	platform_dma_alloc_coherent(dev, size, handle, (gfp) | GFP_DMA)
> > > > > 
> > > > > This GFP_DMA enforcement doesn't make sense for IOMMUs since they can
> > > > > do address translation to give addresses that devices can access
> > > > > to. The IOMMU drivers ignore the zone flag. However, this is still
> > > > > necessary for swiotlb since it can't do address translation.
> > > > > 
> > > > > We don't always need to use GFP_DMA for swiotlb. We need GFP_DMA for
> > > > > devices incapable of 64bit DMA.
> > > > > 
> > > > > This patch is sorta updated version of:
> > > > > 
> > > > > http://marc.info/?l=linux-kernel&m=122638215612705&w=2
> > > > > 
> > > > > Signed-off-by: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> > > > > Cc: Yasunori Goto <y-goto@jp.fujitsu.com>
> > > > > ---
> > > > >  arch/ia64/kernel/pci-swiotlb.c |   10 +++++++++-
> > > > >  1 files changed, 9 insertions(+), 1 deletions(-)
> > > > > 
> > > > > diff --git a/arch/ia64/kernel/pci-swiotlb.c b/arch/ia64/kernel/pci-swiotlb.c
> > > > > index 717ad4f..573f02c 100644
> > > > > --- a/arch/ia64/kernel/pci-swiotlb.c
> > > > > +++ b/arch/ia64/kernel/pci-swiotlb.c
> > > > > @@ -13,8 +13,16 @@
> > > > >  int swiotlb __read_mostly;
> > > > >  EXPORT_SYMBOL(swiotlb);
> > > > >  
> > > > > +static void *ia64_swiotlb_alloc_coherent(struct device *dev, size_t size,
> > > > > +					 dma_addr_t *dma_handle, gfp_t gfp)
> > > > > +{
> > > > > +	if (dev->coherent_dma_mask != DMA_64BIT_MASK)
> > > > > +		gfp |= GFP_DMA;
> > > > > +	return swiotlb_alloc_coherent(dev, size, dma_handle, gfp);
> > > > > +}
> > > > > +
> > > > >  struct dma_map_ops swiotlb_dma_ops = {
> > > > > -	.alloc_coherent = swiotlb_alloc_coherent,
> > > > > +	.alloc_coherent = ia64_swiotlb_alloc_coherent,
> > > > >  	.free_coherent = swiotlb_free_coherent,
> > > > >  	.map_page = swiotlb_map_page,
> > > > >  	.unmap_page = swiotlb_unmap_page,
> > > > > -- 
> > > > > 1.6.0.6
> > > > 
> > > > 
> > > > Though I may be misunderstanding something, this initialization seems to be
> > > > called only when CONFIG_IA64_DIG_VTD is on.
> > > 
> > > Hmm, what's 'this initialization'?
> > > 
> > > This patch always sets swiotlb_dma_ops.alloc_coherent to
> > > ia64_swiotlb_alloc_coherent.
> > 
> > I tested your patch, but, ia64_swiotlb_alloc_coherent() was not called with
> > CONFIG_GENERIC.
> 
> You use the generic kernel on a DIG box, right? If so, yeah, there is
> something wrong.
> 
> 
> > swiotlb_dma_ops is set by pci_swiotlb_init().
> > However, it seems to be not called when CONFIG_IA64_DIG/Generic configuration.
> 
> You are talking about setting dma_ops to swiotlb_dma_ops?
> 
> I think that swiotlb_dma_init() also sets dma_ops to swiotlb_dma_ops.

Certainly.
I overlooked the 7th patch of your unifying dma_ops patch set.
ia64_swiotlb_alloc_coherent was called when I tested again.
I'm sorry.

However, GFP_DMA is still always on in ia64_swiotlb_alloc_coherent()
regardless of the value of dev->coherent_dma_mask.

After following patch applied, GFP_DMA is set correctly by your patch.
Am I still overlooking other your patch?

Bye.



---
 arch/ia64/include/asm/dma-mapping.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Index: dma_fix_test/arch/ia64/include/asm/dma-mapping.h
===================================================================
--- dma_fix_test.orig/arch/ia64/include/asm/dma-mapping.h       2009-01-30 19:36:33.000000000 +0900
+++ dma_fix_test/arch/ia64/include/asm/dma-mapping.h    2009-01-30 20:20:06.000000000 +0900
@@ -71,7 +71,7 @@ static inline void *dma_alloc_coherent(s
                                       dma_addr_t *daddr, gfp_t gfp)
 {
        struct dma_mapping_ops *ops = platform_dma_get_ops(dev);
-       return ops->alloc_coherent(dev, size, daddr, gfp | GFP_DMA);
+       return ops->alloc_coherent(dev, size, daddr, gfp);
 }

 static inline void dma_free_coherent(struct device *dev, size_t size,


-- 
Yasunori Goto 


  reply	other threads:[~2009-01-30 11:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-28 12:53 FUJITA Tomonori
2009-01-28 12:53 ` [PATCH -tip 2/3] IA64: fix VT-d dma_mapping_error FUJITA Tomonori
2009-01-28 12:53   ` [PATCH -tip 3/3] intel-iommu: make dma mapping functions static FUJITA Tomonori
2009-01-29 11:41 ` [PATCH -tip 1/3] IA64: fix swiotlb alloc_coherent for non DMA_64BIT_MASK devices Yasunori Goto
2009-01-29 11:54   ` FUJITA Tomonori
2009-01-29 22:54     ` Yasunori Goto
2009-01-29 23:36       ` FUJITA Tomonori
2009-01-30 11:24         ` Yasunori Goto [this message]
2009-02-02 23:28           ` FUJITA Tomonori
2009-02-03  1:52             ` Yasunori Goto
2009-01-29 13:40 ` 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=20090130184210.4A8E.E1E9C6FF@jp.fujitsu.com \
    --to=y-goto@jp.fujitsu.com \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-ia64@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tony.luck@intel.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®