From: Andrew Morton <akpm@linux-foundation.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Shanker Donthineni <sdonthineni@nvidia.com>,
Kuan-Ying Lee <Kuan-Ying.Lee@mediatek.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Subject: Re: No care given to GDB scripts..
Date: Wed, 29 Nov 2023 17:02:54 -0800 [thread overview]
Message-ID: <20231129170254.e7ca4c866b521c291e88395e@linux-foundation.org> (raw)
In-Reply-To: <25a5e810-1e57-4a59-ae82-cb2c7d28a116@gmail.com>
On Wed, 29 Nov 2023 16:23:55 -0800 Florian Fainelli <f.fainelli@gmail.com> wrote:
> > Is there any way of scripting the scripts so we can have some sort of
> > automated testing down under tools/testing/selftests/?
>
> That might be a bit difficult to do as this would mean that we can self
> debug and introspect using gdb the live kernel. Testing using QEMU is
> definitively doable however. Of course, I just found another script that
> broke (device.py)!
Oh. That sounds quite the exercise in the context of tools/selftests.
One can of course just fire up gdb against the vmlinux elf file and
play around, but I assume this won't permit a useful amount of the
scripts to be exercised.
Suppose someone has set up qemu or whatever and has attached gdb to it.
Could we provide that person with a script or a canned set of commands
which exercise the gdb scripts to a useful extent? So rather than
attempting automated testing under the seltests umbrella, we provide
less skilled individuals with the means to easily and quickly check for
regressions. I'd expect that such a toolset would be particularly
helpful for regression testing the scripts across all the supported
architectures?
next prev parent reply other threads:[~2023-11-30 1:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 22:48 Florian Fainelli
2023-11-29 23:06 ` Andrew Morton
2023-11-30 0:23 ` Florian Fainelli
2023-11-30 1:02 ` Andrew Morton [this message]
2023-11-30 4:49 ` Florian Fainelli
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=20231129170254.e7ca4c866b521c291e88395e@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Kuan-Ying.Lee@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=f.fainelli@gmail.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sdonthineni@nvidia.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
all inboxes | Powered by JetHome®