Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

biostacks.bt: use tracepoints instead of kprobes #2891

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

makelinux
Copy link
Contributor

@makelinux makelinux commented Dec 26, 2023

because since v5.17-rc1~116^2~83 function blk_account_io_start became static and can't be used as a kprobe.
But block_io_start tracepoint is available only since v6.5-rc1114^2181.
The original kprobe version is retained as biostacks-kp.bt

@chenhengqi
Copy link
Contributor

The problem is that the block_io_start tracepoint is relative new and not widely available.

Copy link
Member

@danobi danobi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems like there's already prior art in having a -kp variant of the tool.
So probably fine to continue.

CI failure looks legit (and is what @chenhengqi mentioned). I think
ci.yml needs to be updated to ignore testing that tool.

Copy link
Contributor

@viktormalik viktormalik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer moving tools/biostacks-kp.bt to tools/old/biostacks.bt which is the way we currently maintain multiple versions of tools for different kernels.

That would also allow to easily resolve the CI issue by adding the tool into TOOLS_TEST_OLDVERSION for relevant CI jobs.

because since v5.17-rc1~116^2~83 function blk_account_io_start
became static and can't be used as a kprobe.

But block_io_start tracepoint is available only since v6.5-rc1~114^2~181.

The original kprobe version is retained as old/biostacks.bt
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants