search for: xen_xenbus_frontend

From: Randy Dunlap <randy.dunlap at oracle.com> When a driver kconfig symbol =m and it selects another symbol, that other symbol will also be =m (unless something else causes it to be =y), so when XEN_BLKDEV_FRONTEND=m and/or XEN_NETDEV_FRONTEND=m, then XEN_XENBUS_FRONTEND=m, but that won't build (build error message below). Changing XEN_XENBUS_FRONTEND from a tristate to a bool makes it be =y (builtin) any time that it is selected, so there is no build error. arch/x86/pci/built-in.o: In function `xenbus_register_frontend': include/xen/xenbus.h:115: undefin...

From: Randy Dunlap <randy.dunlap at oracle.com> When a driver kconfig symbol =m and it selects another symbol, that other symbol will also be =m (unless something else causes it to be =y), so when XEN_BLKDEV_FRONTEND=m and/or XEN_NETDEV_FRONTEND=m, then XEN_XENBUS_FRONTEND=m, but that won't build (build error message below). Changing XEN_XENBUS_FRONTEND from a tristate to a bool makes it be =y (builtin) any time that it is selected, so there is no build error. arch/x86/pci/built-in.o: In function `xenbus_register_frontend': include/xen/xenbus.h:115: undefin...

From: Randy Dunlap <randy.dunlap at oracle.com> When a driver kconfig symbol =m and it selects another symbol, that other symbol will also be =m (unless something else causes it to be =y), so when XEN_BLKDEV_FRONTEND=m and/or XEN_NETDEV_FRONTEND=m, then XEN_XENBUS_FRONTEND=m, but that won't build (build error message below). Changing XEN_XENBUS_FRONTEND from a tristate to a bool makes it be =y (builtin) any time that it is selected, so there is no build error. arch/x86/pci/built-in.o: In function `xenbus_register_frontend': include/xen/xenbus.h:115: undefin...

...N is enabled the gntdev driver will be compiled as a module. Signed-off-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig index 07bec09..af5d986 100644 --- a/drivers/xen/Kconfig +++ b/drivers/xen/Kconfig @@ -76,6 +76,7 @@ config XEN_XENBUS_FRONTEND config XEN_GNTDEV tristate "userspace grant access device driver" depends on XEN + default m select MMU_NOTIFIER help Allows userspace processes to use grants. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.x...

...g index e7068c5..1969ea1 100644 --- a/drivers/video/Kconfig +++ b/drivers/video/Kconfig @@ -2245,7 +2245,7 @@ config XEN_FBDEV_FRONTEND select FB_SYS_IMAGEBLIT select FB_SYS_FOPS select FB_DEFERRED_IO - select INPUT_XEN_KBDDEV_FRONTEND + select INPUT_XEN_KBDDEV_FRONTEND if INPUT_MISC select XEN_XENBUS_FRONTEND default y help -- 1.7.11.7

Hi All, xen stable-2.6.31/master doesn''t seem to compile: CC [M] drivers/watchdog/w83877f_wdt.o CC [M] drivers/watchdog/w83977f_wdt.o CC [M] drivers/watchdog/machzwd.o CC [M] drivers/watchdog/sbc_epx_c3.o CC [M] drivers/watchdog/wm8350_wdt.o CC [M] drivers/watchdog/softdog.o CC drivers/xen/grant-table.o CC drivers/xen/features.o CC

Hello, The following patches are a solution to a problem we have encountered when using the Xen hypervisor: - Need Pxx/Cxx states to save on power consumption when using Xen (we do want those datacenters to consume less power!), - Also need to figure out the Turbo mode so that the scheduler can properly boost a core for CPU bound guests. In essence the Xen hypervisor requires that

...06,14 +106,14 @@ config PCI_PF_STUB When in doubt, say N. config XEN_PCIDEV_FRONTEND - tristate "Xen PCI Frontend" - depends on X86 && XEN - select PCI_XEN + tristate "Xen PCI Frontend" + depends on X86 && XEN + select PCI_XEN select XEN_XENBUS_FRONTEND - default y - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + default y + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from...

...06,14 +106,14 @@ config PCI_PF_STUB When in doubt, say N. config XEN_PCIDEV_FRONTEND - tristate "Xen PCI Frontend" - depends on X86 && XEN - select PCI_XEN + tristate "Xen PCI Frontend" + depends on X86 && XEN + select PCI_XEN select XEN_XENBUS_FRONTEND - default y - help - The PCI device frontend driver allows the kernel to import arbitrary - PCI devices from a PCI backend to support PCI driver domains. + default y + help + The PCI device frontend driver allows the kernel to import arbitrary + PCI devices from...

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as

Hello, I''ve previously been successful with Xen4 and VT-d on other systems. I am having trouble getting VT-d passthrough working to a WinXP domain with DX58SO (Q45) motherboard and i7 930 CPU. VT-d is enabled in bios, xm info shows hvm_directio capability, I have iommu=1 set, I have the devices bound to pciback on dom0 cmdline, xm pci-list-assignable-devices shows the devices as