From: Petr Vorel <pvorel@suse.cz>
To: sujiaxun <sujiaxun@uniontech.com>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] [v2, 1/2] syscalls/sched_get_priority_max01: Convert to new
Date: Fri, 17 Dec 2021 10:13:43 +0100 [thread overview]
Message-ID: <YbxUx8mz7ejCjp7W@pevik> (raw)
In-Reply-To: <20211217062637.29720-1-sujiaxun@uniontech.com>
Hi sujiaxun,
> +++ b/testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c
> @@ -1,142 +1,43 @@
> +// SPDX-License-Identifier: GPL-2.0-only
> /*
> * Copyright (c) Wipro Technologies Ltd, 2002. All Rights Reserved.
FYI You could add your or LTP copyright. Which one you prefer?
> +/*\
> + * [Description]
> *
> - * DESCRIPTION
> * This is a Phase I test for the sched_get_priority_max(2) system call.
I suggest to change it to
+ * Basic test for the sched_get_priority_max(2) system call.
+ * Obtain different maximum priority scheduling strategies and compare
+ * them with the expected value.
FYI metadata are:
https://github.com/linux-test-project/ltp/releases/download/20210121/metadata.20210121.html
https://github.com/linux-test-project/ltp/releases/download/20210121/metadata.20210121.pdf
You can run make in metadata/ if you're curious what output you do with
[Description]. The output will be in docparse/metadata.html and/or
docparse/metadata.pdf.
> - * It is intended to provide a limited exposure of the system call.
> - *
> - * Setup:
> - * Setup signal handling.
> - * Pause for SIGUSR1 if option specified.
> - *
> - * Test:
> - * Loop if the proper options are given.
> - * Execute system call
> - * Check return code, if system call failed (return=-1)
> - * Log the errno and Issue a FAIL message.
> - * Otherwise, Issue a PASS message.
> - *
> - * Cleanup:
> - * Print errno log and/or timing stats if options given
> - *
> - * USAGE: <for command-line>
> - * sched_get_priority_max01 [-c n] [-e] [-i n] [-I x] [-P x] [-t] [-h] [-f]
> - * [-p]
> - * where, -c n : Run n copies concurrently.
> - * -e : Turn on errno logging.
> - * -h : Show help screen
> - * -f : Turn off functional testing
> - * -i n : Execute test n times.
> - * -I x : Execute test for x seconds.
> - * -p : Pause for SIGUSR1 before starting
> - * -P x : Pause for x seconds between iterations.
> - * -t : Turn on syscall timing.
> - *
> - ****************************************************************/
> + * Obtain different maximum priority scheduling strategies and compare
> + * them with the expected value.
> + */
> #include <errno.h>
> #include <sched.h>
> -#include "test.h"
> -
> -static void setup();
> -static void cleanup();
> -
> -char *TCID = "sched_get_priority_max01";
> +#include "lapi/syscalls.h"
> +#include "tst_test.h"
> -static struct test_case_t {
> +static struct test_case {
> char *desc;
> int policy;
> int retval;
> -} test_cases[] = {
> - {
> - "Test for SCHED_OTHER", SCHED_OTHER, 0}, {
> - "Test for SCHED_FIFO", SCHED_FIFO, 99}, {
> - "Test for SCHED_RR", SCHED_RR, 99}
> +} tcases[] = {
> + {"SCHED_OTHER", SCHED_OTHER, 0},
> + {"SCHED_FIFO", SCHED_FIFO, 99},
> + {"SCHED_RR", SCHED_RR, 99}
> };
FYI if string is the same as constant, you can use macro:
#define POLICY_DESC(x) .desc = #x, .policy = x
static struct test_case {
char *desc;
int policy;
int retval;
} tcases[] = {
{POLICY_DESC(SCHED_OTHER), 0},
{POLICY_DESC(SCHED_FIFO), 99},
{POLICY_DESC(SCHED_RR), 99}
};
Thus if you agree, I'm going to merge with this diff below.
diff --git testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c
index 8dcf7e3ea6..5058153e36 100644
--- testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c
+++ testcases/kernel/syscalls/sched_get_priority_max/sched_get_priority_max01.c
@@ -1,14 +1,16 @@
// SPDX-License-Identifier: GPL-2.0-only
/*
* Copyright (c) Wipro Technologies Ltd, 2002. All Rights Reserved.
+ * Copyright (c) 2021 sujiaxun <sujiaxun@uniontech.com>
*/
/*\
* [Description]
*
- * This is a Phase I test for the sched_get_priority_max(2) system call.
- * Obtain different maximum priority scheduling strategies and compare
- * them with the expected value.
+ * Basic test for the sched_get_priority_max(2) system call.
+ *
+ * Obtain different maximum priority scheduling strategies and compare
+ * them with the expected value.
*/
#include <errno.h>
@@ -16,14 +18,16 @@
#include "lapi/syscalls.h"
#include "tst_test.h"
+#define POLICY_DESC(x) .desc = #x, .policy = x
+
static struct test_case {
char *desc;
int policy;
int retval;
} tcases[] = {
- {"SCHED_OTHER", SCHED_OTHER, 0},
- {"SCHED_FIFO", SCHED_FIFO, 99},
- {"SCHED_RR", SCHED_RR, 99}
+ {POLICY_DESC(SCHED_OTHER), 0},
+ {POLICY_DESC(SCHED_FIFO), 99},
+ {POLICY_DESC(SCHED_RR), 99}
};
static void run_test(unsigned int nr)
@@ -33,11 +37,9 @@ static void run_test(unsigned int nr)
TST_EXP_VAL(tst_syscall(__NR_sched_get_priority_max, tc->policy),
tc->retval, "test for %s", tc->desc);
-
}
static struct tst_test test = {
.tcnt = ARRAY_SIZE(tcases),
.test = run_test,
};
-
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2021-12-17 9:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 6:26 [LTP] [PATCH] [v2, 1/2] syscalls/sched_get_priority_max01: Convert to new sujiaxun
2021-12-17 9:13 ` Petr Vorel [this message]
2021-12-20 19:54 ` Petr Vorel
2021-12-21 1:58 ` sujiaxun
2021-12-21 8: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=YbxUx8mz7ejCjp7W@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--cc=sujiaxun@uniontech.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.