From: Petr Vorel <pvorel@suse.cz>
To: Wei Gao <wegao@suse.com>, ltp@lists.linux.it
Subject: Re: [LTP] [PATCH v4 2/2] swapping01.c: Reporting /proc/meminfo during test
Date: Mon, 18 Dec 2023 14:47:55 +0100 [thread overview]
Message-ID: <20231218134755.GA209176@pevik> (raw)
In-Reply-To: <20231218133404.GB199735@pevik>
> Hi Wei,
> > Get clear overview memory status during test is good for debug, such as
> > get report before the test and also at the moment of the failure.
> > Signed-off-by: Wei Gao <wegao@suse.com>
> > ---
> > testcases/kernel/mem/swapping/swapping01.c | 4 ++++
> > 1 file changed, 4 insertions(+)
> > diff --git a/testcases/kernel/mem/swapping/swapping01.c b/testcases/kernel/mem/swapping/swapping01.c
> > index fc225e4a6..025f44363 100644
> > --- a/testcases/kernel/mem/swapping/swapping01.c
> > +++ b/testcases/kernel/mem/swapping/swapping01.c
> > @@ -83,7 +83,9 @@ static void test_swapping(void)
> > switch (pid = SAFE_FORK()) {
> > case 0:
> > + TST_PRINT_MEMINFO();
> > do_alloc(0);
> > + TST_PRINT_MEMINFO();
> Developer asked you to print /proc/meminfo "before the test starts and at the
> moment of the failure" Wouldn't be just this second TST_PRINT_MEMINFO() enough?
OK, I merged this. Thank you.
Kind regards,
Petr
> Kind regards,
> Petr
> > do_alloc(1);
> > exit(0);
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2023-12-18 13:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-10 9:43 [LTP] [PATCH v1] swapping01.c: Reporting /proc/meminfo before test and at the moment of the failure Wei Gao via ltp
2023-12-12 17:29 ` Petr Vorel
2023-12-14 6:33 ` [LTP] [PATCH v2 0/2] Add tst_print_meminfo function in swapping01 Wei Gao via ltp
2023-12-14 6:33 ` [LTP] [PATCH v2 1/2] tst_memutils.c: Add tst_print_meminfo function Wei Gao via ltp
2023-12-14 6:33 ` [LTP] [PATCH v2 2/2] swapping01.c: Reporting /proc/meminfo during test Wei Gao via ltp
2023-12-14 7:13 ` [LTP] [PATCH v3 0/2] Add tst_print_meminfo function into swapping01 Wei Gao via ltp
2023-12-14 7:13 ` [LTP] [PATCH v3 1/2] tst_memutils.c: Add tst_print_meminfo function Wei Gao via ltp
2023-12-15 18:57 ` Petr Vorel
2023-12-18 3:41 ` Li Wang
2023-12-18 3:51 ` Li Wang
2023-12-18 4:39 ` Petr Vorel
2023-12-18 4:30 ` Petr Vorel
2023-12-18 7:20 ` Li Wang
2023-12-14 7:13 ` [LTP] [PATCH v3 2/2] swapping01.c: Reporting /proc/meminfo during test Wei Gao via ltp
2023-12-18 7:37 ` Li Wang
2023-12-18 12:22 ` [LTP] [PATCH v4 0/2] Add tst_print_meminfo function into swapping01 Wei Gao via ltp
2023-12-18 12:22 ` [LTP] [PATCH v4 1/2] tst_memutils.c: Add tst_print_meminfo function Wei Gao via ltp
2023-12-18 13:24 ` Petr Vorel
2023-12-18 12:22 ` [LTP] [PATCH v4 2/2] swapping01.c: Reporting /proc/meminfo during test Wei Gao via ltp
2023-12-18 13:34 ` Petr Vorel
2023-12-18 13:47 ` Petr Vorel [this message]
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=20231218134755.GA209176@pevik \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
--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