On Wed, Dec 14, 2011 at 11:26:57AM -0700, Eric Blake wrote:
> On 12/14/2011 11:17 AM, Eric Blake wrote:
> > On 12/13/2011 05:38 PM, Daniel P. Berrange wrote:
> >> From: "Daniel P. Berrange"
> >>
> >> The Xen & VBox drivers deal with callbacks & dispatching of
> >> events directly. All the other dr
On Wed, Dec 14, 2011 at 11:17:47AM -0700, Eric Blake wrote:
> On 12/13/2011 05:38 PM, Daniel P. Berrange wrote:
> > From: "Daniel P. Berrange"
> >
> > The Xen & VBox drivers deal with callbacks & dispatching of
> > events directly. All the other drivers use a timer to dispatch
> > events from a c
On 12/13/2011 05:38 PM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> The Xen & VBox drivers deal with callbacks & dispatching of
> events directly. All the other drivers use a timer to dispatch
> events from a clean stack state, rather than deep inside the
> drivers. Convert Xen & V
On 12/14/2011 11:17 AM, Eric Blake wrote:
> On 12/13/2011 05:38 PM, Daniel P. Berrange wrote:
>> From: "Daniel P. Berrange"
>>
>> The Xen & VBox drivers deal with callbacks & dispatching of
>> events directly. All the other drivers use a timer to dispatch
>> events from a clean stack state, rather
On 12/13/2011 05:38 PM, Daniel P. Berrange wrote:
> From: "Daniel P. Berrange"
>
> The Xen & VBox drivers deal with callbacks & dispatching of
> events directly. All the other drivers use a timer to dispatch
> events from a clean stack state, rather than deep inside the
> drivers. Convert Xen & V
From: "Daniel P. Berrange"
The Xen & VBox drivers deal with callbacks & dispatching of
events directly. All the other drivers use a timer to dispatch
events from a clean stack state, rather than deep inside the
drivers. Convert Xen & VBox over to virDomainEventState so
that they match behaviour o
