similar to: [PATCH linux-2.6.18-xen] blkback: don''t call vbd_size() if bd_disk is NULL

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

Hi all, I add a blkback QoS patch. You can config(dynamic/static) different I/O speed for different VM disk by this patch. ---------------------------------------------------------------------------- diff -urNp blkback/blkback.c blkback-qos/blkback.c --- blkback/blkback.c 2011-06-22 07:54:19.000000000 +0800 +++ blkback-qos/blkback.c 2011-06-22 07:53:18.000000000 +0800 @@ -44,6 +44,11 @@

Patrick, there following patches fix xenpaging for me. Granttable handling is incomplete. If a page is gone, a GNTST_eagain should be returned to the caller to inidcate the hypercall has to be retried after a while, until the page is available again. Please review. Olaf _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

In blkback driver, after I/O requests are submitted to Dom-0 block I/O subsystem, blkback goes to ''sleep'' effectively without letting blkfront know about it (req_event isn''t set appropriately). Hence blkfront doesn''t notify blkback when it submits a new I/O thus delaying the ''dispatch'' of the new I/O to Dom-0 block I/O subsystem. The new I/O is

This is a cherry pick of two patches that add support for guest paged out frames in the XCP 2.6.32 dom0 patch queue. First patch propagates the ENOENT returned by the hypervisor in the case of a paged out page, all the way up the call chain to the MMAPBATCH_V2 ioctl. The ioctl is mainly used to harvest those return values and retry. The second patch adds retry loops to all backend grant

When I submitted the qcow2 patch for blktap, suggestions came up that the qemu block drivers should be used also for blktap to eliminate the current code duplication in ioemu and blktap. The attached patch adds support for a tap:ioemu pseudo driver. Devices using this driver won''t use tapdisk (containing the code duplication) any more, but will connect to the qemu-dm of the domain. In

Hi Jens, this series removes the revalidate_disk() function, which has been a really odd duck in the last years. The prime reason why most people use it is because it propagates a size change from the gendisk to the block_device structure. But it also calls into the rather ill defined ->revalidate_disk method which is rather useless for the callers. So this adds a new helper to just

Hi All, We contributed the problem when CD-ROM was changed as follows. There was especially no comment though we confirmed the correction method. Therefore, the patch that corrects these problems is contributed. Signed-off-by: Takanori Kasai <kasai.takanori@jp.fujitsu.com> Best Regards, --- Takanori Kasai ----- Original Message ----- From: "Kasai Takanori"

Also remove unused xenbus_{,un}map_ring(), adjust types, and clean up header inclusion. Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/drivers/xen/blkback/blkback.c +++ b/drivers/xen/blkback/blkback.c @@ -41,6 +41,8 @@ #include <linux/list.h> #include <linux/delay.h> #include <xen/balloon.h> +#include <xen/evtchn.h> +#include <xen/gnttab.h>

As usual, written and (build-)tested on 2.6.27.4 and made apply to the 2.6.18 tree without further testing. Signed-off-by: Jan Beulich <jbeulich@novell.com> Index: head-2008-11-04/drivers/xen/blktap/blktap.c =================================================================== --- head-2008-11-04.orig/drivers/xen/blktap/blktap.c 2008-10-01 16:35:04.000000000 +0200 +++

Changes: tools/blktap: remove unneeded pointer dereferencing in convert_dev_name_to_num tools/blktap: constify string arrays in convert_dev_name_to_num tools/blktap: fix params and physical-device parsing tools/blktap: remove unneeded pointer dereferencing from img2qcow.c tools/blktap: remove unneeded pointer dereferencing from qcow2raw.c tools/blktap2: fix build errors caused by Werror in

Hi have 4 dom0 with debian lenny running xen. When I run ps axf|grep xvd I see it''s different on diferent dom0s. dom0-A 15677 ? S< 0:00 \_ [blkback.139.xvd] 15678 ? S< 0:38 \_ [blkback.139.xvd] 17015 ? S< 0:00 \_ [blkback.140.xvd] 17016 ? S< 2:34 \_ [blkback.140.xvd] 21309 ? S< 0:00 \_ [blkback.142.xvd] 21310 ?

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

Is exporting a block device from one DomU to another supported? ''xm block-attach'' appears to support it based on the command line options displayed but maybe it''s one of those things that doesn''t work because nobody ever uses it? I''m wondering about accessing a VSS snapshot from a windows DomU in Dom0 (or another DomU). In theory, GPLPV should be able

I think you need this patch otherwise you will be passing uninitialised data from the stack to GNTTABOP_unmap_grant_ref in fast_flush_area. Also, I think the memset of the pending_grant_handles array should happen before you start using them so I moved it to before blkif_xenbus_init. I''m not sure if this is necessary or it might possibly have to go even earlier. Signed off by Harry

Hi Everyone, When you want to use ionice to limit the amount of disk a DomU has, due to have to run ionice on every blkback process? Incidently, what is the format of the blkback process? I see the following in ps aux: blkback.xx.xvda blkback.xx.xvda1 blkback.xx.xvd where xx appears to be the domain ID. I''m curious as to the last few letters mean? Thanks

Hey Roger, I tested the feature-persistent patches and they rolled out succesfully out of the test system. This is a bootup test with 32/64 dom0, 32/64 PV/PVHVM domU, with new and old OS-es. I am thinking to send a git pull on Friday to Jens so that they will be part of Linux v3.8.

I just noticed that the linux block backend does not copy the full 64 bits of the id field of a request to the associated response. The blkif.h states that this is echoed in the response. An unsigned long in make_response is used as an intermediary. This would sure be helpful to me if the full 64 bits were echoed. - Bruce Rogers _______________________________________________ Xen-devel

Hi all, I want to use ionice command change the priority of threads of blkback(in domain0) for each corresponding blkfront . However, I do not know how to recognize which is the thread for the corresponding blkfront using ps aux. Anybody can give me some advice? Thanks in advance! -- View this message in context:

Hi,all In the vbd blkback driver(linux/drivers/xen/blkback/blkback.c), when function dispatch_rw_block_io() try to do the real I/O job, it will do a sanity check on I/O request sent from DomU in the following code fragment: ... 430 for (i = 0; i < nseg; i++) { 431 uint32_t flags; 432 433 seg[i].nsec = req->seg[i].last_sect -