mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	joerg.roedel@amd.com, mingo@redhat.com, tglx@linutronix.de,
	hpa@zytor.com, linux-kernel@vger.kernel.org,
	iommu@lists.linux-foundation.org, muli@il.ibm.com
Subject: Re: [PATCH 0/8] x86 dma_*_coherent rework patchset v2
Date: Fri, 22 Aug 2008 09:09:31 +0200	[thread overview]
Message-ID: <20080822070931.GY14110@elte.hu> (raw)
In-Reply-To: <200808210807.05996.jbarnes@virtuousgeek.org>


* Jesse Barnes <jbarnes@virtuousgeek.org> wrote:

> > Surely, this patchset should be for 2.6.28.
> >
> > Can you send this via the x86 tree instead of pci?
> >
> > - IOMMU code is arch stuff rather than pci.
> > - We can avoid a mistake such as the previous one.
> 
> Yeah I was thinking 2.6.28 too, via the x86 tree.  The problem last 
> time was that I sent it too soon (I misunderstood Ingo when he said it 
> was ready) so we broke the build on some non-x86 platforms.  I don't 
> think that'll be an issue this time, but we may as well push through 
> x86 anyway; I agree that IOMMU is really a platform feature more than 
> a PCI one.

yeah, GART/IOMMU has been historically a more platform specific thing 
although there's certainly no hard boundaries. This code will show up in 
linux-next as well soon, so there's plenty of time to discover and fix 
any cross-arch breakages. (if any)

and if the PCI tree becomes very active in this area that would make the 
movement of these commits over there more practical we can do that too 
at any point of time, it's all kept separate in tip/x86/iommu, purely 
based on Linus's tree. The blessings of 160+ topic branches ;-)

	Ingo

  reply	other threads:[~2008-08-22  7:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-19 14:32 Joerg Roedel
2008-08-19 14:32 ` [PATCH 1/8] x86: add alloc_coherent dma_ops callback to GART driver Joerg Roedel
2008-08-21 14:16   ` FUJITA Tomonori
2008-08-21 15:17     ` Joerg Roedel
2008-08-21 17:28     ` [PATCH] x86: make gart_alloc_coherent return zeroed memory Joerg Roedel
2008-08-21 23:19       ` FUJITA Tomonori
2008-08-22  6:35         ` Joerg Roedel
2008-08-22  6:41           ` Ingo Molnar
2008-08-22  6:55             ` Joerg Roedel
2008-08-22  6:36         ` Ingo Molnar
2008-08-19 14:32 ` [PATCH 2/8] x86: add free_coherent dma_ops callback to GART driver Joerg Roedel
2008-08-19 14:32 ` [PATCH 3/8] x86: add free_coherent dma_ops callback to Calgary IOMMU driver Joerg Roedel
2008-08-19 14:32 ` [PATCH 4/8] x86: add alloc_coherent dma_ops callback to NOMMU driver Joerg Roedel
2008-08-19 14:32 ` [PATCH 5/8] x86: add free_coherent " Joerg Roedel
2008-08-19 14:32 ` [PATCH 6/8] x86: cleanup dma_*_coherent functions Joerg Roedel
2008-08-19 14:32 ` [PATCH 7/8] x86: move dma_*_coherent functions to include file Joerg Roedel
2008-08-19 14:32 ` [PATCH 8/8] x86, AMD IOMMU: remove obsolete FIXME comment Joerg Roedel
2008-08-20  9:46 ` [PATCH 0/8] x86 dma_*_coherent rework patchset v2 Ingo Molnar
2008-08-20 10:18   ` [PATCH] dma-coherent: export dma_[alloc|release]_from_coherent methods Ingo Molnar
2008-08-20 11:28     ` Joerg Roedel
2008-08-20 17:39   ` [PATCH 0/8] x86 dma_*_coherent rework patchset v2 Jesse Barnes
2008-08-21 12:00     ` Ingo Molnar
2008-08-21 14:16       ` FUJITA Tomonori
2008-08-21 15:07         ` Jesse Barnes
2008-08-22  7:09           ` Ingo Molnar [this message]
2008-08-21 15:20         ` Joerg Roedel
2008-08-21 14:16   ` FUJITA Tomonori
2008-08-21 15:12     ` FUJITA Tomonori
2008-08-22  6:44       ` Ingo Molnar
2008-08-22  6:57         ` FUJITA Tomonori
2008-08-22  7:04           ` Ingo Molnar
2008-08-22  7:29             ` FUJITA Tomonori
2008-08-22  8:23               ` 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=20080822070931.GY14110@elte.hu \
    --to=mingo@elte.hu \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hpa@zytor.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=joerg.roedel@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=muli@il.ibm.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome