All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next v3 00/11] bpf: propagate read/precision marks over state graph backedges
Date: Wed, 11 Jun 2025 23:10:43 +0000	[thread overview]
Message-ID: <174968344350.3524559.14906547029551737094.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250611200546.4120963-1-eddyz87@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Wed, 11 Jun 2025 13:05:35 -0700 you wrote:
> Current loop_entry-based states comparison logic does not handle the
> following case:
> 
>  .-> A --.  Assume the states are visited in the order A, B, C.
>  |   |   |  Assume that state B reaches a state equivalent to state A.
>  |   v   v  At this point, state C is not processed yet, so state A
>  '-- B   C  has not received any read or precision marks from C.
>             As a result, these marks won't be propagated to B.
> 
> [...]

Here is the summary with links:
  - [bpf-next,v3,01/11] Revert "bpf: use common instruction history across all states"
    (no matching commit)
  - [bpf-next,v3,02/11] bpf: compute SCCs in program control flow graph
    https://git.kernel.org/bpf/bpf-next/c/de270addb499
  - [bpf-next,v3,03/11] bpf: frame_insn_idx() utility function
    https://git.kernel.org/bpf/bpf-next/c/2ca9f34850d6
  - [bpf-next,v3,04/11] bpf: starting_state parameter for __mark_chain_precision()
    https://git.kernel.org/bpf/bpf-next/c/8e1acf430049
  - [bpf-next,v3,05/11] bpf: set 'changed' status if propagate_precision() did any updates
    https://git.kernel.org/bpf/bpf-next/c/a8b96f6950d5
  - [bpf-next,v3,06/11] bpf: set 'changed' status if propagate_liveness() did any updates
    https://git.kernel.org/bpf/bpf-next/c/6b3f95cd99f8
  - [bpf-next,v3,07/11] bpf: move REG_LIVE_DONE check to clean_live_states()
    https://git.kernel.org/bpf/bpf-next/c/d297ccb27e04
  - [bpf-next,v3,08/11] bpf: propagate read/precision marks over state graph backedges
    (no matching commit)
  - [bpf-next,v3,09/11] bpf: remove {update,get}_loop_entry functions
    https://git.kernel.org/bpf/bpf-next/c/49af1fa94a93
  - [bpf-next,v3,10/11] bpf: include backedges in peak_states stat
    https://git.kernel.org/bpf/bpf-next/c/346757cf121d
  - [bpf-next,v3,11/11] selftests/bpf: tests with a loop state missing read/precision mark
    https://git.kernel.org/bpf/bpf-next/c/69afa150dfa2

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      reply	other threads:[~2025-06-11 23:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 20:05 [PATCH bpf-next v3 00/11] bpf: propagate read/precision marks over state graph backedges Eduard Zingerman
2025-06-11 23:10 ` patchwork-bot+netdevbpf [this message]

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=174968344350.3524559.14906547029551737094.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --cc=yonghong.song@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 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.