From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: Petri Latvala <petri.latvala@intel.com>, igt-dev@lists.freedesktop.org
Cc: Kunal Joshi <kunal1.joshi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t RFC] lib/igt_chamelium: Use curl timeout for xmlrpc calls
Date: Thu, 24 Sep 2020 16:25:17 +0300 [thread overview]
Message-ID: <81475469-c5de-7c55-cee5-f33a96ba00ef@gmail.com> (raw)
In-Reply-To: <20200924123625.31755-1-petri.latvala@intel.com>
I guess CI isn't going to run this code anywhere for now? The change
look ok to me. Assuming the results will be all green,
Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
On 24.9.2020 15.36, Petri Latvala wrote:
> Use of timeouts everywhere is meaningless if xmlrpc calls are allowed
> to be blocking forever.
>
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Kunal Joshi <kunal1.joshi@intel.com>
> Cc: Arkadiusz Hiler <arek@hiler.eu>
> Cc: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
> ---
> lib/igt_chamelium.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/lib/igt_chamelium.c b/lib/igt_chamelium.c
> index d9fab902..eac893a6 100644
> --- a/lib/igt_chamelium.c
> +++ b/lib/igt_chamelium.c
> @@ -2427,11 +2427,21 @@ void chamelium_deinit_rpc_only(struct chamelium *chamelium)
> struct chamelium *chamelium_init_rpc_only(void)
> {
> struct chamelium *chamelium = malloc(sizeof(struct chamelium));
> + struct xmlrpc_clientparms clientparms;
> + struct xmlrpc_curl_xportparms curlparms;
>
> if (!chamelium)
> return NULL;
>
> memset(chamelium, 0, sizeof(*chamelium));
> + memset(&clientparms, 0, sizeof(clientparms));
> + memset(&curlparms, 0, sizeof(curlparms));
> +
> + curlparms.timeout = _RECEIVER_RESPONSIVE_AFTER_RESET_SECONDS;
> +
> + clientparms.transport = "curl";
> + clientparms.transportparmsP = &curlparms;
> + clientparms.transportparm_size = XMLRPC_CXPSIZE(timeout);
>
> chamelium->drm_fd = -1;
>
> @@ -2439,7 +2449,7 @@ struct chamelium *chamelium_init_rpc_only(void)
> xmlrpc_env_init(&chamelium->env);
> xmlrpc_client_setup_global_const(&chamelium->env);
> xmlrpc_client_create(&chamelium->env, XMLRPC_CLIENT_NO_FLAGS, PACKAGE,
> - PACKAGE_VERSION, NULL, 0, &chamelium->client);
> + PACKAGE_VERSION, &clientparms, 0, &chamelium->client);
> if (chamelium->env.fault_occurred) {
> igt_debug("Failed to init xmlrpc: %s\n",
> chamelium->env.fault_string);
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-09-24 13:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 12:36 [igt-dev] [PATCH i-g-t RFC] lib/igt_chamelium: Use curl timeout for xmlrpc calls Petri Latvala
2020-09-24 13:14 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2020-09-24 13:25 ` Juha-Pekka Heikkila [this message]
2020-09-24 13:36 ` [igt-dev] [PATCH i-g-t RFC] " Petri Latvala
2020-09-24 13:40 ` Juha-Pekka Heikkila
2020-09-24 13:38 ` Juha-Pekka Heikkila
2020-09-24 13:58 ` Petri Latvala
2020-09-24 16:56 ` [igt-dev] ✓ Fi.CI.IGT: success for " Patchwork
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=81475469-c5de-7c55-cee5-f33a96ba00ef@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kunal1.joshi@intel.com \
--cc=petri.latvala@intel.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