BPF List
 help / color / mirror / Atom feed
From: Manu Bretelle <chantr4@gmail.com>
To: lsf-pc@lists.linux-foundation.org
Cc: bpf@vger.kernel.org
Subject: [LSF/MM/BPF TOPIC] development/troubleshooting workflows for BPF
Date: Wed, 28 Feb 2024 20:24:12 -0800	[thread overview]
Message-ID: <ZeAG7EYG/JwFEYg2@surya> (raw)

Hi all,

Building upon the learnings and knowledge of BPF CI [0], I would like to present
ways that can help developpers make their workflow easier, and improve their
development and troubleshooting velocity.

While there is probably thousand different ways to get to the same result, and
people may have their personal preferences, I will be presenting an approach
which is close to what is used by the CI.
Feedback and suggestions would be greatly appreciated.


Some topics I have in mind:

- Reproducing CI error in CI environemt. Until recently, it was challenging to
  Re-using artifacts produced by the CI, how to reproduce
  the issue within the CI environment, and poke at the system.
- Building and running tests for a foreign architecture. Method to cross-compile
  and run tests for a foreign architecture.
- local development workflow. While most people may already have their own setup,
  here I am proposing a workflow which is simple and allow for fast iteration.
- bisecting issues: leveraging bpf selftests and vm testing, how to leverage
  `git bisect run` to "quickly", or at least with less friction, identify a bad
  commit.

Thanks,

Manu

[0]: https://github.com/kernel-patches/bpf

             reply	other threads:[~2024-02-29  4:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-29  4:24 Manu Bretelle [this message]
2024-03-14 10:15 ` [LSF/MM/BPF TOPIC] development/troubleshooting workflows for BPF Muhammad Usama Anjum

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=ZeAG7EYG/JwFEYg2@surya \
    --to=chantr4@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=lsf-pc@lists.linux-foundation.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