-
Notifications
You must be signed in to change notification settings - Fork 24
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
eBPF turn-off-ening #1667
eBPF turn-off-ening #1667
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The turn-off-ening?! So big a kerfuffle was never seen before!!
26ff782
to
348279a
Compare
e103ce3
to
52e9184
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After a quick look everything sounds good, thanks. The CI pipeline seems to be unhappy though, is it expected?
3112cdd
to
951b4ef
Compare
26e004d
to
11a4ae8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me. A few commentaries, but they could be addressed in follow-up PRs.
if (host.IsRHEL86()) { | ||
CLOG(INFO) << "RHEL 8.6 on ppc64le does not support CORE_BPF, switching to eBPF collection method."; | ||
hconfig->SetCollectionMethod(CollectionMethod::EBPF); | ||
if (k.kernel == 4 && k.major == 18 && k.build_id < 477) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It wont hurt to reference something here to explain why is that.
Description
Make slim and full collector images the same.
Keep legacy driver builds on master, but separate them from the main CI workflow
Checklist
Automated testing
If any of these don't apply, please comment below.
Testing Performed
TODO(replace-me)
Use this space to explain how you tested your PR, or, if you didn't test it, why you did not do so. (Valid reasons include "CI is sufficient" or "No testable changes")
In addition to reviewing your code, reviewers must also review your testing instructions, and make sure they are sufficient.
For more details, ref the Confluence page about this section.