From: Yinghai Lu <yinghai@kernel.org>
To: Matthew Wilcox <matthew@wil.cx>, Ingo Molnar <mingo@elte.hu>,
Jeremy Fitzhardinge <jeremy@goop.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: linux-pci@vger.kernel.org,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Joerg Roedel <joerg.roedel@amd.com>,
FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>,
the arch/x86 maintainers <x86@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [GIT PULL] xen: dom0 support for PCI access
Date: Fri, 08 May 2009 12:46:25 -0700 [thread overview]
Message-ID: <4A048C11.1050702@kernel.org> (raw)
In-Reply-To: <20090508124436.GT8112@parisc-linux.org>
Matthew Wilcox wrote:
> On Fri, May 08, 2009 at 01:10:24PM +0200, Ingo Molnar wrote:
>> ( Cc:-ed PCI folks. Original thread with patches is on lkml. There's
>> a few details that affect non-Xen PCI code too - and it would be
>> nice to see feedback on this general method as well, from the PCI
>> experts . )
>
> I read over the top seven commits here:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=xen-tip/dom0/pci
> and they all seem reasonable to me as far as they affect other code.
> I'm assuming that Xen people know what they're doing with respect to
> the Xen-only code ;-)
1. pcibios_set_cache_line_size looks could be __init
2. pci_xen_init and some xen_ function all for domU aka pv? that naming looks confusing.
YH
next prev parent reply other threads:[~2009-05-08 19:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 21:45 [GIT PULL] xen: dom0 support for PCI access Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 01/11] xen: Don't disable the I/O space Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 02/11] xen: Allow unprivileged Xen domains to create iomap pages Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 03/11] Xen: Rename the balloon lock Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-08 2:01 ` [Xen-devel] " Isaku Yamahata
2009-05-08 2:01 ` Isaku Yamahata
2009-05-11 19:00 ` [Xen-devel] " Jeremy Fitzhardinge
2009-05-12 2:47 ` Isaku Yamahata
2009-05-12 2:47 ` Isaku Yamahata
2009-05-07 21:45 ` [PATCH 04/11] xen: Add xen_create_contiguous_region Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 05/11] x86/PCI: Clean up pci_cache_line_size Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 06/11] x86/PCI: Enable scanning of all pci functions Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 07/11] Xen/x86/PCI: Add support for the Xen PCI subsytem Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-11 9:40 ` Joerg Roedel
2009-05-11 20:32 ` Jeremy Fitzhardinge
2009-05-11 20:32 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 08/11] xen/swiotlb: use dma_alloc_from_coherent to get device coherent memory Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 09/11] x86/pci: make sure _PAGE_IOMAP it set on pci mappings Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 10/11] xen/pci: clean up Kconfig a bit Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-07 21:45 ` [PATCH 11/11] xen: checkpatch cleanups Jeremy Fitzhardinge
2009-05-07 21:45 ` Jeremy Fitzhardinge
2009-05-08 11:10 ` [GIT PULL] xen: dom0 support for PCI access Ingo Molnar
2009-05-08 11:10 ` Ingo Molnar
2009-05-08 12:44 ` Matthew Wilcox
2009-05-08 19:46 ` Yinghai Lu [this message]
2009-05-08 21:05 ` Jeremy Fitzhardinge
2009-05-09 13:32 ` Matthew Wilcox
2009-05-09 15:43 ` Jeremy Fitzhardinge
2009-05-09 20:08 ` Matthew Wilcox
2009-05-11 12:49 ` Ingo Molnar
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=4A048C11.1050702@kernel.org \
--to=yinghai@kernel.org \
--cc=fujita.tomonori@lab.ntt.co.jp \
--cc=ink@jurassic.park.msu.ru \
--cc=jbarnes@virtuousgeek.org \
--cc=jeremy@goop.org \
--cc=joerg.roedel@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=matthew@wil.cx \
--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.