From: Jason Wessel <jason.wessel@windriver.com>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: <kgdb-bugreport@lists.sourceforge.net>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<linux-kernel@vger.kernel.org>, <patches@linaro.org>
Subject: Re: [PATCH] misc: kgdbts: Display progress of asynchronous tests
Date: Thu, 14 Dec 2017 09:20:56 -0600 [thread overview]
Message-ID: <31570645-24de-3625-7a43-eb6d41214478@windriver.com> (raw)
In-Reply-To: <20171212121036.26468-1-daniel.thompson@linaro.org>
On 12/12/2017 06:10 AM, Daniel Thompson wrote:
> kgdbts includes a couple of different "thrashing" style tests that
> may have long runtimes (especially on simulated platforms) and which
> run asynchronously. This is uncomfortable for interactive use and
> makes setting timeouts tricky for automatic use.
Do you know which test was specifically causing a problem? It might not be documented anywhere but I had usually started a user space process which quickly created and deleted user space processes in order to make the kgdbts tests complete quickly.
I don't really see any issue with emitting a printk to indicate progress as it is debug only and test specific. As you know printk's change timing. If I had a dime for each time I had seen a problem go away when I started adding printk's I'd have at least a 50 cents. :-)
Jason.
PS. Added this to kgdb-next and I'll put in a request to get kgdb-next added back to the linux-next builder.
>
> Fix by providing a optional means to show progress during these tests.
> Selecting 100 is somewhat arbitrary but it matches the step used on
> the synchronous tests, is large enough to keep the call to printk
> from invalidating the testing and is human enough to "feel about
> right".
>
> Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
> ---
> drivers/misc/kgdbts.c | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/misc/kgdbts.c b/drivers/misc/kgdbts.c
> index 24108bfad889..6193270e7b3d 100644
> --- a/drivers/misc/kgdbts.c
> +++ b/drivers/misc/kgdbts.c
> @@ -400,10 +400,14 @@ static void skip_back_repeat_test(char *arg)
> int go_back = simple_strtol(arg, NULL, 10);
>
> repeat_test--;
> - if (repeat_test <= 0)
> + if (repeat_test <= 0) {
> ts.idx++;
> - else
> + } else {
> + if (repeat_test % 100 == 0)
> + v1printk("kgdbts:RUN ... %d remaining\n", repeat_test);
> +
> ts.idx -= go_back;
> + }
> fill_get_buf(ts.tst[ts.idx].get);
> }
>
> --
> 2.14.3
>
next prev parent reply other threads:[~2017-12-14 15:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 12:10 Daniel Thompson
2017-12-14 15:20 ` Jason Wessel [this message]
2017-12-14 16:11 ` Daniel Thompson
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=31570645-24de-3625-7a43-eb6d41214478@windriver.com \
--to=jason.wessel@windriver.com \
--cc=arnd@arndb.de \
--cc=daniel.thompson@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@linaro.org \
/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
all inboxes | Powered by JetHome®