public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	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, 02 Aug 2010 08:30:38 -0700	[thread overview]
Message-ID: <4C56E49E.6070102@zytor.com> (raw)
In-Reply-To: <20100802152552.GA4732@phenom.dumpdata.com>

On 08/02/2010 08:25 AM, Konrad Rzeszutek Wilk wrote:
> hpa, are your concerns that a) inserting a sub-system call in the
> generic code is not good. Or b) that we have five IOMMUs (counting SWIOTLB in that
> category) and that we don't jettison from memory the ones we don't need
> (that would be the primary goal of driverization of those IOMMUs,
> right?). Or c) we should remove all sub-system detect calls (Calgary, AMD,
> Intel, AGP) altogether from pci-dma.c and depend more on
> x86_init.iommu structure (perhaps expend it?)

Sorry, had to deal with other stuff.

Basically, a) and c) are the issues, with a) being the more immediate;
the amount of code left in memory is relatively small and as such I'm
not too concerned with that aspect specifically.

With five IOMMUs we're well past the point where we need to have a clean
and generic interface instead of having everything be ad hoc and
interdependent.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2010-08-02 15:31 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 [this message]
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
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=4C56E49E.6070102@zytor.com \
    --to=hpa@zytor.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=albert_herranz@yahoo.es \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=iommu@lists.linux-foundation.org \
    --cc=jbarnes@virtuousgeek.org \
    --cc=jeremy@goop.org \
    --cc=konrad.wilk@oracle.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox