search for: linfo

Displaying 20 results from an estimated 24 matches for "linfo".

Did you mean: info
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 09/13] lguest64 devices
...include <linux/highmem.h> +#include <linux/uaccess.h> +#include <asm/lguest.h> +#include <asm/lguest_user.h> +#include "lguest.h" + +static struct list_head dma_hash[64]; + +/* FIXME: allow multi-page lengths. */ +static int check_dma_list(struct lguest_guest_info *linfo, + const struct lguest_dma *dma) +{ + unsigned int i; + + for (i = 0; i < LGUEST_MAX_DMA_SECTIONS; i++) { + if (!dma->len[i]) + return 1; + if (!lguest_address_ok(linfo, dma->addr[i])) + goto kill; + if (dma->len[i] > PAGE_SIZE) + goto kill; + /* We could do over a page,...
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 09/13] lguest64 devices
...include <linux/highmem.h> +#include <linux/uaccess.h> +#include <asm/lguest.h> +#include <asm/lguest_user.h> +#include "lguest.h" + +static struct list_head dma_hash[64]; + +/* FIXME: allow multi-page lengths. */ +static int check_dma_list(struct lguest_guest_info *linfo, + const struct lguest_dma *dma) +{ + unsigned int i; + + for (i = 0; i < LGUEST_MAX_DMA_SECTIONS; i++) { + if (!dma->len[i]) + return 1; + if (!lguest_address_ok(linfo, dma->addr[i])) + goto kill; + if (dma->len[i] > PAGE_SIZE) + goto kill; + /* We could do over a page,...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...; + +#define HV_OFFSET(x) (typeof(x))((unsigned long)(x)+lguest_hv_offset) + +unsigned long lguest_hv_addr; +unsigned long lguest_hv_offset; +int lguest_hv_pages; + +int lguest_vcpu_pages; +int lguest_vcpu_order; + +DEFINE_MUTEX(lguest_lock); + +int lguest_address_ok(const struct lguest_guest_info *linfo, u64 addr) +{ + return addr / PAGE_SIZE < linfo->pfn_limit; +} + +u8 lhread_u8(struct lguest_vcpu *vcpu, u64 addr) +{ + u8 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u8 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", add...
2007 Apr 18
1
[RFC/PATCH LGUEST X86_64 03/13] lguest64 core
...; + +#define HV_OFFSET(x) (typeof(x))((unsigned long)(x)+lguest_hv_offset) + +unsigned long lguest_hv_addr; +unsigned long lguest_hv_offset; +int lguest_hv_pages; + +int lguest_vcpu_pages; +int lguest_vcpu_order; + +DEFINE_MUTEX(lguest_lock); + +int lguest_address_ok(const struct lguest_guest_info *linfo, u64 addr) +{ + return addr / PAGE_SIZE < linfo->pfn_limit; +} + +u8 lhread_u8(struct lguest_vcpu *vcpu, u64 addr) +{ + u8 val = 0; + + if (!lguest_address_ok(vcpu->guest, addr) + || get_user(val, (u8 __user *)addr) != 0) + kill_guest_dump(vcpu, "bad read address %llx", add...
2014 Dec 11
0
[PATCH RFC v6 11/20] s390x/virtio-ccw: support virtio-1 set_vq format
...ues for the subchannel are in guest memory. */ -static int virtio_ccw_set_vqs(SubchDev *sch, uint64_t addr, uint32_t align, - uint16_t index, uint16_t num) +static int virtio_ccw_set_vqs(SubchDev *sch, VqInfoBlock *info, + VqInfoBlockLegacy *linfo) { VirtIODevice *vdev = virtio_ccw_get_vdev(sch); + uint16_t index = info ? info->index : linfo->index; + uint16_t num = info ? info->num : linfo->num; + uint64_t desc = info ? info->desc : linfo->queue; if (index > VIRTIO_PCI_QUEUE_MAX) { return...
2014 Dec 11
0
[PATCH RFC v6 11/20] s390x/virtio-ccw: support virtio-1 set_vq format
...ues for the subchannel are in guest memory. */ -static int virtio_ccw_set_vqs(SubchDev *sch, uint64_t addr, uint32_t align, - uint16_t index, uint16_t num) +static int virtio_ccw_set_vqs(SubchDev *sch, VqInfoBlock *info, + VqInfoBlockLegacy *linfo) { VirtIODevice *vdev = virtio_ccw_get_vdev(sch); + uint16_t index = info ? info->index : linfo->index; + uint16_t num = info ? info->num : linfo->num; + uint64_t desc = info ? info->desc : linfo->queue; if (index > VIRTIO_PCI_QUEUE_MAX) { return...
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 04/13] Useful debugging
...st_dump_trace(vcpu, regs); +} + +struct guest_ksym_stuff { + unsigned long *addresses; + unsigned long num_syms; + u8 *names; + u8 *token_table; + u16 *token_index; + unsigned long *markers; +}; + +static struct lguest_text_ptr *get_text_segs(struct lguest_vcpu *vcpu) +{ + struct lguest_guest_info *linfo = vcpu->guest; + struct lguest_text_ptr *segs, **p; + struct lguest_text_ptr *g; + unsigned long addr; + int i; + + if (!linfo->lguest_data) + return NULL; + + addr = lhread_u64(vcpu, (u64)&linfo->lguest_data->text); + if (!addr) + return NULL; + + g = (struct lguest_text_ptr*)add...
2007 Apr 18
0
[RFC/PATCH LGUEST X86_64 04/13] Useful debugging
...st_dump_trace(vcpu, regs); +} + +struct guest_ksym_stuff { + unsigned long *addresses; + unsigned long num_syms; + u8 *names; + u8 *token_table; + u16 *token_index; + unsigned long *markers; +}; + +static struct lguest_text_ptr *get_text_segs(struct lguest_vcpu *vcpu) +{ + struct lguest_guest_info *linfo = vcpu->guest; + struct lguest_text_ptr *segs, **p; + struct lguest_text_ptr *g; + unsigned long addr; + int i; + + if (!linfo->lguest_data) + return NULL; + + addr = lhread_u64(vcpu, (u64)&linfo->lguest_data->text); + if (!addr) + return NULL; + + g = (struct lguest_text_ptr*)add...
2010 Aug 03
2
Error: Incorrect password length
...path = /home writable = yes browseable = no [netlogon] path = /usr/netlogon read only = yes [mi_user] #The other required DATA to be shared from /data path = /home/data/mi_user writable = yes public = yes [gdocs] #G: drive path = /home/data/gdocs writable = yes public = yes [linfo] # H: drive path = /home/data/linfo writable = yes public = yes [mapba] #K: drive path = /home/data/mapba writable = yes public = yes [ccad55] #L: drive path = /home/data/ccad55 writable = yes public = yes [qadocs] #Q: drive path = /home/data/qadocs writable = yes public = yes [...
2014 Nov 25
15
[PATCH RFC v2 00/12] qemu: towards virtio-1 host support
Hi, here's the next version of my virtio-1 qemu patchset. Using virtio-1 virtio-blk and virtio-net devices with a guest kernel built from <1416829787-14252-1-git-send-email-mst at redhat.com> still seems to work for the virtio-ccw transport. Changes from v1: - rebased against current master - don't advertise VERSION_1 for all devices, make devices switch it on individually
2014 Nov 25
15
[PATCH RFC v2 00/12] qemu: towards virtio-1 host support
Hi, here's the next version of my virtio-1 qemu patchset. Using virtio-1 virtio-blk and virtio-net devices with a guest kernel built from <1416829787-14252-1-git-send-email-mst at redhat.com> still seems to work for the virtio-ccw transport. Changes from v1: - rebased against current master - don't advertise VERSION_1 for all devices, make devices switch it on individually
2014 Nov 26
15
[PATCH RFC v3 00/12] qemu: towards virtio-1 host support
Next version of virtio-1 patches for qemu. Only change from v2 is splitting out the vring accessors into a separate header file - should hopefully fix the build issues. Cornelia Huck (9): virtio: cull virtio_bus_set_vdev_features virtio: support more feature bits s390x/virtio-ccw: fix check for WRITE_FEAT virtio: introduce legacy virtio devices virtio: allow virtio-1 queue layout
2014 Nov 26
15
[PATCH RFC v3 00/12] qemu: towards virtio-1 host support
Next version of virtio-1 patches for qemu. Only change from v2 is splitting out the vring accessors into a separate header file - should hopefully fix the build issues. Cornelia Huck (9): virtio: cull virtio_bus_set_vdev_features virtio: support more feature bits s390x/virtio-ccw: fix check for WRITE_FEAT virtio: introduce legacy virtio devices virtio: allow virtio-1 queue layout
2014 Nov 27
22
[PATCH RFC v4 00/16] qemu: towards virtio-1 host support
Yet another version of the virtio-1 support patches. This one has seen some (very) light testing with the virtio-1 guest support patches currently on vhost-next. Changes from v3: - Add support for FEATURES_OK. We refuse to set features after the driver has set this in the status field, and we allow to fail setting the status if the features are inconsistent. - Add missing virtio-1 changes
2014 Nov 27
22
[PATCH RFC v4 00/16] qemu: towards virtio-1 host support
Yet another version of the virtio-1 support patches. This one has seen some (very) light testing with the virtio-1 guest support patches currently on vhost-next. Changes from v3: - Add support for FEATURES_OK. We refuse to set features after the driver has set this in the status field, and we allow to fail setting the status if the features are inconsistent. - Add missing virtio-1 changes
2014 Oct 07
18
[PATCH RFC 00/11] qemu: towards virtio-1 host support
This patchset aims to get us some way to implement virtio-1 compliant and transitional devices in qemu. Branch available at git://github.com/cohuck/qemu virtio-1 I've mainly focused on: - endianness handling - extended feature bits - virtio-ccw new/changed commands Thanks go to Thomas for some preliminary work in this area. I've been able to start guests both with and without the
2014 Oct 07
18
[PATCH RFC 00/11] qemu: towards virtio-1 host support
This patchset aims to get us some way to implement virtio-1 compliant and transitional devices in qemu. Branch available at git://github.com/cohuck/qemu virtio-1 I've mainly focused on: - endianness handling - extended feature bits - virtio-ccw new/changed commands Thanks go to Thomas for some preliminary work in this area. I've been able to start guests both with and without the
2014 Dec 02
24
[PATCH RFC v5 00/19] qemu: towards virtio-1 host support
Another iteration of virtio-1 patches for qemu, as always available on git://github.com/cohuck/qemu virtio-1 This one seems to work together with the current vhost-next patches (well, I can ping :) Changes from v4: - add helpers for feature bit manipulation and checking - use 64 bit feature bits instead of 32 bit arrays - infrastructure to allow devices to offer different sets of feature bits
2014 Dec 02
24
[PATCH RFC v5 00/19] qemu: towards virtio-1 host support
Another iteration of virtio-1 patches for qemu, as always available on git://github.com/cohuck/qemu virtio-1 This one seems to work together with the current vhost-next patches (well, I can ping :) Changes from v4: - add helpers for feature bit manipulation and checking - use 64 bit feature bits instead of 32 bit arrays - infrastructure to allow devices to offer different sets of feature bits
2014 Dec 11
45
[PATCH RFC v6 00/20] qemu: towards virtio-1 host support
And yet another iteration of virtio-1 support in qemu, tested with the latest virtio kernel patches. Find it at git://github.com/cohuck/qemu virtio-1 Changes from v5: - fixed stupid bug in "virtio: support more feature bits": we need to define a proper prop backend for 64 bit wide handling... - don't negotiate revision 1 unless VERSION_1 is offered - use 64 bit wide features