From: Yang Xu <xuyang2018.jy@cn.fujitsu.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy*
Date: Fri, 30 Aug 2019 17:50:49 +0800 [thread overview]
Message-ID: <5D68F179.3000402@cn.fujitsu.com> (raw)
In-Reply-To: <5D688449.3080906@cn.fujitsu.com>
on 2019/08/30 10:04, Xiao Yang wrote:
> On 2019/08/30 4:38, Petr Vorel wrote:
>> Hi,
>>> Since commit 55ee8a5ad ("syscalls: Add set_mempolicy numa tests"),
>>> these cases have been added into runtests/numa, but forget to add it
>>> in runtest/syscalls.
>>> Signed-off-by: Yang Xu<xuyang2018.jy@cn.fujitsu.com>
>> Reviewed-by: Petr Vorel<pvorel@suse.cz>
>>> ---
>>> runtest/syscalls | 5 +++++
>>> 1 file changed, 5 insertions(+)
>>> diff --git a/runtest/syscalls b/runtest/syscalls
>>> index c41ba2a0d..1694ef147 100644
>>> --- a/runtest/syscalls
>>> +++ b/runtest/syscalls
>>> @@ -1177,6 +1177,11 @@ setitimer01 setitimer01
>>> setitimer02 setitimer02
>>> setitimer03 setitimer03
>>> +set_mempolicy01 set_mempolicy01
>>> +set_mempolicy02 set_mempolicy02
>>> +set_mempolicy03 set_mempolicy03
>>> +set_mempolicy04 set_mempolicy04
>>> +
>>> setns01 setns01
>>> setns02 setns02
>> Wouldn't be better to move all NUMA tests out of syscalls?
>> Syscalls are big already.
> Hi Petr,
> all NUMA tests actually verify the functionality of
> syscalls(move_pages(2), set_mempolicy(2), etc)
> so I think that they can be added into syscalls group.
> PS: If someone want to run syscalls from LTP as many as possible, they
> just need to run syscalls group directly.
+1 , set_mempolicy syscall should belong to numa and syscall group.
> Best Regards,
> Xiao Yang
>> BTW I'm looking forward to the new testrunner [1][2], which also solve problem
>> of runtest files :)
Hi Petr
For new testrunner, I think it is a good improvement to save test time by parallel running case.
I am also looking forward to it.
>> Kind regards,
>> Petr
>> [1] https://people.kernel.org/metan/towards-parallel-kernel-test-runs
>> [2] https://github.com/metan-ucw/ltp/tree/master/docparse
>> .
> .
next prev parent reply other threads:[~2019-08-30 9:50 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-28 10:14 [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy* Yang Xu
2019-08-28 10:14 ` [LTP] [PATCH 2/2] runtest/numa: add migrate_pages* Yang Xu
2019-08-29 20:41 ` Petr Vorel
2019-08-30 1:43 ` Xiao Yang
2019-08-30 10:54 ` Petr Vorel
2019-08-30 12:58 ` Petr Vorel
2019-08-28 10:25 ` [LTP] [PATCH 1/2] runtest/syscalls: add set_mempolicy* Xiao Yang
2019-08-29 20:38 ` Petr Vorel
2019-08-30 2:04 ` Xiao Yang
2019-08-30 9:50 ` Yang Xu [this message]
2019-08-30 13:08 ` Petr Vorel
2019-08-30 10:57 ` 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=5D68F179.3000402@cn.fujitsu.com \
--to=xuyang2018.jy@cn.fujitsu.com \
--cc=ltp@lists.linux.it \
/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