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

Build Falco on ppc64le #1225

Closed
wants to merge 2 commits into from
Closed

Conversation

sarveshtamba
Copy link

Signed-off-by: sarveshtamba [email protected]

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

If contributing rules or changes to rules, please make sure to also uncomment one of the following line:

/kind rule-update

/kind rule-create

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area engine

/area rules

/area tests

/area proposals

What this PR does / why we need it: Support to build Falco on ppc64le.

Which issue(s) this PR fixes: Support to build Falco on ppc64le.

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Support to build Falco on ppc64le.

@poiana
Copy link
Contributor

poiana commented May 20, 2020

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@sarveshtamba
Copy link
Author

/assign @fntlnz

Copy link
Contributor

@fntlnz fntlnz left a comment

Choose a reason for hiding this comment

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

Hi! Thanks for getting this in line, having ppc64le sounds exciting to us :)

Looking at this PR, seems that the relevant changes to build on ppc64le are in the CMake files, however the PR contains a lot of unrelated changes in other files that are probably the effect of some messed up rebase.

Please let me know how I can help

@fntlnz
Copy link
Contributor

fntlnz commented Jun 5, 2020

Once this is ready, I think that we can add a test runner for docker using --platform=linux/ppc64le in order to let our test run for ppc too.

sarveshtamba and others added 2 commits June 16, 2020 12:41
Signed-off-by: sarveshtamba <[email protected]>
Signed-off-by: Amit Shirodkar <[email protected]>

revert changes in falco-driver-loader for build on ppc64le
    Signed-off-by: Amit Shirodkar <[email protected]>
INSTALL_COMMAND "")

if("${CMAKE_SYSTEM_PROCESSOR}" STREQUAL "ppc64le")
ExternalProject_Add(
Copy link
Contributor

Choose a reason for hiding this comment

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

I love how you used moonjit here. I think this is worth discussing in the community call to see if we can just use moonjit for everything at this point. I'm adding a discussion point for today.

Copy link
Contributor

Choose a reason for hiding this comment

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

I'm trying to understand why we need to use moonjit here and consolidate if there's a valid reason.

I see that luait is still maintained despite what they say on the moonjit page.

URL "https://github.com/draios/sysdig/archive/${SYSDIG_VERSION}.tar.gz"
# URL_HASH SHA256=bd09607aa8beb863db07e695863f7dc543e2d39e7153005759d26a340ff66fa5
# we need to change the case of the luaL_reg to luaL_Reg since we are using Moonjit
PATCH_COMMAND sed -i "s/luaL_reg/luaL_Reg/g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/chisel.cpp && sed -i "s/luaL_reg/luaL_Reg/g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/lua_parser.cpp && sed -i "s/luaL_getn/lua_objlen /g" ${SYSDIG_SOURCE_DIR}/userspace/libsinsp/lua_parser_api.cpp
Copy link
Contributor

Choose a reason for hiding this comment

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

The only thing that changes here is the patch command.

I think it's better if we just do the if for the patch command and not for the whole external project.

@krisnova
Copy link
Contributor

Next steps:

@sarveshtamba

  • Test moonjit vs raptorjit for the Power PC use case
    • Does it work with both?
    • Does it work with only moonjit?

@fntlnz

  • Test moonjit with CircleCI to see if the tests pass/fail

@shirodkara
Copy link

Next steps:

@sarveshtamba

* Test moonjit vs raptorjit for the Power PC use case
  
  * Does it work with both?
  * Does it work with only moonjit?

@kris-nova @fntlnz I wasn't able to build raptorjit on PowerPC , so on power, falco builds only with moonjit.

@fntlnz
Copy link
Contributor

fntlnz commented Aug 13, 2020

I tested this and works very well. Moonjit is the right option in my opinion.

@leogr leogr added this to the 0.26.0 milestone Aug 25, 2020
@krisnova krisnova modified the milestones: 0.26.0, 0.27.0 Sep 24, 2020
@fntlnz fntlnz mentioned this pull request Oct 13, 2020
4 tasks
@poiana
Copy link
Contributor

poiana commented Nov 25, 2020

@sarveshtamba: PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@fntlnz fntlnz modified the milestones: 0.27.0, 0.28.0 Jan 15, 2021
@leodido
Copy link
Member

leodido commented Apr 9, 2021

/milestone 0.28.1

@poiana poiana modified the milestones: 0.28.0, 0.28.1 Apr 9, 2021
@leogr leogr modified the milestones: 0.28.1, 0.29.0 Apr 26, 2021
@leogr leogr modified the milestones: 0.29.0, 0.30.0 Jun 17, 2021
@fntlnz fntlnz removed their assignment Aug 30, 2021
@leogr leogr modified the milestones: 0.30.0, 0.31.0 Sep 28, 2021
@poiana
Copy link
Contributor

poiana commented Dec 27, 2021

Issues go stale after 90d of inactivity.

Mark the issue as fresh with /remove-lifecycle stale.

Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle stale

@jasondellaluce
Copy link
Contributor

/milestone 0.32.0

@poiana poiana modified the milestones: 0.31.0, 0.32.0 Jan 19, 2022
@poiana
Copy link
Contributor

poiana commented Feb 18, 2022

Stale issues rot after 30d of inactivity.

Mark the issue as fresh with /remove-lifecycle rotten.

Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Provide feedback via https://github.com/falcosecurity/community.

/lifecycle rotten

@poiana
Copy link
Contributor

poiana commented Mar 20, 2022

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

@poiana poiana closed this Mar 20, 2022
@poiana
Copy link
Contributor

poiana commented Mar 20, 2022

@poiana: Closed this PR.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue with /reopen.

Mark the issue as fresh with /remove-lifecycle rotten.

Provide feedback via https://github.com/falcosecurity/community.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants