From: patchwork-bot+netdevbpf@kernel.org
To: Kajol Jain <kjain@linux.ibm.com>
Cc: bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
acme@kernel.org, peterz@infradead.org, songliubraving@fb.com,
daniel@iogearbox.net, andrii@kernel.org, kafai@fb.com,
yhs@fb.com, john.fastabend@gmail.com, davem@davemloft.net,
kpsingh@kernel.org, hawk@kernel.org, kuba@kernel.org,
maddy@linux.ibm.com, atrajeev@linux.vnet.ibm.com,
linux-perf-users@vger.kernel.org, rnsastry@linux.ibm.com,
andrii.nakryiko@gmail.com
Subject: Re: [PATCH v4] bpf: Remove config check to enable bpf support for branch records
Date: Mon, 06 Dec 2021 14:30:08 +0000 [thread overview]
Message-ID: <163880100849.9978.9385858982566868204.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211206073315.77432-1-kjain@linux.ibm.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Mon, 6 Dec 2021 13:03:15 +0530 you wrote:
> Branch data available to bpf programs can be very useful to get
> stack traces out of userspace application.
>
> Commit fff7b64355ea ("bpf: Add bpf_read_branch_records() helper")
> added bpf support to capture branch records in x86. Enable this feature
> for other architectures as well by removing check specific to x86.
>
> [...]
Here is the summary with links:
- [v4] bpf: Remove config check to enable bpf support for branch records
https://git.kernel.org/bpf/bpf-next/c/db52f57211b4
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-12-06 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 7:33 [PATCH v4] bpf: Remove config check to enable bpf support for branch records Kajol Jain
2021-12-06 14:30 ` 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=163880100849.9978.9385858982566868204.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=acme@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=atrajeev@linux.vnet.ibm.com \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=hawk@kernel.org \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kjain@linux.ibm.com \
--cc=kpsingh@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=peterz@infradead.org \
--cc=rnsastry@linux.ibm.com \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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