On Tue, Apr 10, 2018 at 03:15:57PM +0800, Peter Xu wrote:
> On Mon, Apr 09, 2018 at 11:19:43AM +0200, Marc-André Lureau wrote:
> > Hi
> >
> > On Sun, Apr 8, 2018 at 5:02 AM, Peter Xu wrote:
> > > On Wed, Apr 04, 2018 at 03:58:56PM +0200, Marc-André Lureau wrote:
> > >> Hi Peter
> > >>
> > >> On W
On Mon, Apr 09, 2018 at 11:19:43AM +0200, Marc-André Lureau wrote:
> Hi
>
> On Sun, Apr 8, 2018 at 5:02 AM, Peter Xu wrote:
> > On Wed, Apr 04, 2018 at 03:58:56PM +0200, Marc-André Lureau wrote:
> >> Hi Peter
> >>
> >> On Wed, Mar 28, 2018 at 6:02 AM, Peter Xu wrote:
> >> > On Mon, Mar 26, 2018
Hi
On Sun, Apr 8, 2018 at 5:02 AM, Peter Xu wrote:
> On Wed, Apr 04, 2018 at 03:58:56PM +0200, Marc-André Lureau wrote:
>> Hi Peter
>>
>> On Wed, Mar 28, 2018 at 6:02 AM, Peter Xu wrote:
>> > On Mon, Mar 26, 2018 at 11:46:13AM +0200, Marc-André Lureau wrote:
>> >> Hi
>> >>
>> >> On Mon, Mar 26,
On Wed, Apr 04, 2018 at 03:58:56PM +0200, Marc-André Lureau wrote:
> Hi Peter
>
> On Wed, Mar 28, 2018 at 6:02 AM, Peter Xu wrote:
> > On Mon, Mar 26, 2018 at 11:46:13AM +0200, Marc-André Lureau wrote:
> >> Hi
> >>
> >> On Mon, Mar 26, 2018 at 11:08 AM, Peter Xu wrote:
> >> > On Mon, Mar 26, 201
Hi Peter
On Wed, Mar 28, 2018 at 6:02 AM, Peter Xu wrote:
> On Mon, Mar 26, 2018 at 11:46:13AM +0200, Marc-André Lureau wrote:
>> Hi
>>
>> On Mon, Mar 26, 2018 at 11:08 AM, Peter Xu wrote:
>> > On Mon, Mar 26, 2018 at 10:33:27AM +0200, Marc-André Lureau wrote:
>> >> Hi
>> >>
>> >> On Mon, Mar 26
On Mon, Mar 26, 2018 at 11:46:13AM +0200, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 26, 2018 at 11:08 AM, Peter Xu wrote:
> > On Mon, Mar 26, 2018 at 10:33:27AM +0200, Marc-André Lureau wrote:
> >> Hi
> >>
> >> On Mon, Mar 26, 2018 at 10:07 AM, Peter Xu wrote:
> >> > On Fri, Mar 23, 2018 at
Hi
On Mon, Mar 26, 2018 at 11:08 AM, Peter Xu wrote:
> On Mon, Mar 26, 2018 at 10:33:27AM +0200, Marc-André Lureau wrote:
>> Hi
>>
>> On Mon, Mar 26, 2018 at 10:07 AM, Peter Xu wrote:
>> > On Fri, Mar 23, 2018 at 05:18:53PM +0100, Marc-André Lureau wrote:
>> >
>> > [...]
>> >
>> >> > +/*
>> >> >
On Mon, Mar 26, 2018 at 10:33:27AM +0200, Marc-André Lureau wrote:
> Hi
>
> On Mon, Mar 26, 2018 at 10:07 AM, Peter Xu wrote:
> > On Fri, Mar 23, 2018 at 05:18:53PM +0100, Marc-André Lureau wrote:
> >
> > [...]
> >
> >> > +/*
> >> > + * Dispatch one single QMP request. The function will free the
Hi
On Mon, Mar 26, 2018 at 10:07 AM, Peter Xu wrote:
> On Fri, Mar 23, 2018 at 05:18:53PM +0100, Marc-André Lureau wrote:
>
> [...]
>
>> > +/*
>> > + * Dispatch one single QMP request. The function will free the req_obj
>> > + * and objects inside it before return.
>> > + */
>> > +static void mon
On Fri, Mar 23, 2018 at 05:18:53PM +0100, Marc-André Lureau wrote:
[...]
> > +/*
> > + * Dispatch one single QMP request. The function will free the req_obj
> > + * and objects inside it before return.
> > + */
> > +static void monitor_qmp_dispatch_one(QMPRequest *req_obj)
> > {
> > -QObject
On Fri, Mar 9, 2018 at 9:59 AM, Peter Xu wrote:
> Originally QMP goes through these steps:
>
> JSON Parser --> QMP Dispatcher --> Respond
> /|\(2)(3) |
>(1) | \|/ (4)
>+- main thread +
>
> This patch does t
On 03/22/2018 12:00 AM, Peter Xu wrote:
Doesn't OOB insist on having an ID field with the command?
OOB insists on an id field - but there is the situation that SOME errors
occur even before the id field has been encountered (for example, if you
send non-JSON, the parser gets all confused - it
On Thu, Mar 22, 2018 at 12:32:36AM +0100, Marc-André Lureau wrote:
> Hi
>
> On Wed, Mar 21, 2018 at 9:33 PM, Eric Blake wrote:
> > On 03/21/2018 03:09 PM, Dr. David Alan Gilbert wrote:
> >
>
> So the parsing job and the dispatching job is isolated now. It gives us
> a chance in fo
Hi
On Wed, Mar 21, 2018 at 9:33 PM, Eric Blake wrote:
> On 03/21/2018 03:09 PM, Dr. David Alan Gilbert wrote:
>
So the parsing job and the dispatching job is isolated now. It gives us
a chance in following up patches to totally move the parser outside.
The isolation is d
On 03/21/2018 03:09 PM, Dr. David Alan Gilbert wrote:
So the parsing job and the dispatching job is isolated now. It gives us
a chance in following up patches to totally move the parser outside.
The isolation is done using one QEMUBH. Only one dispatcher QEMUBH is
used for all the monitors.
* Marc-André Lureau (marcandre.lur...@gmail.com) wrote:
> Hi
>
> On Fri, Mar 9, 2018 at 9:59 AM, Peter Xu wrote:
> > Originally QMP goes through these steps:
> >
> > JSON Parser --> QMP Dispatcher --> Respond
> > /|\(2)(3) |
> >(1) |
Hi
On Fri, Mar 9, 2018 at 9:59 AM, Peter Xu wrote:
> Originally QMP goes through these steps:
>
> JSON Parser --> QMP Dispatcher --> Respond
> /|\(2)(3) |
>(1) | \|/ (4)
>+- main thread +
>
> This patch do
On 03/09/2018 02:59 AM, Peter Xu wrote:
Originally QMP goes through these steps:
JSON Parser --> QMP Dispatcher --> Respond
/|\(2)(3) |
(1) | \|/ (4)
+- main thread +
This patch does this:
JSON Par
Originally QMP goes through these steps:
JSON Parser --> QMP Dispatcher --> Respond
/|\(2)(3) |
(1) | \|/ (4)
+- main thread +
This patch does this:
JSON Parser QMP Dispatcher --> Respond
/|\ |
19 matches
Mail list logo
