search for: hebutterworth

Here''s the latest USB code against the xen 3.0.0 release. Since the last posting this version updates the code to use the new 32 bit grant references and the latest GNTTABOP_map_grant_ref definition. I''ve also changed the definition of the virtual USB HCD to have a single port rather than seven ports with six unused. Domains importing multiple USB devices will get a HCD for

...e remaining pages after an error is encountered. All in all, this looks like a bug to me where failure to map a grant reference in the middle of a set would result in pages kept mapped in the backend when fast_flush_area fails to clean them up. Am I right? Harry. -- Harry Butterworth <harry@hebutterworth.freeserve.co.uk> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

hi, it would be extremely useful for me if someone with knowledge of how the current tools and drivers use Xenstore would be kind enough to update the Wiki with current information. I have been spending quite a lot of time trying to get my domU connected to a block device in dom0 using a home-brewed domain creation tool, and I am still at the ''Timeout connecting to device!''

Hi Folks, I just did a "hg pull -u" on my unstable tree and realized that the USB virtualization related code disappeared (e.g. /linux-2.6-xen-sparse/drivers/xen/usbfront/ and /linux-2.6-xen-sparse/drivers/xen/usbback/ directories are not present). I traced the changes to the changeset 7027:06d84bf87159 which was committed on september 22 by djm@kirby.fc.hp.com. Could someone please

Here is the usage for Fedora usage: mkinitrd [--version] [-v] [-f] [--preload <module>] [--omit-scsi-modules] [--omit-raid-modules] [--omit-lvm-modules] [--with=<module>] [--image-version] [--fstab=<fstab>] [--nocompress] [--builtin=<module>] [--nopivot] <initrd-image> <kernel-version> (ex: mkinitrd /boot/initrd-2.2.5-15.img

Andrew, I think bug 709 is caused by blktapctrl not daemonizing itself correctly and holding open a file descriptor that the xm-test python code is reading from. I''m not really very familiar with blktapctrl. If you''d like to pick up the bug or outline how you''d like it fixed---for example by copying the daemonize implementation from xenconsoled---that would be

Ewan, Keir seems to think this patch is OK. I tested it on an Intellistation A Pro for x86_64 and it works for me. I think it is low risk because it''s executed at the end of the shutdown process. Please apply. http://lists.xensource.com/archives/html/xen-devel/2006-04/msg00223.html _______________________________________________ Xen-devel mailing list

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

This patch implements a local buffer reference type for kernel virtual address space and a remote buffer reference type for buffers up to 16 pages based on grant tables. These types are used by the USB driver for bulk data transfer. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com

This patch implements the xenidc_channel interface using grant tables but leaves the channel bring-up and tear-down sequencing to a derived class (xenidc_gnttab_channel implements that). This code is part of the implementation of the xenidc_endpoint used for interdomain communication by the USB driver. Signed-off-by: Harry Butterworth <butterwo@uk.ibm.com>

This patch picks up all the fixes to the previous 13 patches that were required to get the code working now that the last four patches are reformatted and I''m able to test the code again. These fixes will go into the correct patches if I do another revision. Aside from the fixes, this patch defines the USB interdomain protocol which consists of a number of transactions and a message

Here''s the first snapshot of the USB code after updating to the new xenbus. The xenidc code provides a much higher level of abstraction than the new xenbus code so the changes didn''t affect the usb driver much. I had to put in empty frontend_changed and backend_changed functions because the new xenbus code segfaults without them. The USB code doesn''t need them because

Lots of xm-test tests are failing with console timeouts on some machines at the moment. I reproduced the problem and found it was due to some probing activity in the boot process of the -xen kernel. The behaviour of the current xm-test code is to assume that the boot process has finished after performing three one-second waits for input---when the probing activity introduces more than three