xenbus.c File Reference

#include <linux/module.h>
#include <linux/init.h>
#include <linux/list.h>
#include <linux/vmalloc.h>
#include <linux/workqueue.h>
#include <xen/xenbus.h>
#include <xen/events.h>
#include <asm/xen/pci.h>
#include "pciback.h"

Go to the source code of this file.

Macros
#define	INVALID_EVTCHN_IRQ   (-1)

Functions
	module_param (passthrough, bool, S_IRUGO)
	MODULE_PARM_DESC (passthrough,"Option to specify how to export PCI topology to guest:\n"" 0 - (default) Hide the true PCI topology and makes the frontend\n"" there is a single PCI bus with only the exported devices on it.\n"" For example, a device at 03:05.0 will be re-assigned to 00:00.0\n"" while second device at 02:1a.1 will be re-assigned to 00:01.1.\n"" 1 - Passthrough provides a real view of the PCI topology to the\n"" frontend (for example, a device at 06:01.b will still appear at\n"" 06:01.b to the frontend). This is similar to how Xen 2.0.x\n"" exposed PCI devices to its driver domains. This may be required\n"" for drivers which depend on finding their hardward in certain\n"" bus/slot locations.")
int __init	xen_pcibk_xenbus_register (void)
void __exit	xen_pcibk_xenbus_unregister (void)

Variables
struct workqueue_struct *	xen_pcibk_wq
struct xen_pcibk_backend *__read_mostly	xen_pcibk_backend

Macro Definition Documentation

#define INVALID_EVTCHN_IRQ   (-1)

Definition at line 16 of file xenbus.c.

Function Documentation

module_param	(	passthrough	,
		bool	,
		S_IRUGO
	)

MODULE_PARM_DESC	(	passthrough	,
		"Option to specify how to export PCI topology to guest:\n"" 0 - (default) Hide the true PCI topology and makes the frontend\n"" there is a single PCI bus with only the exported devices on it.\n"" For	example,
		a device at 03:05.0 will be re-assigned to 00:00.0\n""while second device at 02:1a.1 will be re-assigned to 00:01.1.\n""1-Passthrough provides a real view of the PCI topology to the\n""frontend(for example, a device at 06:01.b will still appear at\n""06:01.b to the frontend).This is similar to how Xen 2.0.x\n""exposed PCI devices to its driver domains.This may be required\n""for drivers which depend on finding their hardward in certain\n""bus/slot locations."
	)

int __init xen_pcibk_xenbus_register

(

void

)

Definition at line 722 of file xenbus.c.

void __exit xen_pcibk_xenbus_unregister

(

void

)

Definition at line 737 of file xenbus.c.

Variable Documentation

struct xen_pcibk_backend* __read_mostly xen_pcibk_backend

Definition at line 720 of file xenbus.c.

struct workqueue_struct* xen_pcibk_wq

Definition at line 17 of file xenbus.c.