From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: xen-devel@lists.xensource.com, Sheng Yang <sheng@linux.intel.com>
Subject: Re: [PATCH 05/11] xen pci platform device driver
Date: Mon, 10 May 2010 11:48:16 -0400 [thread overview]
Message-ID: <20100510154816.GL29517@phenom.dumpdata.com> (raw)
In-Reply-To: <1273501247-27267-6-git-send-email-stefano.stabellini@eu.citrix.com>
On Mon, May 10, 2010 at 03:20:41PM +0100, Stefano Stabellini wrote:
> Add the xen pci platform device driver that is responsible
> for initializing the grant table and xenbus in PV on HVM mode.
> Few changes to xenbus and grant table are necessary to allow the delayed
> initialization in HVM mode.
> Grant table needs few additional modifications to work in HVM mode.
>
> When running on HVM the event channel upcall is never called while in
> progress because it is a normal Linux irq handler, therefore we cannot
> be sure that evtchn_upcall_pending is 0 when returning.
> For this reason if evtchn_upcall_pending is set by Xen we need to loop
> again on the event channels set pending otherwise we might loose some
> event channel deliveries.
>
> Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Signed-off-by: Sheng Yang <sheng@linux.intel.com>
> ---
> drivers/xen/Kconfig | 11 ++-
> drivers/xen/Makefile | 3 +-
> drivers/xen/events.c | 5 +-
> drivers/xen/grant-table.c | 70 +++++++++-
> drivers/xen/platform-pci.c | 236 ++++++++++++++++++++++++++++++++++
> drivers/xen/xenbus/xenbus_probe.c | 20 ++-
> include/xen/grant_table.h | 1 +
> include/xen/interface/grant_table.h | 1 +
> include/xen/interface/platform_pci.h | 45 +++++++
> include/xen/platform_pci.h | 41 ++++++
> include/xen/xenbus.h | 1 +
> 11 files changed, 417 insertions(+), 17 deletions(-)
> create mode 100644 drivers/xen/platform-pci.c
> create mode 100644 include/xen/interface/platform_pci.h
> create mode 100644 include/xen/platform_pci.h
>
> diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
> index cab100a..3e02457 100644
> --- a/drivers/xen/Kconfig
> +++ b/drivers/xen/Kconfig
> @@ -60,4 +60,13 @@ config XEN_SYS_HYPERVISOR
> Create entries under /sys/hypervisor describing the Xen
> hypervisor environment. When running native or in another
> virtual environment, /sys/hypervisor will still be present,
> - but will have no xen contents.
> \ No newline at end of file
> + but will have no xen contents.
> +
> +config XEN_PLATFORM_PCI
> + tristate "xen platform pci device driver"
> + depends on XEN
Wasn't there some XENBUS frontend depency needed here?
next prev parent reply other threads:[~2010-05-10 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-10 14:20 [PATCH 05/11] xen pci platform device driver Stefano Stabellini
2010-05-10 15:48 ` Konrad Rzeszutek Wilk [this message]
2010-05-11 11:26 ` Stefano Stabellini
2010-05-10 20:40 ` Jeremy Fitzhardinge
2010-05-11 11:53 ` Stefano Stabellini
-- strict thread matches above, loose matches on Subject: below --
2010-05-24 18:25 [PATCH 0 of 12] PV on HVM Xen Stefano Stabellini
2010-05-24 18:27 ` [PATCH 05/11] Xen PCI platform device driver Stefano Stabellini
2010-05-28 8:55 ` [Xen-devel] " Zhigang Wang
2010-05-28 14:18 ` Stefano Stabellini
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=20100510154816.GL29517@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=sheng@linux.intel.com \
--cc=stefano.stabellini@eu.citrix.com \
--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.