search for: vhost_vdpa_stop_irq_offloading

...son is we may want to fallback to software datapath for some >>>> reason (e.g software assisted live migration). In this case we need >>>> intercept device write to used ring so we can not offloading >>>> virtqueue interrupt in this case. >>> so add a VHOST_VDPA_STOP_IRQ_OFFLOADING? Then do we need a >>> VHOST_VDPA_START_IRQ_OFFLOADING, then let userspace fully control >>> this? Or any better approaches? >> >> >> Probably not, it's as simple as allocating another eventfd (but not >> irqfd), and pass it to vhost-vdpa. Then the...

...son is we may want to fallback to software datapath for some >>>> reason (e.g software assisted live migration). In this case we need >>>> intercept device write to used ring so we can not offloading >>>> virtqueue interrupt in this case. >>> so add a VHOST_VDPA_STOP_IRQ_OFFLOADING? Then do we need a >>> VHOST_VDPA_START_IRQ_OFFLOADING, then let userspace fully control >>> this? Or any better approaches? >> >> >> Probably not, it's as simple as allocating another eventfd (but not >> irqfd), and pass it to vhost-vdpa. Then the...

...ck to software datapath > > > > > for some reason (e.g software assisted live migration). In > > > > > this case we need intercept device write to used ring so we > > > > > can not offloading virtqueue interrupt in this case. > > > > so add a VHOST_VDPA_STOP_IRQ_OFFLOADING? Then do we need a > > > > VHOST_VDPA_START_IRQ_OFFLOADING, then let userspace fully > > > > control this? Or any better approaches? > > > > > > > > > Probably not, it's as simple as allocating another eventfd (but not > > > irqfd),...