similar to: git pull for Jens for 3.8 (xen-blkback related, feature-persistent).

Hey Roger, I am seeing this weird behavior when using #linux-next + stable/for-jens-3.8 tree. Basically I can do ''pvscan'' on xvd* disk and quite often I get checksum errors: # pvscan /dev/xvdf PV /dev/xvdf2 VG VolGroup00 lvm2 [18.88 GiB / 0 free] PV /dev/dm-14 VG vg_x86_64-pvhvm lvm2 [4.00 GiB / 68.00 MiB free] PV /dev/dm-12 VG vg_i386-pvhvm lvm2

Hey Jens, Please pull: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-jens-3.5 it has two critical fixes to deal with 32/64 guest/host combinations when sending DISCARD commands. They weren''t properly sent resulting in the guest crashing (https://bugzilla.redhat.com/show_bug.cgi?id=824641) The fix is in the backend (blkback) and the frontend has some extra

Hey, Linus released this Saturday v3.5 and there were quite a few of interesting components/fixes/features that went in! Going to go down the list of what shortlog provided: - Less MSR traps when using AMD machines - so better performance. [andre] - The APIC IPI interface works - which means that ''perf'' in the initial domain works. So no more lockups. Also with some

Hey Linus, I am heading out for a week of vacation but would hate to have missed the merge window. Hence sending it out early in anticipation that you will release v3.9 on Sunday. With that said, please git pull the following tag: git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git stable/for-linus-3.10-rc0-tag which has just a couple of features and mostly bug-fixes. Here is the

Hello Roger Pau Monne, The patch 4d4f270f1880: "xen-blkback: move free persistent grants code" from Nov 16, 2012, leads to the following warning: drivers/block/xen-blkback/blkback.c:238 free_persistent_gnts() warn: 'persistent_gnt' was already freed. drivers/block/xen-blkback/blkback.c 232 pages[segs_to_unmap] = persistent_gnt->page; 233

Hello Roger Pau Monne, The patch 4d4f270f1880: "xen-blkback: move free persistent grants code" from Nov 16, 2012, leads to the following warning: drivers/block/xen-blkback/blkback.c:238 free_persistent_gnts() warn: 'persistent_gnt' was already freed. drivers/block/xen-blkback/blkback.c 232 pages[segs_to_unmap] = persistent_gnt->page; 233

Hello Roger Pau Monne, The patch 0a8704a51f38: "xen/blkback: Persistent grant maps for xen blk drivers" from Oct 24, 2012, leads to the following warning: drivers/block/xen-blkfront.c:807 blkif_free() warn: 'persistent_gnt' was already freed. 807 llist_for_each_entry(persistent_gnt, all_gnts, node) { 808

Hello Roger Pau Monne, The patch 0a8704a51f38: "xen/blkback: Persistent grant maps for xen blk drivers" from Oct 24, 2012, leads to the following warning: drivers/block/xen-blkfront.c:807 blkif_free() warn: 'persistent_gnt' was already freed. 807 llist_for_each_entry(persistent_gnt, all_gnts, node) { 808

Hi Jeremy, I backported the branch I have in linux-next plus some older PV on HVM fixes to stable-2.6.32.x. Please pull: git://xenbits.xen.org/people/sstabellini/linux-pvhvm.git stable-2.6.32-pvhvm Ian Campbell (11): xen: do not respond to unknown xenstore control requests xen: use new schedop interface for suspend xen: switch to new schedop hypercall by default. xen:

Hi, One of our colleagues spotted a problem in xentop. Sometimes the VBD_WSECT value suddenly becomes unreasonably high, and it turned out xentop reads /sys/bus/xen-backend/devices/vbd-(domid)-(devID)/statistics/wr_sect into an unsigned long long. That value is exposed by blkback, and among other stat counters, it''s a signed integer: drivers/block/xen-blkback/common.h struct

With the introduction of indirect segments we can receive requests with a number of segments bigger than the maximum number of allowed iovecs in a bios, so make sure that blkback doesn't try to allocate a bios with more iovecs than BIO_MAX_PAGES Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> ---

When backend disconnect, sync IO requests to the disk. Signed-off-by: Joe Jin <joe.jin@oracle.com> Cc: Jens Axboe <jaxboe@fusionio.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Ian Campbell <Ian.Campbell@eu.citrix.com> --- drivers/block/xen-blkback/xenbus.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/block/xen-blkback/xenbus.c

Moving grant ref handles from blkbk to pending_req will allow us to get rid of the shared blkbk structure. Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: xen-devel@lists.xen.org --- drivers/block/xen-blkback/blkback.c | 16 ++++------------ 1 files changed, 4 insertions(+), 12 deletions(-) diff --git

>>> On 03.04.13 at 15:25, William Dauchy <wdauchy@gmail.com> wrote: > On Wed, Apr 3, 2013 at 3:01 PM, Jan Beulich <JBeulich@suse.com> wrote: >> Iirc we requested the earlier commit to be removed from stable >> trees, and I think Greg also did so. > > I''m sorry but I''m unable to find a revert of 01c681d in stable tree. ChangeLog-3.8.3

On Sun, Jul 22, 2012 at 03:34:42PM +0200, Ingo Molnar wrote: > Linus, > > Please pull the latest timers-core-for-linus git tree from: > > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git timers-core-for-linus > > HEAD: eec19d1a0d04c80e66eef634f7b8f460f2ca5643 Merge branch ''linus'' into timers/core > > Continued cleanups of the core

[ Please CC me I am not subscribed to this ML ] Original posting from [1]... <QUOTE> On Thu, Feb 25, 2016 at 05:13:05PM +0100, Sedat Dilek via llvm-dev wrote: > Build-time increased approx. 1h from 2 to 3 hours when using CMAKE > instead of CONFIGURE/MAKE (logs deleted for LLVM v3.8.0rc2). > Building always done with one single parallel-compile-jobs. > When using CMAKE

This patch contains fixes for persistent grants implementation v2: * handle == 0 is a valid handle, so initialize grants in blkback setting the handle to BLKBACK_INVALID_HANDLE instead of 0. Reported by Konrad Rzeszutek Wilk. * new_map is a boolean, use "true" or "false" instead of 1 and 0. Reported by Konrad Rzeszutek Wilk. * blkfront announces the

Add a note to the public headers regarding how to get the VCPU ID for HVM guests (on x86). Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Cc: Jan Beulich <jbeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Matt Wilson <msw@amazon.com> --- This is what Linux PVHVM does AFAIK, and also what I've been

Add a note to the public headers regarding how to get the VCPU ID for HVM guests (on x86). Signed-off-by: Roger Pau Monné <roger.pau@citrix.com> Acked-by: Matt Wilson <msw@amazon.com> Cc: Jan Beulich <jbeulich@suse.com> Cc: Keir Fraser <keir@xen.org> Cc: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> Cc: Matt Wilson <msw@amazon.com> --- This is what Linux PVHVM

Hi Linus, These patches make it possible to inhibit the Xen emulated device unplug on the kernel command line (mostly "Just In Case") and renames xen_emul_unplug=ignore to the clearer xen_emul_unplug=unnecessary. Since it changes the name of a command line option we''d like to get it in before 2.6.36 proper. The third changeset is a pure cleanup which you could ignore for