search for: class_ids

Cleanup the names of variables that refer to the hyperv_device abstraction. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/blkvsc_drv.c | 12 ++--

Cleanup the names of variables that refer to the hyperv_device abstraction. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/blkvsc_drv.c | 12 ++--

Signed-off-by: Anthony Liguori <aliguori@us.ibm.com> --- hw/9pfs/virtio-9p-device.c | 43 ++++++---- hw/ac97.c | 39 +++++---- hw/acpi_piix4.c | 59 +++++++------ hw/apb_pci.c | 54 ++++++++----- hw/bonito.c | 30 ++++--- hw/cirrus_vga.c | 33 +++++--- hw/dec_pci.c | 57 ++++++++----- hw/e1000.c

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

This patch cleans up (a lot of the) naming issues that various reviewers have noted. It also gets rid of some unnecessary layering in the code. At the lowest level, we have one abstraction for representing a hyperv device (struct hyperv_device) and one abstraction for representing a hyperv driver (struct hyperv_driver). This collapses an unnecessary layering that existed in the code for

This patch cleans up (a lot of the) naming issues that various reviewers have noted. It also gets rid of some unnecessary layering in the code. At the lowest level, we have one abstraction for representing a hyperv device (struct hyperv_device) and one abstraction for representing a hyperv driver (struct hyperv_driver). This collapses an unnecessary layering that existed in the code for

On 2019/10/17 ??12:53, Alex Williamson wrote: > On Wed, 16 Oct 2019 15:31:25 +0000 > Parav Pandit <parav at mellanox.com> wrote: > >>> -----Original Message----- >>> From: Cornelia Huck <cohuck at redhat.com> >>> Sent: Wednesday, October 16, 2019 3:53 AM >>> To: Parav Pandit <parav at mellanox.com> >>> Cc: Alex Williamson

On 2019/10/17 ??12:53, Alex Williamson wrote: > On Wed, 16 Oct 2019 15:31:25 +0000 > Parav Pandit <parav at mellanox.com> wrote: > >>> -----Original Message----- >>> From: Cornelia Huck <cohuck at redhat.com> >>> Sent: Wednesday, October 16, 2019 3:53 AM >>> To: Parav Pandit <parav at mellanox.com> >>> Cc: Alex Williamson

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

On Mon, Aug 10, 2015 at 8:08 PM, Kostya Serebryany <kcc at google.com> wrote: > > > On Mon, Aug 10, 2015 at 5:53 PM, Brian Cain via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> >> First off, thanks -- this is a pretty great library and it feels like I'm >> learning a lot. >> > > Thanks! > > >> I'm getting some

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}

The title says it all. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/blkvsc_drv.c | 46 +++++++++++++++--------------- drivers/staging/hv/netvsc_drv.c | 44 +++++++++++++++--------------- drivers/staging/hv/storvsc_drv.c | 36

The title says it all. Signed-off-by: K. Y. Srinivasan <kys at microsoft.com> Signed-off-by: Haiyang Zhang <haiyangz at microsoft.com> Signed-off-by: Hank Janssen <hjanssen at microsoft.com> --- drivers/staging/hv/blkvsc_drv.c | 46 +++++++++++++++--------------- drivers/staging/hv/netvsc_drv.c | 44 +++++++++++++++--------------- drivers/staging/hv/storvsc_drv.c | 36

On Thu, 17 Oct 2019 16:30:43 +0800 Jason Wang <jasowang at redhat.com> wrote: > On 2019/10/17 ??12:53, Alex Williamson wrote: > >>> Yet another suggestion: have the class 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

On Wed, 23 Oct 2019 21:07:47 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match 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

On Wed, 23 Oct 2019 21:07:47 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match 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

On Mon, 23 Sep 2019 21:03:26 +0800 Jason Wang <jasowang at redhat.com> wrote: > Mdev bus only supports vfio driver right now, so it doesn't implement > match 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

I ran "ninja check-asan" and no errors. But "ninja check-msan" had 117 errors. I took the first FAILED test, which was for eventfd.cc, and executed the command line creating an eventfd executable in a temporary directory and then executed that file using gdb. Finally, used bt to dump the stack. I've emailed llvm-admin at lists.llvm.org to setup an account since

This group of patches removes all DPRINT from hv_vmbus.ko. It is divided in several patches due to size. All DPRINT calls have been removed, and where needed have been replaced with pr_XX native calls. Many debug DPRINT calls have been removed outright. The amount of clutter this driver prints has been significantly reduced. Signed-off-by: Hank Janssen <hjanssen at microsoft.com>

This group of patches removes all DPRINT from hv_vmbus.ko. It is divided in several patches due to size. All DPRINT calls have been removed, and where needed have been replaced with pr_XX native calls. Many debug DPRINT calls have been removed outright. The amount of clutter this driver prints has been significantly reduced. Signed-off-by: Hank Janssen <hjanssen at microsoft.com>