public inbox for kdevops@lists.linux.dev
 help / color / mirror / Atom feed
From: Luis Chamberlain <mcgrof@kernel.org>
To: Chuck Lever <cel@kernel.org>, Daniel Gomez <da.gomez@kruces.com>,
	kdevops@lists.linux.dev
Cc: Luis Chamberlain <mcgrof@kernel.org>
Subject: [PATCH 0/8] linux-ab enhancements + monitor support
Date: Mon, 11 Aug 2025 15:42:59 -0700	[thread overview]
Message-ID: <20250811224307.2218478-1-mcgrof@kernel.org> (raw)

These are a collection of practical enhancements developed as I tested
Linux AB testing with parallel writeback developmental patches to help
do analysis on impact on memory management. The last patch adds the
ability to do experimental (non upstream) monitoring of different types.
We could obviously later add monitoring for existing upstream knobs but
in this case we want to track folio migration success rates and so are
using a currently out of tree knob.

Luis Chamberlain (8):
  bootlinux: use different kernel for A/B testing by default
  bootlinux: add support for custom refs on dev kernels on the CLI
  bootlinux: add git ref verification before cloning
  bootlinux: add git dirty check before cloning
  bootlinux: add intelligent git repository detection and management
  bootlinux: enhance A/B testing and repository management
  fstests: add make target for running tests on all hosts
  monitoring: integrate monitoring collection into fstests workflow

 Kconfig                                       |   4 +
 README.md                                     |   1 +
 defconfigs/xfs_reflink_lbs                    |   1 +
 kconfigs/Kconfig.kdevops                      |   8 +-
 playbooks/roles/bootlinux/tasks/build/9p.yml  | 193 +++++++++++++++++-
 .../roles/bootlinux/tasks/build/builder.yml   | 165 +++++++++++++++
 .../roles/bootlinux/tasks/build/targets.yml   | 166 +++++++++++++++
 playbooks/roles/fstests/tasks/main.yml        |  14 ++
 scripts/ensure_newlines.py                    |   3 +-
 workflows/fstests/Makefile                    |  10 +
 workflows/linux/Kconfig                       |  18 +-
 11 files changed, 571 insertions(+), 12 deletions(-)

-- 
2.47.2


             reply	other threads:[~2025-08-11 22:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-11 22:42 Luis Chamberlain [this message]
2025-08-11 22:43 ` [PATCH 1/8] bootlinux: use different kernel for A/B testing by default Luis Chamberlain
2025-08-11 22:43 ` [PATCH 2/8] bootlinux: add support for custom refs on dev kernels on the CLI Luis Chamberlain
2025-08-11 22:43 ` [PATCH 3/8] bootlinux: add git ref verification before cloning Luis Chamberlain
2025-08-11 22:43 ` [PATCH 4/8] bootlinux: add git dirty check " Luis Chamberlain
2025-08-11 22:43 ` [PATCH 5/8] bootlinux: add intelligent git repository detection and management Luis Chamberlain
2025-08-11 22:43 ` [PATCH 6/8] bootlinux: enhance A/B testing and repository management Luis Chamberlain
2025-08-11 22:43 ` [PATCH 7/8] fstests: add make target for running tests on all hosts Luis Chamberlain
2025-08-11 22:43 ` [PATCH 8/8] monitoring: integrate monitoring collection into fstests workflow Luis Chamberlain
2025-08-11 22:46   ` Luis Chamberlain
2025-08-12  0:49     ` Luis Chamberlain
2025-08-14  0:59       ` Luis Chamberlain

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=20250811224307.2218478-1-mcgrof@kernel.org \
    --to=mcgrof@kernel.org \
    --cc=cel@kernel.org \
    --cc=da.gomez@kruces.com \
    --cc=kdevops@lists.linux.dev \
    /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