From: Fabiano Rosas <farosas@suse.de>
To: Het Gala <het.gala@nutanix.com>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, thuth@redhat.com,
lvivier@redhat.com, pbonzini@redhat.com, peterx@redhat.com
Subject: Re: [PATCH v2 1/3] qtest: migration: Enhance qtest migration functions to support 'channels' argument
Date: Fri, 01 Mar 2024 10:33:41 -0300 [thread overview]
Message-ID: <878r32vzyi.fsf@suse.de> (raw)
In-Reply-To: <584cc08c-7847-401c-aa4a-516427ae1c4d@nutanix.com>
Het Gala <het.gala@nutanix.com> writes:
> On 01/03/24 2:19 pm, Het Gala wrote:
>>
>> On 29/02/24 6:47 am, Fabiano Rosas wrote:
>>> Het Gala <het.gala@nutanix.com> writes:
>>>
>>>> On 27/02/24 1:04 am, Het Gala wrote:
>>>>>
>>>>> On 26/02/24 6:31 pm, Fabiano Rosas wrote:
>>>>>> Het Gala<het.gala@nutanix.com> writes:
>>>>>>
>>>>>>> On 24/02/24 1:42 am, Fabiano Rosas wrote:
>>>>>>> this was the same first approach that I attempted. It won't work
>>>>>>> because
>>>>>>>
>>>>>>> The final 'migrate' QAPI with channels string would look like
>>>>>>>
> [...]
>>> I'm not sure what you tried. This works:
>>>
>>> g_assert(!qdict_haskey(args, "channels"));
>>> if (channels) {
>>> channels_obj = qobject_from_json(channels, errp);
>>> qdict_put_obj(args, "channels", channels_obj);
>>> }
>>
>> Are you sure the above works ?
>
> Sorry, please ignore the below doubt. I understood what silly mistakes I
> was doing. you were right, qobject_from_json() works fine and converts
> string to json object.
>
> Will follow your latest reply and send out the patch really soon. Thank
> you for unblocking me here quickly :)
Just please don't make it all one patch. Each of those steps could be a
separate patch.
next prev parent reply other threads:[~2024-03-01 13:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 15:25 [PATCH v2 0/3] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs Het Gala
2024-02-23 15:25 ` [PATCH v2 1/3] qtest: migration: Enhance qtest migration functions to support 'channels' argument Het Gala
2024-02-23 15:57 ` Het Gala
2024-02-23 20:12 ` Fabiano Rosas
2024-02-24 12:48 ` Het Gala
2024-02-24 15:54 ` Het Gala
2024-02-26 13:01 ` Fabiano Rosas
2024-02-26 19:34 ` Het Gala
2024-02-26 20:24 ` Het Gala
2024-02-29 1:17 ` Fabiano Rosas
2024-02-29 21:51 ` Fabiano Rosas
2024-03-01 8:49 ` Het Gala
2024-03-01 12:47 ` Het Gala
2024-03-01 13:33 ` Fabiano Rosas [this message]
2024-02-23 15:25 ` [PATCH v2 2/3] qtest: migration: Add negative validation tests for 'uri' and 'channels' Het Gala
2024-02-23 15:25 ` [PATCH v2 3/3] qtest: migration: Start migration with 'channels' argument Het Gala
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878r32vzyi.fsf@suse.de \
--to=farosas@suse.de \
--cc=het.gala@nutanix.com \
--cc=lvivier@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).