Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2018-03-28 Thread Prerna
Hi Marc, Currently the block job handling needs to be sorted out before events can assume independent handling from RPC contexts. Sorry, I have not been able to revisit this in the past 2 months, but this is something I would very much like to fix. I will try looking up the exact dependency of the

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2018-03-21 Thread Marc Hartmayer
On Tue, Oct 24, 2017 at 07:34 PM +0200, Prerna Saxena wrote: > As noted in > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > libvirt-QEMU driver handles all async events from the main loop. > Each event handling needs the per-VM lock to make forward

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-12-05 Thread Prerna
I spent a while trying to work through this proposal, here are a few points which need more thought: On Wed, Nov 8, 2017 at 7:22 PM, Daniel P. Berrange wrote: > On Mon, Nov 06, 2017 at 06:43:12AM +0100, Prerna wrote: > > Thanks for your reply Daniel. I am still on vacation

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-11-14 Thread Prerna
On Wed, Nov 15, 2017 at 12:07 AM, Marc Hartmayer < mhart...@linux.vnet.ibm.com> wrote: > On Tue, Oct 24, 2017 at 07:34 PM +0200, Prerna Saxena < > saxenap@gmail.com> wrote: > > As noted in > > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > > libvirt-QEMU driver handles

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-11-14 Thread Marc Hartmayer
On Tue, Oct 24, 2017 at 07:34 PM +0200, Prerna Saxena wrote: > As noted in > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > libvirt-QEMU driver handles all async events from the main loop. > Each event handling needs the per-VM lock to make forward

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-11-08 Thread Daniel P. Berrange
On Mon, Nov 06, 2017 at 06:43:12AM +0100, Prerna wrote: > Thanks for your reply Daniel. I am still on vacation all of this week so > have not been able to respond. > Few questions inline: > > On Thu, Oct 26, 2017 at 2:43 PM, Daniel P. Berrange > wrote: > > > On Tue, Oct 24,

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-11-05 Thread Prerna
Thanks for your reply Daniel. I am still on vacation all of this week so have not been able to respond. Few questions inline: On Thu, Oct 26, 2017 at 2:43 PM, Daniel P. Berrange wrote: > On Tue, Oct 24, 2017 at 10:34:53AM -0700, Prerna Saxena wrote: > > > > As noted in > >

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-10-26 Thread Daniel P. Berrange
On Tue, Oct 24, 2017 at 10:34:53AM -0700, Prerna Saxena wrote: > > As noted in > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > libvirt-QEMU driver handles all async events from the main loop. > Each event handling needs the per-VM lock to make forward progress. In > the

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-10-26 Thread Peter Krempa
On Thu, Oct 26, 2017 at 10:21:17 +0530, Prerna wrote: > On Wed, Oct 25, 2017 at 4:12 PM, Jiri Denemark wrote: > > On Tue, Oct 24, 2017 at 10:34:53 -0700, Prerna Saxena wrote: [...] > > > Patch Series status: > > > Strictly RFC only. No compilation issues. I have not had a

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-10-25 Thread Prerna
On Wed, Oct 25, 2017 at 4:12 PM, Jiri Denemark wrote: > On Tue, Oct 24, 2017 at 10:34:53 -0700, Prerna Saxena wrote: > > > > As noted in > > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > > libvirt-QEMU driver handles all async events from the main

Re: [libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-10-25 Thread Jiri Denemark
On Tue, Oct 24, 2017 at 10:34:53 -0700, Prerna Saxena wrote: > > As noted in > https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html > libvirt-QEMU driver handles all async events from the main loop. > Each event handling needs the per-VM lock to make forward progress. In > the case

[libvirt] [[RFC] 0/8] Implement async QEMU event handling in libvirtd.

2017-10-24 Thread Prerna Saxena
As noted in https://www.redhat.com/archives/libvir-list/2017-May/msg00016.html libvirt-QEMU driver handles all async events from the main loop. Each event handling needs the per-VM lock to make forward progress. In the case where an async event is received for the same VM which has an RPC