From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>
Cc: Richard Palethorpe <rpalethorpe@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v1] clone3: Add clone3's clone_args cgroup
Date: Thu, 23 Mar 2023 10:26:55 +0100 [thread overview]
Message-ID: <20230323092655.GF405493@pevik> (raw)
In-Reply-To: <20230226003526.8733-1-wegao@suse.com>
Hi Wei,
Do you plan to use this somewhere? Otherwise I don't see the point to just
add it.
Kind regards,
Petr
> Signed-off-by: Wei Gao <wegao@suse.com>
> ---
> include/lapi/sched.h | 3 +++
> include/tst_clone.h | 1 +
> lib/tst_clone.c | 1 +
> 3 files changed, 5 insertions(+)
> diff --git a/include/lapi/sched.h b/include/lapi/sched.h
> index 1065665d1..3ad16d136 100644
> --- a/include/lapi/sched.h
> +++ b/include/lapi/sched.h
> @@ -54,6 +54,9 @@ struct clone_args {
> uint64_t __attribute__((aligned(8))) stack;
> uint64_t __attribute__((aligned(8))) stack_size;
> uint64_t __attribute__((aligned(8))) tls;
> + uint64_t __attribute__((aligned(8))) set_tid;
> + uint64_t __attribute__((aligned(8))) set_tid_size;
> + uint64_t __attribute__((aligned(8))) cgroup;
> };
> static inline int clone3(struct clone_args *args, size_t size)
> diff --git a/include/tst_clone.h b/include/tst_clone.h
> index 9ffdc68d1..7b278dfa7 100644
> --- a/include/tst_clone.h
> +++ b/include/tst_clone.h
> @@ -11,6 +11,7 @@
> struct tst_clone_args {
> uint64_t flags;
> uint64_t exit_signal;
> + uint64_t cgroup;
> };
> /* clone3 with fallbacks to clone when possible. Be aware that it
> diff --git a/lib/tst_clone.c b/lib/tst_clone.c
> index ecc84408c..2aa00beb1 100644
> --- a/lib/tst_clone.c
> +++ b/lib/tst_clone.c
> @@ -15,6 +15,7 @@ pid_t tst_clone(const struct tst_clone_args *tst_args)
> struct clone_args args = {
> .flags = tst_args->flags,
> .exit_signal = tst_args->exit_signal,
> + .cgroup = tst_args->cgroup,
> };
> int flags;
> pid_t pid = -1;
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2023-03-23 9:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-26 0:35 [LTP] [PATCH v1] clone3: Add clone3's clone_args cgroup Wei Gao via ltp
2023-03-23 9:26 ` Petr Vorel [this message]
2023-03-23 12:17 ` Wei Gao via ltp
2023-03-24 6:32 ` Petr Vorel
2023-03-24 6:54 ` Wei Gao via ltp
2023-03-24 8:26 ` Petr Vorel
2023-04-21 12:38 ` [LTP] [PATCH v2] " Wei Gao via ltp
2023-04-21 13:29 ` Cyril Hrubis
2023-04-22 1:42 ` [LTP] [PATCH v3] " Wei Gao via ltp
2023-04-26 13:44 ` Cyril Hrubis
2023-05-09 0:31 ` [LTP] [PATCH v4] " Wei Gao via ltp
2023-05-17 9:28 ` Petr Vorel
2023-05-17 12:08 ` [LTP] [PATCH v5] " Wei Gao via ltp
2023-08-25 10:36 ` Richard Palethorpe
2023-08-29 23:26 ` Wei Gao via ltp
2023-08-30 8:02 ` Richard Palethorpe
2023-08-29 23:18 ` [LTP] [PATCH v6] " Wei Gao via ltp
2023-08-31 6:47 ` [LTP] [PATCH v7] " Wei Gao via ltp
2023-08-31 9:19 ` Richard Palethorpe
2023-09-01 10:19 ` Petr Vorel
2023-09-01 10:22 ` Petr Vorel
2023-09-02 5:05 ` Wei Gao via ltp
2024-04-04 20:42 ` Petr Vorel
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=20230323092655.GF405493@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=rpalethorpe@suse.com \
--cc=wegao@suse.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