From: Richard Palethorpe <rpalethorpe@suse.de>
To: Petr Vorel <pvorel@suse.cz>
Cc: kernel-team@android.com, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v7 1/1] mmapstress01: refactor to tst_test framework
Date: Mon, 14 Nov 2022 09:44:56 +0000 [thread overview]
Message-ID: <875yfhvotj.fsf@suse.de> (raw)
In-Reply-To: <Y25+IZDZ9/rvSH+E@pevik>
Hello,
Petr Vorel <pvorel@suse.cz> writes:
> Hi Edward, Richard, all,
>
>> Hello,
>
>> Richard Palethorpe <rpalethorpe@suse.de> writes:
>
>> > Hello,
>
>> > Edward Liaw via ltp <ltp@lists.linux.it> writes:
>
>> >> Use ltp framework and apply make check corrections. Reorder functions
>> >> and variables. Use safe macros.
>> >> Drop leavefile option.
>> >> Build tests with FILE_OFFSET_BITS=64 instead of doing LARGE_FILE checks
>> >> to switch between 32 and 64 bit types and syscalls.
>> >> Define fsize bounds by file offset bits.
>> >> Move sighandler to setup and remove sig blocks.
>> >> Add option to specify pattern.
>> >> Set default nprocs to ncpus with min of 1 and max of 20.
>
>> >> Signed-off-by: Edward Liaw <edliaw@google.com>
>
>> > Reviewed-by: Richard Palethorpe <rpalethorpe@suse.com>
>
>> > Will merge this today if the CI is happy and nobody comments.
>
>> Merged, thanks!
>
> Thanks for your work! FYI 2 tiny problems sneaked in, see below.
>
> runtest/mm contained -t 0.20 option, which caused failure. Fixed in:
> https://github.com/linux-test-project/ltp/commit/36321277a294c0467219f650fd76aa1a8d310c1d
>
>> >> ---
>> >> testcases/kernel/mem/mmapstress/Makefile | 2 +
> ...
>> >> +static struct tst_option options[] = {
>> >> + {"d", &debug, "Enable debug output"},
>> >> + {"f:", &opt_filesize, "Initial filesize (default 4096)"},
>> >> + {"m", &do_sync, "Do random msync/fsyncs as well"},
>> >> + {"o", &do_offset, "Randomize the offset of file to map"},
>> >> + {"p:", &opt_nprocs,
>> >> + "Number of mapping children to create (default 1 < ncpus < 20)"},
>> >> + {"P:", &opt_pattern,
>> >> + "Use a fixed pattern (default random)"},
>> >> + {"r", &randloops,
>> >> + "Randomize number of pages map children check (random % 500), "
>> >> + "otherwise each child checks 500 pages"},
>> >> + {"S:", &opt_sparseoffset,
>> >> + "When non-zero, causes the sparse area to be left before the data, "
>> >> + "so that the actual initial filesize is sparseoffset + filesize "
>> >> + "(default 0)"},
>> >> + {},
>> >> +};
> Using options as non-inline leads to our docparse documentation
> having the name of the variable (options) i this case instead of listing
> options. Fixed in
> https://github.com/linux-test-project/ltp/commit/72de038ff54496c5ced6ddc2d76713376aababb1
>
> @Metan: I wonder if this can be fixed in docparser.
> @Richie: If not, it would be nice to have check for it (I'll add issue with
> "check" label).
Yeah, the checker could also produce the metadata. I'm not sure I want
to start down that path though. This is an AST level operation which
Sparse is pretty bad at.
I think both tools have serious issues. Perhaps using tree-sitter or
even Arocc would be far more profitable.
>
> @Edward FYI to build doc:
> cd metadata && make # open ../docparse/metadata.html
>
> Here is stable version:
> http://linux-test-project.github.io/metadata/metadata.stable.html
>
> I plan to write hook to put version for master branch, being updated after each
> commit.
>
> Kind regards,
> Petr
--
Thank you,
Richard.
--
Mailing list info: https://lists.linux.it/listinfo/ltp
next prev parent reply other threads:[~2022-11-14 10:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 21:58 [LTP] [PATCH v7 0/1] mmapstress01: refactor to ltp framework Edward Liaw via ltp
2022-10-27 21:58 ` [LTP] [PATCH v7 1/1] mmapstress01: refactor to tst_test framework Edward Liaw via ltp
2022-11-08 10:49 ` Richard Palethorpe
2022-11-08 11:19 ` Richard Palethorpe
2022-11-11 16:53 ` Petr Vorel
2022-11-11 17:07 ` Petr Vorel
2022-11-14 10:00 ` Richard Palethorpe
2022-11-14 9:44 ` Richard Palethorpe [this message]
2022-11-14 10:50 ` Cyril Hrubis
2022-11-14 14:17 ` 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=875yfhvotj.fsf@suse.de \
--to=rpalethorpe@suse.de \
--cc=kernel-team@android.com \
--cc=ltp@lists.linux.it \
--cc=pvorel@suse.cz \
/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