search for: config_xen_balloon_memory_hotplug

...os-v4 branch). * x86/xen: during early setup, only 1:1 map the ISA region Fixes a boot failure if tboot is used. * xen/evtchn: avoid a deadlock when unbinding an event channel Fixes a potential deadlock by users (e.g., qemu, xenstored) of /dev/xen/evtchn. You may also wish to consider enabling CONFIG_XEN_BALLOON_MEMORY_HOTPLUG. The kernel bug that was causing problems is already fixed (by xen/balloon: Subtract from xen_released_pages the count that is populated) and now that dom0 will not try to auto-balloon by default, enabling this option should no longer cause problems in dom0. This option is required to increase th...

...>and Ver. 2.6.34.1. This patch cleanly applys > >to Ver. 2.6.34.1 > > Thanks. I''ve pushed this into xen.git as xen/memory-hotplug so people > can play with it more easily (but I haven''t merged it into any of the > other branches yet). Thx. > >+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >+static inline unsigned long current_target(void) > >+{ > >+ return balloon_stats.target_pages; > > Why does this need its own version? Because original version return values not bigger then initial memory allocation which does not allow memory hotplug to function. >...

...hvm.git > > repository, 2.6.34-pvhvm head, > > Good. I noticed you have some specific tests for "xen_pv_domain()" - > are there many differences between pv and hvm? No. Only those changes are needed where xen_domain()/xen_pv_domain() is used. > >>>+#ifdef CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > >>>+static inline unsigned long current_target(void) > >>>+{ > >>>+ return balloon_stats.target_pages; > >>Why does this need its own version? > >Because original version return values not bigger > >then initial memory allocation which does...

Hi, everyone! We google a lot, but can''t find how to config the pvscsi on our ubuntu13.04 PV on HVM.There are some links http://wiki.xen.org/wiki/Paravirtualized_SCSI http://wiki.xen.org/wiki/Xen_Configuration_File_Options And we use the config option above Configure PVSCSI devices vscsi = [ ''/dev/sdc, 0:0:0:0'' ] I pass sdc to the hvm, but in our pvhvm (ubuntu13.04)

...//bugs.centos.org/view.php?id=6561 http://bugs.centos.org/view.php?id=6570 ================================================================== kernel Changelog info from the SPEC file: * Mon Jul 22 2013 Johnny Hughes johnny at centos.org 3.4.54-8 - upgraded to upstream version 3.4.54 - Turned on CONFIG_XEN_BALLOON_MEMORY_HOTPLUG in this kernel (centos bug 6561) - added patch 131 and patch 132 per centos bug 6570 ================================================================== The following kernel.org changelog entries are applicable since the last kernel update: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog...

...CONFIG_XEN_BLKDEV_FRONTEND=yCONFIG_XEN_BLKDEV_BACKEND=yCONFIG_NETXEN_NIC=mCONFIG_XEN_NETDEV_FRONTEND=yCONFIG_XEN_NETDEV_BACKEND=mCONFIG_INPUT_XEN_KBDDEV_FRONTEND=yCONFIG_HVC_XEN=yCONFIG_HVC_XEN_FRONTEND=y# CONFIG_XEN_WDT is not setCONFIG_XEN_FBDEV_FRONTEND=y# Xen driver supportCONFIG_XEN_BALLOON=y# CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not setCONFIG_XEN_SCRUB_PAGES=yCONFIG_XEN_DEV_EVTCHN=yCONFIG_XEN_BACKEND=yCONFIG_XENFS=yCONFIG_XEN_COMPAT_XENFS=yCONFIG_XEN_SYS_HYPERVISOR=yCONFIG_XEN_XENBUS_FRONTEND=yCONFIG_XEN_GNTDEV=yCONFIG_XEN_GRANT_DEV_ALLOC=mCONFIG_SWIOTLB_XEN=yCONFIG_XEN_PCIDEV_BACKEND=mCONFIG_XEN_PRIVCMD=y# CONFIG_XEN_A...

...//bugs.centos.org/view.php?id=6561 http://bugs.centos.org/view.php?id=6570 ================================================================== kernel Changelog info from the SPEC file: * Mon Jul 22 2013 Johnny Hughes johnny at centos.org 3.4.54-8 - upgraded to upstream version 3.4.54 - Turned on CONFIG_XEN_BALLOON_MEMORY_HOTPLUG in this kernel (centos bug 6561) - added patch 131 and patch 132 per centos bug 6570 ================================================================== The following kernel.org changelog entries are applicable since the last kernel update: https://www.kernel.org/pub/linux/kernel/v3.x/ChangeLog...

...ttp://bugs.centos.org/view.php?id=6570 > > ================================================================== > > kernel Changelog info from the SPEC file: > > * Mon Jul 22 2013 Johnny Hughes johnny at centos.org 3.4.54-8 > - upgraded to upstream version 3.4.54 > - Turned on CONFIG_XEN_BALLOON_MEMORY_HOTPLUG > in this kernel (centos bug 6561) > - added patch 131 and patch 132 per centos bug 6570 > > ================================================================== > > The following kernel.org changelog entries are applicable since the last > kernel update: > > https://www....

...IG_XEN_BLKDEV_BACKEND=m # CONFIG_XEN_SCSI_FRONTEND is not set CONFIG_NETXEN_NIC=m CONFIG_XEN_NETDEV_FRONTEND=m CONFIG_XEN_NETDEV_BACKEND=m CONFIG_INPUT_XEN_KBDDEV_FRONTEND=y CONFIG_HVC_XEN=y CONFIG_HVC_XEN_FRONTEND=y CONFIG_TCG_XEN=m CONFIG_XEN_WDT=m CONFIG_XEN_FBDEV_FRONTEND=y CONFIG_XEN_BALLOON=y CONFIG_XEN_BALLOON_MEMORY_HOTPLUG=y CONFIG_XEN_BALLOON_MEMORY_HOTPLUG_LIMIT=512 CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=m CONFIG_XEN_BACKEND=y CONFIG_XENFS=m CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=m CONFIG_XEN_GRANT_DEV_ALLOC=m CONFIG_SWIOTLB_XEN=y CONFIG_XEN_TMEM...

On Thu, Apr 03, 2014 at 10:57:18PM -0400, Waiman Long wrote: > On 04/03/2014 01:23 PM, Konrad Rzeszutek Wilk wrote: > >On Wed, Apr 02, 2014 at 10:10:17PM -0400, Waiman Long wrote: > >>On 04/02/2014 04:35 PM, Waiman Long wrote: > >>>On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote: > >>>>On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote:

On Thu, Apr 03, 2014 at 10:57:18PM -0400, Waiman Long wrote: > On 04/03/2014 01:23 PM, Konrad Rzeszutek Wilk wrote: > >On Wed, Apr 02, 2014 at 10:10:17PM -0400, Waiman Long wrote: > >>On 04/02/2014 04:35 PM, Waiman Long wrote: > >>>On 04/02/2014 10:32 AM, Konrad Rzeszutek Wilk wrote: > >>>>On Wed, Apr 02, 2014 at 09:27:29AM -0400, Waiman Long wrote:

...IO_BALLOON=y # CONFIG_VIRTIO_INPUT is not set CONFIG_VIRTIO_MMIO=y # CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set # # Microsoft Hyper-V guest support # CONFIG_HYPERV=y CONFIG_HYPERV_TSCPAGE=y CONFIG_HYPERV_UTILS=y # CONFIG_HYPERV_BALLOON is not set # # Xen driver support # CONFIG_XEN_BALLOON=y # CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_GRANT_DEV_ALLOC=y CONFIG_SWIOTLB_XEN=y CONFIG_XEN_PCIDEV_BACKEND=y # CONFIG_XEN_PVCALLS_B...

...IO_BALLOON=y # CONFIG_VIRTIO_INPUT is not set CONFIG_VIRTIO_MMIO=y # CONFIG_VIRTIO_MMIO_CMDLINE_DEVICES is not set # # Microsoft Hyper-V guest support # CONFIG_HYPERV=y CONFIG_HYPERV_TSCPAGE=y CONFIG_HYPERV_UTILS=y # CONFIG_HYPERV_BALLOON is not set # # Xen driver support # CONFIG_XEN_BALLOON=y # CONFIG_XEN_BALLOON_MEMORY_HOTPLUG is not set CONFIG_XEN_SCRUB_PAGES=y CONFIG_XEN_DEV_EVTCHN=y CONFIG_XEN_BACKEND=y CONFIG_XENFS=y CONFIG_XEN_COMPAT_XENFS=y CONFIG_XEN_SYS_HYPERVISOR=y CONFIG_XEN_XENBUS_FRONTEND=y CONFIG_XEN_GNTDEV=y CONFIG_XEN_GRANT_DEV_ALLOC=y CONFIG_SWIOTLB_XEN=y CONFIG_XEN_PCIDEV_BACKEND=y # CONFIG_XEN_PVCALLS_B...

https://bugs.freedesktop.org/show_bug.cgi?id=75985 Priority: medium Bug ID: 75985 Assignee: nouveau at lists.freedesktop.org Summary: HDMI audio device only visible after rescan QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: jean-louis at

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

Not really interesting yet, this just gets us to the state where single queue boots on a current kernel. Signed-off-by: Jens Axboe <axboe at kernel.dk> --- block/Kconfig | 5 + block/Kconfig.iosched | 2 + block/blk-core.c | 427 ++++++++++++++++++-------------------- block/blk-exec.c | 14 +- block/blk-flush.c

Not really interesting yet, this just gets us to the state where single queue boots on a current kernel. Signed-off-by: Jens Axboe <axboe at kernel.dk> --- block/Kconfig | 5 + block/Kconfig.iosched | 2 + block/blk-core.c | 427 ++++++++++++++++++-------------------- block/blk-exec.c | 14 +- block/blk-flush.c