WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH 05/11] xen pci platform device driver

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH 05/11] xen pci platform device driver
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 10 May 2010 11:48:16 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, Sheng Yang <sheng@xxxxxxxxxxxxxxx>
Delivery-date: Mon, 10 May 2010 08:49:50 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1273501247-27267-6-git-send-email-stefano.stabellini@xxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <> <1273501247-27267-6-git-send-email-stefano.stabellini@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
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@xxxxxxxxxxxxx>
> Signed-off-by: Sheng Yang <sheng@xxxxxxxxxxxxxxx>
> ---
>  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?

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>