search for: calbacks

On Fri, Oct 11, 2019 at 04:15:55PM +0800, Jason Wang wrote: > + * @set_vq_cb: Set the interrut calback function for s/interrut/interrupt/ s/calback/callback/ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 488 bytes Desc: not available URL:

Hi, I''m having some strange behavior on callbacks when testing with RSpec2. On my test, when I create a resource using the #create method the callbacks related to #before_create are not called. If I go to the console and I try to type the command Resource.create(client_uri: "http://example.com") all works fine. There are no mocks around, and I can''t understand if this

> From: Jason Wang [mailto:jasowang at redhat.com] > Sent: Tuesday, September 24, 2019 9:54 PM > > This patch implements basic support for mdev driver that supports > virtio transport for kernel virtio driver. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > include/linux/mdev.h | 2 + > include/linux/virtio_mdev.h | 145 >

> From: Jason Wang [mailto:jasowang at redhat.com] > Sent: Tuesday, September 24, 2019 9:54 PM > > This patch implements basic support for mdev driver that supports > virtio transport for kernel virtio driver. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > include/linux/mdev.h | 2 + > include/linux/virtio_mdev.h | 145 >

On Wed, Sep 25, 2019 at 08:45:21PM +0800, Jason Wang wrote: > > On 2019/9/25 ??5:09, Tian, Kevin wrote: > > > From: Jason Wang [mailto:jasowang at redhat.com] > > > Sent: Tuesday, September 24, 2019 9:54 PM > > > > > > This patch implements basic support for mdev driver that supports > > > virtio transport for kernel virtio driver. > >

On Wed, Sep 25, 2019 at 08:45:21PM +0800, Jason Wang wrote: > > On 2019/9/25 ??5:09, Tian, Kevin wrote: > > > From: Jason Wang [mailto:jasowang at redhat.com] > > > Sent: Tuesday, September 24, 2019 9:54 PM > > > > > > This patch implements basic support for mdev driver that supports > > > virtio transport for kernel virtio driver. > >

On Tue, 24 Sep 2019 21:53:30 +0800 Jason Wang <jasowang at redhat.com> wrote: > This patch implements basic support for mdev driver that supports > virtio transport for kernel virtio driver. > > Signed-off-by: Jason Wang <jasowang at redhat.com> > --- > include/linux/mdev.h | 2 + > include/linux/virtio_mdev.h | 145 ++++++++++++++++++++++++++++++++++++

This patch implements basic support for mdev driver that supports virtio transport for kernel virtio driver. Signed-off-by: Jason Wang <jasowang at redhat.com> --- include/linux/mdev.h | 2 + include/linux/virtio_mdev.h | 145 ++++++++++++++++++++++++++++++++++++ 2 files changed, 147 insertions(+) create mode 100644 include/linux/virtio_mdev.h diff --git a/include/linux/mdev.h

This patch implements basic support for mdev driver that supports virtio transport for kernel virtio driver. Signed-off-by: Jason Wang <jasowang at redhat.com> --- include/linux/mdev.h | 1 + include/linux/virtio_mdev.h | 148 ++++++++++++++++++++++++++++++++++++ 2 files changed, 149 insertions(+) create mode 100644 include/linux/virtio_mdev.h diff --git a/include/linux/mdev.h

On 2019/9/25 ??9:21, Michael S. Tsirkin wrote: > On Wed, Sep 25, 2019 at 08:45:21PM +0800, Jason Wang wrote: >> On 2019/9/25 ??5:09, Tian, Kevin wrote: >>>> From: Jason Wang [mailto:jasowang at redhat.com] >>>> Sent: Tuesday, September 24, 2019 9:54 PM >>>> >>>> This patch implements basic support for mdev driver that supports

On 2019/9/25 ??5:09, Tian, Kevin wrote: >> From: Jason Wang [mailto:jasowang at redhat.com] >> Sent: Tuesday, September 24, 2019 9:54 PM >> >> This patch implements basic support for mdev driver that supports >> virtio transport for kernel virtio driver. >> >> Signed-off-by: Jason Wang <jasowang at redhat.com> >> --- >>

> From: Jason Wang > Sent: Wednesday, September 25, 2019 8:45 PM > > > On 2019/9/25 ??5:09, Tian, Kevin wrote: > >> From: Jason Wang [mailto:jasowang at redhat.com] > >> Sent: Tuesday, September 24, 2019 9:54 PM > >> > >> This patch implements basic support for mdev driver that supports > >> virtio transport for kernel virtio driver.

Hello all! I''m having a problem which is driving me insane. It''s probably related to the fact that I''m new to javascript.... :) Here''s the thing, I have a couple of effects which are all being put in the queue. Some of these effects have callbacks; e.g. "afterFinish". But the calback is being made directly instead of after the effect is done. The

Rusty, Anthony, Dor, I need your brain power :-) On smp guests I have seen a problem with virtio (the version in curent Avi's git) which do not occur on single processor guests: kernel BUG at /space/kvm/drivers/virtio/virtio_ring.c:228! illegal operation: 0001 [#1] Modules linked in: ipv6 CPU: 2 Not tainted Process swapper (pid: 0, task: 000000000f83e038, ksp: 000000000f877d70) Krnl

Rusty, Anthony, Dor, I need your brain power :-) On smp guests I have seen a problem with virtio (the version in curent Avi's git) which do not occur on single processor guests: kernel BUG at /space/kvm/drivers/virtio/virtio_ring.c:228! illegal operation: 0001 [#1] Modules linked in: ipv6 CPU: 2 Not tainted Process swapper (pid: 0, task: 000000000f83e038, ksp: 000000000f877d70) Krnl

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hi all: There are hardware that can do virtio datapath offloading while having its own control path. This path tries to implement a mdev based unified API to support using kernel virtio driver to drive those devices. This is done by introducing a new mdev transport for virtio (virtio_mdev) and register itself as a new kind of mdev driver. Then it provides a unified way for kernel virtio driver to

Hello, i have ported the BCP (Bride Control Protocol) patch for pppd 2.4.1 mentioned in http://lists.osdl.org/pipermail/bridge/2004-September/000619.html to pppd 2.4.2. The kernel patch still works without problems with kernel 2.4.30. Perhaps someone else could use this patch ... Here again some documentation i have found about the BCP patch somewere else: When pppd negotiates BCP, it tells