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: linux-kernel@vger.kernel.org, iommu@lists.linux-foundation.org,
	Jeremy Fitzhardinge <jeremy@goop.org>,
	alex.williamson@redhat.com,
	FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
	Albert Herranz <albert_herranz@yahoo.es>,
	Ian Campbell <Ian.Campbell@citrix.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	x86@kernel.org, Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 9/9] x86: Detect whether we should use Xen SWIOTLB.
Date: Tue, 27 Jul 2010 12:03:56 -0700	[thread overview]
Message-ID: <4C4F2D9C.4020303@zytor.com> (raw)
In-Reply-To: <1280250002-20279-10-git-send-email-konrad.wilk@oracle.com>

On 07/27/2010 10:00 AM, Konrad Rzeszutek Wilk wrote:
> It is paramount that we call pci_xen_swiotlb_detect before
> pci_swiotlb_detect as both implementations use the 'swiotlb'
> and 'swiotlb_force' flags. The pci-xen_swiotlb_detect inhibits
> the swiotlb_force and swiotlb flag so that the native SWIOTLB
> implementation is not enabled when running under Xen.
> 
> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
> Acked-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com>
> Cc: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
> Cc: Albert Herranz <albert_herranz@yahoo.es>
> Cc: Ian Campbell <Ian.Campbell@citrix.com>
> Cc: Thomas Gleixner <tglx@linutronix.de>
> Cc: "H. Peter Anvin" <hpa@zytor.com>
> Cc: x86@kernel.org
> Cc: Jesse Barnes <jbarnes@virtuousgeek.org>
> ---
>  arch/x86/kernel/pci-dma.c |    7 +++++--
>  1 files changed, 5 insertions(+), 2 deletions(-)
> 

Is there any way we can abstract this out a bit more instead of crapping
on generic code?

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


  reply	other threads:[~2010-07-27 19:05 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 [this message]
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
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=4C4F2D9C.4020303@zytor.com \
    --to=hpa@zytor.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=albert_herranz@yahoo.es \
    --cc=alex.williamson@redhat.com \
    --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