search for: eventfds

Hi. I have Centos 7 (updated) running as my host, and I?m using Qemu and KVM, version 2.0.0 and 2.6.0. I have a Trendnet TU-S9 USB serial dongle attached to the host, which uses the Prolific 2303 chipset. I blacklisted the pl2303 driver so the host doesn?t grab the device, and want to expose it to the guest. On the client, I see 2 USB hubs (3.0 and 2.0), and I see 2 USB endpoints (even though

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

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > >

On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: > On Thu, 2015-09-17 at 16:31 -0700, Ming Lin wrote: > > On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > > > Hi Ming & Co, > > > > > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > >

...sidering hypercalls for e.g. virtio, is open for discussion. I also had to extend kvm in a minor way, making all ioeventfd options accessible through the API. This actually needs less code than checking that users DTRT. Patches 1-5 are useful in themselves. Patches 5 and 6 add support for PV MMIO eventfds and add the test for it, tested against a kernel patch I'll send shortly. They can be applied separately when we are sure the kernel interface is going to be there. Michael S. Tsirkin (6): kvm: remove unused APIs kvm: support any size for pio eventfd kvm: support non datamatch ioeventfd...

...sidering hypercalls for e.g. virtio, is open for discussion. I also had to extend kvm in a minor way, making all ioeventfd options accessible through the API. This actually needs less code than checking that users DTRT. Patches 1-5 are useful in themselves. Patches 5 and 6 add support for PV MMIO eventfds and add the test for it, tested against a kernel patch I'll send shortly. They can be applied separately when we are sure the kernel interface is going to be there. Michael S. Tsirkin (6): kvm: remove unused APIs kvm: support any size for pio eventfd kvm: support non datamatch ioeventfd...

.../* pvmmio only looks at the address, so always a hit */ + return true; + + if (len != p->length) /* address-range must be precise for a hit */ return false; @@ -671,9 +680,11 @@ ioeventfd_check_collision(struct kvm *kvm, struct _ioeventfd *p) list_for_each_entry(_p, &kvm->ioeventfds, list) if (_p->bus_idx == p->bus_idx && - _p->addr == p->addr && _p->length == p->length && - (_p->wildcard || p->wildcard || - _p->datamatch == p->datamatch)) + _p->addr == p->addr && + (_p->pvmmio...

.../* pvmmio only looks at the address, so always a hit */ + return true; + + if (len != p->length) /* address-range must be precise for a hit */ return false; @@ -671,9 +680,11 @@ ioeventfd_check_collision(struct kvm *kvm, struct _ioeventfd *p) list_for_each_entry(_p, &kvm->ioeventfds, list) if (_p->bus_idx == p->bus_idx && - _p->addr == p->addr && _p->length == p->length && - (_p->wildcard || p->wildcard || - _p->datamatch == p->datamatch)) + _p->addr == p->addr && + (_p->pvmmio...

On 2020/7/16 ??12:13, Zhu, Lingshan wrote: > > > On 7/16/2020 12:02 PM, Jason Wang wrote: >> >> On 2020/7/16 ??11:59, Zhu, Lingshan wrote: >>> >>> On 7/16/2020 10:59 AM, Jason Wang wrote: >>>> >>>> On 2020/7/16 ??9:39, Zhu, Lingshan wrote: >>>>> >>>>> >>>>> On 7/15/2020 9:43 PM, Jason Wang

On 2020/7/16 ??12:13, Zhu, Lingshan wrote: > > > On 7/16/2020 12:02 PM, Jason Wang wrote: >> >> On 2020/7/16 ??11:59, Zhu, Lingshan wrote: >>> >>> On 7/16/2020 10:59 AM, Jason Wang wrote: >>>> >>>> On 2020/7/16 ??9:39, Zhu, Lingshan wrote: >>>>> >>>>> >>>>> On 7/15/2020 9:43 PM, Jason Wang

On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > Hi Ming & Co, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > > > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: > > > > These 2 patches added virtio-nvme to kernel and qemu, > > >

On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > Hi Ming & Co, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > > > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: > > > > These 2 patches added virtio-nvme to kernel and qemu, > > >

On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > From: Jason Wang <jasowang at redhat.com> > Date: Wed, 1 Apr 2020 22:17:27 +0800 > Subject: [PATCH] vhost: let CONFIG_VHOST to be selected by drivers > > The defconfig on some archs enable vhost_net or vhost_vsock by > default. So

On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > From: Jason Wang <jasowang at redhat.com> > Date: Wed, 1 Apr 2020 22:17:27 +0800 > Subject: [PATCH] vhost: let CONFIG_VHOST to be selected by drivers > > The defconfig on some archs enable vhost_net or vhost_vsock by > default. So

On Thu, Apr 02, 2020 at 11:22:57AM +0800, Jason Wang wrote: > > On 2020/4/2 ??12:08, Michael S. Tsirkin wrote: > > On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > > > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > > > From: Jason Wang <jasowang at redhat.com> > > > Date: Wed, 1 Apr 2020 22:17:27 +0800 >

On Thu, Apr 02, 2020 at 11:22:57AM +0800, Jason Wang wrote: > > On 2020/4/2 ??12:08, Michael S. Tsirkin wrote: > > On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > > > >From 9b3a5d23b8bf6b0a11e65e688335d782f8e6aa5c Mon Sep 17 00:00:00 2001 > > > From: Jason Wang <jasowang at redhat.com> > > > Date: Wed, 1 Apr 2020 22:17:27 +0800 >

? 2023/2/28 17:41, Xie Yongji ??: > Add eventfd for the vdpa callback so that user > can signal it directly instead of running the > callback. It will be used for vhost-vdpa case. > > Signed-off-by: Xie Yongji <xieyongji at bytedance.com> > --- > drivers/vhost/vdpa.c | 2 ++ > drivers/virtio/virtio_vdpa.c | 1 + > include/linux/vdpa.h | 3 +++

On Thu, Apr 02, 2020 at 10:23:59PM +0800, Jason Wang wrote: > > On 2020/4/2 ??10:03, Michael S. Tsirkin wrote: > > On Thu, Apr 02, 2020 at 11:22:57AM +0800, Jason Wang wrote: > > > On 2020/4/2 ??12:08, Michael S. Tsirkin wrote: > > > > On Wed, Apr 01, 2020 at 10:29:32PM +0800, Jason Wang wrote: > > > > > >From

I've "successfully" built 3.9.0 release but when I run "ninja check-all" I got 208 Unexpected failures: Expected Passes : 33997 Expected Failures : 198 Unsupported Tests : 685 Unexpected Failures: 208 Below is the log I captured running "time ninja check-all | tee ninja-check-all.txt" https://drive.google.com/open?id=0B-KTY7zi7eZHU2hGYTRtd01QZjA

Hi, This is the first attempt to add a new qemu nvme backend using in-kernel nvme target. Most code are ported from qemu-nvme and also borrow code from Hannes Reinecke's rts-megasas. It's similar as vhost-scsi, but doesn't use virtio. The advantage is guest can run unmodified NVMe driver. So guest can be any OS that has a NVMe driver. The goal is to get as good performance as