All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>, hpa@zytor.com
Cc: jeremy@goop.org, Ian.Campbell@citrix.com,
	albert_herranz@yahoo.es, x86@kernel.org,
	linux-kernel@vger.kernel.org, jbarnes@virtuousgeek.org,
	iommu@lists.linux-foundation.org, tglx@linutronix.de
Subject: Re: [PATCH 9/9] x86: Detect whether we should use Xen SWIOTLB.
Date: Mon, 2 Aug 2010 12:42:34 -0400	[thread overview]
Message-ID: <20100802164234.GC6961@phenom.dumpdata.com> (raw)
In-Reply-To: <20100803010025R.fujita.tomonori@lab.ntt.co.jp>

On Tue, Aug 03, 2010 at 01:01:08AM +0900, FUJITA Tomonori wrote:
> On Mon, 02 Aug 2010 08:47:53 -0700
> "H. Peter Anvin" <hpa@zytor.com> wrote:
> 
> > On 08/02/2010 08:43 AM, FUJITA Tomonori wrote:
> > > 
> > > That's the difficult part because IOMMUs are not
> > > interdependent. Hardware IOMMUs are related with swiotlb. GART and
> > > AMD-IOMMU are too.
> > > 
> > > We could invent sorta IOMMU register interface and driver-ize IOMMUs
> > > but they can't be interdependent completely.
> > 
> > Of course.  However, we need there to be as much structure to it as
> > there can be.
> 
> Ok, let's see if Konrad can invent something clean.

<chuckles> Thank you for your vote of confidence.
> 
> But his attempt to create "swiotlb iommu function array" and "hardware
> iommu function array" looks like to makes the code more unreadable.

Let me go to my favorite coffee shop and think this one through.
Can I get concession for putting the original patch in (the simple, dumb one),
and then:
 - start working on the IOMMU register interface without having to try
   to get it done for 2.6.36, and
 - do the driverization as a seperate cleanup.


  reply	other threads:[~2010-08-02 16:44 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-27 16:59 [PATCH] Xen-SWIOTLB v0.8.6 used for Xen PCI pass through for PV guests Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 1/9] xen: use _PAGE_IOMAP in ioremap to do machine mappings Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 2/9] xen: Allow unprivileged Xen domains to create iomap pages Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 3/9] xen: Rename the balloon lock Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 4/9] xen: Add xen_create_contiguous_region Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 5/9] vmap: add flag to allow lazy unmap to be disabled at runtime Konrad Rzeszutek Wilk
2010-07-27 16:59 ` [PATCH 6/9] xen/mmu: inhibit vmap aliases rather than trying to clear them out Konrad Rzeszutek Wilk
2010-07-27 17:00 ` [PATCH 7/9] swiotlb-xen: SWIOTLB library for Xen PV guest with PCI passthrough Konrad Rzeszutek Wilk
2010-07-27 17:00 ` [PATCH 8/9] pci-swiotlb-xen: Add glue code to setup dma_ops utilizing xen_swiotlb_* functions Konrad Rzeszutek Wilk
2010-07-27 17:00 ` [PATCH 9/9] x86: Detect whether we should use Xen SWIOTLB Konrad Rzeszutek Wilk
2010-07-27 19:03   ` H. Peter Anvin
2010-07-27 19:41     ` Konrad Rzeszutek Wilk
2010-07-27 23:36       ` FUJITA Tomonori
2010-07-28  0:19         ` H. Peter Anvin
2010-07-28  0:52           ` FUJITA Tomonori
2010-07-28 22:38             ` Konrad Rzeszutek Wilk
2010-07-28 22:52               ` H. Peter Anvin
2010-07-29  7:17                 ` FUJITA Tomonori
2010-07-29 13:44                   ` H. Peter Anvin
2010-07-29 16:05                   ` Konrad Rzeszutek Wilk
2010-08-02 15:25                     ` Konrad Rzeszutek Wilk
2010-08-02 15:30                       ` H. Peter Anvin
2010-08-02 15:43                         ` FUJITA Tomonori
2010-08-02 15:47                           ` H. Peter Anvin
2010-08-02 16:01                             ` FUJITA Tomonori
2010-08-02 16:42                               ` Konrad Rzeszutek Wilk [this message]
2010-08-02 16:53                                 ` H. Peter Anvin
2010-08-03  5:35                                 ` FUJITA Tomonori

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=20100802164234.GC6961@phenom.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=albert_herranz@yahoo.es \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=hpa@zytor.com \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@kernel.org \
    /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.