All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Chanudet <echanude@redhat.com>
To: Albert Esteve <aesteve@redhat.com>
Cc: "Tejun Heo" <tj@kernel.org>,
	"Johannes Weiner" <hannes@cmpxchg.org>,
	"Michal Koutný" <mkoutny@suse.com>,
	"Shuah Khan" <shuah@kernel.org>,
	linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH v5 3/4] selftests: cgroup: Add vmtest-dmem runner script
Date: Thu, 9 Jul 2026 09:45:02 -0400	[thread overview]
Message-ID: <ak-gNsQ8vi7yDJsm@x1nano> (raw)
In-Reply-To: <20260706-kunit_cgroups-v5-3-6c42c8753468@redhat.com>

On Mon, Jul 06, 2026 at 02:06:42PM +0200, Albert Esteve wrote:
> Currently, test_dmem relies on the dmem_selftest helper module
> and a VM setup that may not have the helper preinstalled.
> This makes automated coverage of dmem charge paths harder in
> virtme-based runs.
> 
> Add tools/testing/selftests/cgroup/vmtest-dmem.sh to provide a
> repeatable VM workflow for dmem tests. The script uses vng --exec
> to run the test directly inside a virtme-ng guest with minimal
> setup.
> 
> The script boots a virtme-ng guest, validates dmem controller
> availability, ensures the dmem helper path is present, and runs
> tools/testing/selftests/cgroup/test_dmem. If the helper is not
> available as a loaded module, it attempts module build/load for
> the running guest kernel before executing the test binary.
> 
> The runner also supports interactive shell mode (-s) and reuses
> the verbosity and KTAP exit-code conventions used by other vmtest
> scripts, so it integrates with existing kselftest workflows.
> 
> vmtest-dmem.sh is placed in TEST_FILES rather than TEST_PROGS so
> it is installed alongside the test suite but not invoked
> automatically by run_kselftest.sh. It requires a VM-capable host
> and is intended to be run manually.
> 
> Signed-off-by: Albert Esteve <aesteve@redhat.com>

Reviewed-by: Eric Chanudet <echanude@redhat.com>

-- 
Eric Chanudet


  reply	other threads:[~2026-07-09 13:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-06 12:06 [PATCH v5 0/4] cgroup: dmem: add selftest helper, coverage, and VM runner Albert Esteve
2026-07-06 12:06 ` [PATCH v5 1/4] cgroup: Add dmem_selftest module Albert Esteve
2026-07-09 13:26   ` Eric Chanudet
2026-08-24 18:28   ` Michal Koutný
2026-08-31 11:23     ` Albert Esteve
2026-07-06 12:06 ` [PATCH v5 2/4] selftests: cgroup: Add dmem selftest coverage Albert Esteve
2026-07-09 13:31   ` Eric Chanudet
2026-08-24 18:28   ` Michal Koutný
2026-08-31 12:33     ` Albert Esteve
2026-07-06 12:06 ` [PATCH v5 3/4] selftests: cgroup: Add vmtest-dmem runner script Albert Esteve
2026-07-09 13:45   ` Eric Chanudet [this message]
2026-07-06 12:06 ` [PATCH v5 4/4] selftests: cgroup: handle vmtest-dmem -b to test locally built kernel Albert Esteve
2026-08-24 18:27 ` [PATCH v5 0/4] cgroup: dmem: add selftest helper, coverage, and VM runner Michal Koutný
2026-08-31  8:45   ` Albert Esteve

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=ak-gNsQ8vi7yDJsm@x1nano \
    --to=echanude@redhat.com \
    --cc=aesteve@redhat.com \
    --cc=cgroups@vger.kernel.org \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mkoutny@suse.com \
    --cc=shuah@kernel.org \
    --cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.