search for: class_id

...device_obj = device_to_hyperv_device(dev); struct hyperv_device_info device_info; memset(&device_info, 0, sizeof(struct hyperv_device_info)); - get_channel_info(device_ctx, &device_info); + get_channel_info(device_obj, &device_info); if (!strcmp(dev_attr->attr.name, "class_id")) { return sprintf(buf, "{%02x%02x%02x%02x-%02x%02x-%02x%02x-" @@ -464,7 +464,7 @@ static int vmbus_bus_init(void) { struct vmbus_driver_context *vmbus_drv_ctx = &vmbus_drv; struct hv_driver *driver = &vmbus_drv.drv_obj; - struct hyperv_device *dev_ctx = &vmbus_d...

...device_obj = device_to_hyperv_device(dev); struct hyperv_device_info device_info; memset(&device_info, 0, sizeof(struct hyperv_device_info)); - get_channel_info(device_ctx, &device_info); + get_channel_info(device_obj, &device_info); if (!strcmp(dev_attr->attr.name, "class_id")) { return sprintf(buf, "{%02x%02x%02x%02x-%02x%02x-%02x%02x-" @@ -464,7 +464,7 @@ static int vmbus_bus_init(void) { struct vmbus_driver_context *vmbus_drv_ctx = &vmbus_drv; struct hv_driver *driver = &vmbus_drv.drv_obj; - struct hyperv_device *dev_ctx = &vmbus_d...

...rn 0; } -static PCIDeviceInfo virtio_9p_info = { - .qdev.name = "virtio-9p-pci", - .qdev.size = sizeof(VirtIOPCIProxy), - .init = virtio_9p_init_pci, - .vendor_id = PCI_VENDOR_ID_REDHAT_QUMRANET, - .device_id = 0x1009, - .revision = VIRTIO_PCI_ABI_VERSION, - .class_id = 0x2, - .qdev.props = (Property[]) { - DEFINE_PROP_BIT("ioeventfd", VirtIOPCIProxy, flags, VIRTIO_PCI_FLAG_USE_IOEVENTFD_BIT, true), - DEFINE_PROP_UINT32("vectors", VirtIOPCIProxy, nvectors, 2), - DEFINE_VIRTIO_COMMON_FEATURES(VirtIOPCIProxy, host_featu...

Hi, I have a table for an 1 week exam result for many classes in school, like this: Day Class_ID Test Result 1 Monday 1 Paper Passed 2 Tuesday 1 Oral Passed 3 Friday 1 Paper Passed 4 Monday 3 Paper Passed 5 Sunday 3 Oral Passed 6 Monday 3 Paper Passe...

...= 0; @@ -73,7 +74,7 @@ int blk_vsc_initialize(struct hv_driver *driver) /* ASSERT(stor_driver->RingBufferSize >= (PAGE_SIZE << 1)); */ driver->name = g_blk_driver_name; - memcpy(&driver->dev_type, &g_blk_device_type, sizeof(struct hv_guid)); + memcpy(&driver->class_id, &g_blk_device_type, sizeof(struct hv_guid)); stor_driver->request_ext_size = sizeof(struct storvsc_request_extension); diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c index 36a0adb..194f648 100644 --- a/drivers/staging/hv/blkvsc_drv.c +++ b/drivers/stagi...

...= 0; @@ -73,7 +74,7 @@ int blk_vsc_initialize(struct hv_driver *driver) /* ASSERT(stor_driver->RingBufferSize >= (PAGE_SIZE << 1)); */ driver->name = g_blk_driver_name; - memcpy(&driver->dev_type, &g_blk_device_type, sizeof(struct hv_guid)); + memcpy(&driver->class_id, &g_blk_device_type, sizeof(struct hv_guid)); stor_driver->request_ext_size = sizeof(struct storvsc_request_extension); diff --git a/drivers/staging/hv/blkvsc_drv.c b/drivers/staging/hv/blkvsc_drv.c index 36a0adb..194f648 100644 --- a/drivers/staging/hv/blkvsc_drv.c +++ b/drivers/stagi...

...; extern int mdev_register_device(struct device *dev, >>>>>>>> const struct >>>>>>>> mdev_parent_ops *ops); >>>>>>>> >>>>>>>> -It is also required to specify the class_id through:: >>>>>>>> +It is also required to specify the class_id and device >>>>>>>> +specific ops >>>>> through:: >>>>>>>> - extern int mdev_set_class(struct device *dev, u16 id); >>>>>>>>...

...; extern int mdev_register_device(struct device *dev, >>>>>>>> const struct >>>>>>>> mdev_parent_ops *ops); >>>>>>>> >>>>>>>> -It is also required to specify the class_id through:: >>>>>>>> +It is also required to specify the class_id and device >>>>>>>> +specific ops >>>>> through:: >>>>>>>> - extern int mdev_set_class(struct device *dev, u16 id); >>>>>>>>...

First off, thanks -- this is a pretty great library and it feels like I'm learning a lot. I'm getting some more experience with libfuzzer and finding that I have a couple of questions: - How does libfuzzer decide to write a new test file? What distinguishes this one from all the other cases for which new test inputs were not written? Must be something about the path taken through the

...n __sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback>::AllocateBatch (this=this at entry=0x192db80 <__asan::instance>, stat=stat at entry=0x7f76e1bf2c18, c=c at entry=0x7f76e1bd80c8, class_id=class_id at entry=33) #5 0x0000000000448065 in __sanitizer::SizeClassAllocatorLocalCache<__sanitizer::SizeClassAllocator64<105553116266496ul, 4398046511104ul, 0ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __asan::AsanMapUnmapCallback> >::Refill (this=0x7f76e1bd80c8, allocato...

Hi! I have some problems with htb performance. THE SETUP: I have a network with 3 ISP uplinks and 1 local network uplink. There are about 1700 clients. I was shaping their bandwidth with HTB using iptables mangling in a manner: tc class add dev $DEV parent 1:10 classid 1:${CLASS_ID} htb rate \ 16kbit ceil 512kbit burst 2kb prio 2 quantum 1500 tc qdisc add dev $DEV parent 1:${CLASS_ID} handle ${CLASS_ID}: \ sfq perturb 10 tc filter add dev $DEV parent 1: protocol ip prio 17 u32 \ match ip dst "$IP" flowid 1:${CLASS_ID} iptables -A "$CHAIN_NAME&quo...

...uffer_size; @@ -182,16 +182,16 @@ static int blkvsc_drv_init(int (*drv_init)(struct hyperv_driver *drv)) /* Callback to client driver to complete the initialization */ drv_init(&storvsc_drv_obj->base); - drv_ctx->driver.name = storvsc_drv_obj->base.name; - memcpy(&drv_ctx->class_id, &storvsc_drv_obj->base.class_id, + drv->driver.name = storvsc_drv_obj->base.name; + memcpy(&drv->class_id, &storvsc_drv_obj->base.class_id, sizeof(struct hv_guid)); - drv_ctx->probe = blkvsc_probe; - drv_ctx->remove = blkvsc_remove; - drv_ctx->shutdow...

...uffer_size; @@ -182,16 +182,16 @@ static int blkvsc_drv_init(int (*drv_init)(struct hyperv_driver *drv)) /* Callback to client driver to complete the initialization */ drv_init(&storvsc_drv_obj->base); - drv_ctx->driver.name = storvsc_drv_obj->base.name; - memcpy(&drv_ctx->class_id, &storvsc_drv_obj->base.class_id, + drv->driver.name = storvsc_drv_obj->base.name; + memcpy(&drv->class_id, &storvsc_drv_obj->base.class_id, sizeof(struct hv_guid)); - drv_ctx->probe = blkvsc_probe; - drv_ctx->remove = blkvsc_remove; - drv_ctx->shutdow...

...lass id derive from the function > >>> you use to set up the ops. > >>> > >>> void mdev_set_vfio_ops(struct mdev_device *mdev, const struct > >>> vfio_mdev_ops *vfio_ops) { > >>> mdev->device_ops = vfio_ops; > >>> mdev->class_id = MDEV_ID_VFIO; > >>> } > >>> > >>> void mdev_set_virtio_ops(struct mdev_device *mdev, const struct > >>> virtio_mdev_ops *virtio_ops) { > >>> mdev->device_ops = virtio_ops; > >>> mdev->class_id = MDEV_ID_VIRTIO; > &...

...tch method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev driver correctly. > > So this patch adds id_table to mdev_driver and class_id for mdev > device with the match method for mdev bus. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > .../driver-api/vfio-mediated-device.rst | 5 +++++ > drivers/gpu/drm/i915/gvt/kvmgt.c | 1 + > drivers/s390/cio/vfio_ccw_ops.c...

...tch method. But in the future, we may add drivers other than vfio, > the first driver could be virtio-mdev. This means we need to add > device class id support in bus match method to pair the mdev device > and mdev driver correctly. > > So this patch adds id_table to mdev_driver and class_id for mdev > device with the match method for mdev bus. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > .../driver-api/vfio-mediated-device.rst | 5 +++++ > drivers/gpu/drm/i915/gvt/kvmgt.c | 1 + > drivers/s390/cio/vfio_ccw_ops.c...

...atch method. But in the future, we may add drivers other than vfio, > one example is virtio-mdev[1] driver. This means we need to add device > class id support in bus match method to pair the mdev device and mdev > driver correctly. > > So this patch adds id_table to mdev_driver and class_id for mdev > parent with the match method for mdev bus. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > Documentation/driver-api/vfio-mediated-device.rst | 7 +++++-- > drivers/gpu/drm/i915/gvt/kvmgt.c | 2 +- > drivers/s390/cio/vfio_ccw_...

...er::SizeClassMap<17ul, 128ul, 16ul>, __msan::MsanMapUnmapCallback>::AllocateBatch ( this=this at entry=0x212c9a0 <__msan::allocator>, stat=stat at entry=0x212c970 <__msan::fallback_allocator_cache+109392>, c=c at entry=0x2111e20 <__msan::fallback_allocator_cache>, class_id=class_id at entry=6) at ../projects/compiler-rt/lib/msan/../sanitizer_common/sanitizer_allocator.h:357 357 Batch *b = region->free_list.Pop(); (gdb) bt #0 __sanitizer::SizeClassAllocator64<123145302310912ul, 8796093022208ul, 8ul, __sanitizer::SizeClassMap<17ul, 128ul, 16ul>, __msan:...

..._env *env) struct vm_device *device_ctx = device_to_vm_device(device); int ret; - DPRINT_INFO(VMBUS_DRV, "generating uevent - VMBUS_DEVICE_CLASS_GUID={" - "%02x%02x%02x%02x-%02x%02x-%02x%02x-" - "%02x%02x%02x%02x%02x%02x%02x%02x}", - device_ctx->class_id.data[3], device_ctx->class_id.data[2], - device_ctx->class_id.data[1], device_ctx->class_id.data[0], - device_ctx->class_id.data[5], device_ctx->class_id.data[4], - device_ctx->class_id.data[7], device_ctx->class_id.data[6], - device_ctx->class_id.data[8]...

..._env *env) struct vm_device *device_ctx = device_to_vm_device(device); int ret; - DPRINT_INFO(VMBUS_DRV, "generating uevent - VMBUS_DEVICE_CLASS_GUID={" - "%02x%02x%02x%02x-%02x%02x-%02x%02x-" - "%02x%02x%02x%02x%02x%02x%02x%02x}", - device_ctx->class_id.data[3], device_ctx->class_id.data[2], - device_ctx->class_id.data[1], device_ctx->class_id.data[0], - device_ctx->class_id.data[5], device_ctx->class_id.data[4], - device_ctx->class_id.data[7], device_ctx->class_id.data[6], - device_ctx->class_id.data[8]...