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,
jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org,
iommu@lists.linux-foundation.org, tglx@linutronix.de
Subject: Re: [PATCH 9/9] x86: Detect whether we should use Xen SWIOTLB.
Date: Wed, 28 Jul 2010 15:52:50 -0700 [thread overview]
Message-ID: <4C50B4C2.2070807@zytor.com> (raw)
In-Reply-To: <20100728223816.GB32739@phenom.dumpdata.com>
On 07/28/2010 03:38 PM, Konrad Rzeszutek Wilk wrote:
>
> Long term I think the driverization is the way to go, and..
>
> I think the flow a). check if we need SWIOTLB b), check all IOMMUs, c).
> recheck SWIOTLB in case no IOMMUs volunteered MUST be preserved
> irregardless if we driverize the IOMMUs/SWIOTLB or not.
>
> Perhaps we should get together at one of these Linux conferences and
> think this one through? Beers on me.
>
I don't understand point (a) here. (c) simply seems like the fallback
case, and in the case we are actively forcing swiotlb we simply skip
step (b).
-hpa
next prev parent reply other threads:[~2010-07-28 22:53 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 [this message]
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
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=4C50B4C2.2070807@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