From: Jeremy Fitzhardinge <jeremy@goop.org>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: mingo@elte.hu, x86@kernel.org, linux-kernel@vger.kernel.org,
xen-devel@lists.xensource.com
Subject: Re: [GIT PULL] xen: swiotlb support for Xen dom0
Date: Mon, 11 May 2009 09:59:38 -0700 [thread overview]
Message-ID: <4A08597A.6090408@goop.org> (raw)
In-Reply-To: <20090511123626N.fujita.tomonori@lab.ntt.co.jp>
FUJITA Tomonori wrote:
> As I said before, I don't like such weak hacks added for dom0. We will
> merge dom0 support?
>
That's in progress. But they're largely the same hooks that ppc is
using as well.
J
next prev parent reply other threads:[~2009-05-11 17:00 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-08 0:17 [GIT PULL] xen: swiotlb support for Xen dom0 Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 1/9] xen: make sure swiotlb allocation is physically contigious Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 7:47 ` [Xen-devel] [PATCH 1/9] xen: make sure swiotlb allocation isphysically contigious Jan Beulich
2009-05-08 7:47 ` Jan Beulich
2009-05-08 15:51 ` [Xen-devel] " Jeremy Fitzhardinge
2009-05-08 15:51 ` Jeremy Fitzhardinge
2009-05-11 3:40 ` [PATCH 1/9] xen: make sure swiotlb allocation is physically contigious FUJITA Tomonori
2009-05-11 13:55 ` Joerg Roedel
2009-05-11 18:42 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 2/9] xen swiotlb: fixup swiotlb is chunks smaller than MAX_CONTIG_ORDER Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 3/9] xen: add hooks for mapping phys<->bus addresses in swiotlb Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-11 3:40 ` FUJITA Tomonori
2009-05-11 14:11 ` Joerg Roedel
2009-05-11 14:11 ` Joerg Roedel
2009-05-08 0:17 ` [PATCH 4/9] xen/swiotlb: add swiotlb_arch_range_needs_mapping hook for xen Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-11 3:40 ` FUJITA Tomonori
2009-05-11 14:16 ` Joerg Roedel
2009-05-11 14:16 ` Joerg Roedel
2009-05-08 0:17 ` [PATCH 5/9] xen: enable swiotlb for xen domain 0 Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-11 3:40 ` FUJITA Tomonori
2009-05-11 14:21 ` Joerg Roedel
2009-05-11 14:21 ` Joerg Roedel
2009-05-08 0:17 ` [PATCH 6/9] swiotlb: use swiotlb_alloc_boot to allocate emergency pool Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 7/9] xen/swiotlb: improve comment on gfp flags in xen_alloc_coherent() Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 8/9] xen/swiotlb: add sync functions Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 0:17 ` [PATCH 9/9] xen/swiotlb: update to new new dma_ops Jeremy Fitzhardinge
2009-05-08 0:17 ` Jeremy Fitzhardinge
2009-05-08 11:19 ` [GIT PULL] xen: swiotlb support for Xen dom0 Ingo Molnar
2009-05-08 11:19 ` Ingo Molnar
2009-05-11 3:40 ` FUJITA Tomonori
2009-05-11 16:59 ` Jeremy Fitzhardinge [this message]
2009-05-11 22:45 ` FUJITA Tomonori
2009-05-11 22:45 ` FUJITA Tomonori
2009-05-11 13:04 ` Ingo Molnar
2009-05-11 13:04 ` Ingo Molnar
2009-05-11 16:57 ` Jeremy Fitzhardinge
2009-05-11 16:57 ` Jeremy Fitzhardinge
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=4A08597A.6090408@goop.org \
--to=jeremy@goop.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xensource.com \
/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.