qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Het Gala <het.gala@nutanix.com>
To: Fabiano Rosas <farosas@suse.de>, qemu-devel@nongnu.org
Cc: marcandre.lureau@redhat.com, thuth@redhat.com,
	lvivier@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v4 3/8] Replace migrate_get_connect_uri inplace of migrate_get_socket_address
Date: Tue, 12 Mar 2024 02:27:44 +0530	[thread overview]
Message-ID: <3193a63f-c127-4673-a6fa-4872eeadd735@nutanix.com> (raw)
In-Reply-To: <878r2omr0f.fsf@suse.de>

[-- Attachment #1: Type: text/plain, Size: 1962 bytes --]


On 12/03/24 2:21 am, Fabiano Rosas wrote:
> Het Gala<het.gala@nutanix.com>  writes:
>
>> On 11/03/24 11:49 pm, Fabiano Rosas wrote:
>>> Het Gala<het.gala@nutanix.com>   writes:
>>>
>>>>    bool migrate_watch_for_events(QTestState *who, const char *name,
>>>> @@ -130,7 +140,7 @@ void migrate_qmp(QTestState *who, QTestState *to, const char *uri,
>>>>    
>>>>        g_assert(!qdict_haskey(args, "uri"));
>>>>        if (!uri) {
>>>> -        connect_uri = migrate_get_socket_address(to, "socket-address");
>>>> +        connect_uri = migrate_get_connect_uri(to, "socket-address");
>>> What's the point of the "socket-address" argument here? Seems a bit
>>> nonsensical to me to call: migrate_get_socket_address(..., "socket-address").
>>>
>>> What about we just suppress this throughout the stack and directly call:
>>>
>>>       object = qdict_get(rsp, "socket-address");
>> Fabiano, I didn't get clearly understand your point here. From what I
>> understand,
>> you want to call just
>> 1. migrate_get_connect_uri(to) and migrate_get_connect_qdict(to)
> Yes.
Ack
>> 2. delete migrate_get_socket_address(..., "socket-address") altogether
> No, just the string argument, not the whole function:
>
> static char *migrate_get_socket_address(QTestState *who) <----
> {
>      QDict *rsp;
>      char *result;
>      SocketAddressList *addrs;
>      Visitor *iv = NULL;
>      QObject *object;
>
>      rsp = migrate_query(who);
>      object = qdict_get(rsp, "socket-address"); <-----
>      ...
> }
>
> If the thing is called migrate_get_SOCKET_ADDRESS(), it's obvious that
> the "socket-address" is the parameter we want. We even call
> SocketAddress_to_str, so there's no point in having that argument
> there. We will never call the function with something else in
> 'parameter'.
Ahh, okay. I got your point, and yes, it makes sense. Will just call
migrate_get_socket_address(to) and let the qdict_get() call 
"socket-address" internally.

Regards,

Het Gala

[-- Attachment #2: Type: text/html, Size: 3599 bytes --]

  reply	other threads:[~2024-03-11 20:58 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-08 20:59 [PATCH v4 0/8] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs Het Gala
2024-03-08 20:59 ` [PATCH v4 1/8] Add 'to' object into migrate_qmp() Het Gala
2024-03-08 20:59 ` [PATCH v4 2/8] Replace connect_uri and move migrate_get_socket_address inside migrate_qmp Het Gala
2024-03-11 18:16   ` Fabiano Rosas
2024-03-11 20:13     ` Het Gala
2024-03-08 20:59 ` [PATCH v4 3/8] Replace migrate_get_connect_uri inplace of migrate_get_socket_address Het Gala
2024-03-11 18:19   ` Fabiano Rosas
2024-03-11 20:33     ` Het Gala
2024-03-11 20:51       ` Fabiano Rosas
2024-03-11 20:57         ` Het Gala [this message]
2024-03-08 20:59 ` [PATCH v4 4/8] Add channels parameter in migrate_qmp_fail Het Gala
2024-03-11 18:20   ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 5/8] Add migrate_set_ports into migrate_qmp to update migration port value Het Gala
2024-03-11 18:42   ` Fabiano Rosas
2024-03-11 21:15     ` Het Gala
2024-03-08 20:59 ` [PATCH v4 6/8] Add channels parameter in migrate_qmp Het Gala
2024-03-11 18:44   ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 7/8] Add multifd_tcp_plain test using list of channels instead of uri Het Gala
2024-03-11 19:58   ` Fabiano Rosas
2024-03-08 20:59 ` [PATCH v4 8/8] Add negative tests to validate migration QAPIs Het Gala
2024-03-09  7:41 ` [PATCH v4 0/8] qtest: migration: Add tests for introducing 'channels' argument in migrate QAPIs Het Gala
2024-03-11 21:25   ` Peter Xu
2024-03-11 21:31     ` Het Gala
2024-03-11 21:38       ` Peter Xu
2024-03-11 21:59         ` 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=3193a63f-c127-4673-a6fa-4872eeadd735@nutanix.com \
    --to=het.gala@nutanix.com \
    --cc=farosas@suse.de \
    --cc=lvivier@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@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).