Gitiles
Code Review Sign In
gerrit.openbmc.org / mdmillerii / openbmc / e918757fd9f23aeb15905b0cd188c52ab1017793
commite918757fd9f23aeb15905b0cd188c52ab1017793[log] [tgz]
authorJoel Stanley <joel@jms.id.au>Wed Sep 12 09:19:29 2018 +0930
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Sep 12 09:52:58 2018 -0400
tree130d352a7d8ff68a1c4f46c67f4fee5c0d7310e9
parent3f236b77a7fd52176b731d279172a45c5ad9e8bd [diff]
linux-aspeed: Disable CONFIG_BPF_STREAM_PARSER

This is a feature used to attach BPF programs to network stockets. It is
used by systemd to restrict the IP addresses that processes can access
at a per-cgroup level. The upstream commit message calls this 'per-unit
IP access lists and accounting'.

It requires CONFIG_CGROUP_BPF and CONFIG_BPF_STREAM_PARSER. We did not
have CONFIG_CGROUP_BPF turned on, which caused the noisy messages.

Until OpenBMC adds configuration to take advantage of this feature,
disable CONFIG_BPF_STREAM_PARSER which allows systemd to correctly
detect that it cannot use BPF filters.

(From meta-aspeed rev: 53e41a55f5b3890fcec07c900a1894d57d6d499c)

Change-Id: I16a3c07025b7e954afa2dfdc7982fa70119c60dd
Signed-off-by: Joel Stanley <joel@jms.id.au>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 130d352a7d8ff68a1c4f46c67f4fee5c0d7310e9
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-ibm/
  5. meta-ingrasys/
  6. meta-intel/
  7. meta-inventec/
  8. meta-mellanox/
  9. meta-nuvoton/
  10. meta-openembedded/
  11. meta-openpower/
  12. meta-phosphor/
  13. meta-portwell/
  14. meta-qualcomm/
  15. meta-quanta/
  16. meta-raspberrypi/
  17. meta-security/
  18. meta-x86/
  19. poky/
  20. bitbake ⇨ poky/bitbake/
  21. LICENSE ⇨ poky/LICENSE
  22. meta ⇨ poky/meta
  23. meta-poky ⇨ poky/meta-poky/
  24. oe-init-build-env ⇨ poky/oe-init-build-env
  25. scripts ⇨ poky/scripts/
  26. .gitignore
  27. .gitreview
  28. .templateconf
  29. MAINTAINERS
  30. openbmc-env
  31. README.md
  32. setup
README.md

OpenBMC

Build Status

The OpenBMC project can be described as a Linux distribution for embedded devices that have a BMC; typically, but not limited to, things like servers, top of rack switches or RAID appliances. The OpenBMC stack uses technologies such as Yocto, OpenEmbedded, systemd, and D-Bus to allow easy customization for your server platform.

Setting up your OpenBMC project

1) Prerequisite

  • Ubuntu 14.04
sudo apt-get install -y git build-essential libsdl1.2-dev texinfo gawk chrpath diffstat
  • Fedora 23
sudo dnf install -y git patch diffstat texinfo chrpath SDL-devel bitbake
sudo dnf groupinstall "C Development Tools and Libraries"

2) Download the source

git clone git@github.com:openbmc/openbmc.git
cd openbmc

3) Target your hardware

Any build requires an environment variable known as TEMPLATECONF to be set to a hardware target. You can see all of the known targets with find meta-* -name local.conf.sample. Choose the hardware target and then move to the next step. Additional examples can be found in the OpenBMC Cheatsheet

MachineTEMPLATECONF
Palmettometa-ibm/meta-palmetto/conf
Zaiusmeta-ingrasys/meta-zaius/conf
Witherspoonmeta-ibm/meta-witherspoon/conf

As an example target Palmetto

export TEMPLATECONF=meta-ibm/meta-palmetto/conf

4) Build

. openbmc-env
bitbake obmc-phosphor-image

Additional details can be found in the docs repository.

Build Validation and Testing

Commits submitted by members of the OpenBMC GitHub community are compiled and tested via our Jenkins server. Commits are run through two levels of testing. At the repository level the makefile make check directive is run. At the system level, the commit is built into a firmware image and run with an arm-softmmu QEMU model against a barrage of CI tests.

Commits submitted by non-members do not automatically proceed through CI testing. After visual inspection of the commit, a CI run can be manually performed by the reviewer.

Automated testing against the QEMU model along with supported systems are performed. The OpenBMC project uses the Robot Framework for all automation. Our complete test repository can be found here.

Submitting Patches

Support of additional hardware and software packages is always welcome. Please follow the contributing guidelines when making a submission. It is expected that contributions contain test cases.

Bug Reporting

Issues are managed on GitHub. It is recommended you search through the issues before opening a new one.

Features of OpenBMC

Feature List

  • REST Management
  • IPMI
  • SSH based SOL
  • Power and Cooling Management
  • Event Logs
  • Zeroconf discoverable
  • Sensors
  • Inventory
  • LED Management
  • Host Watchdog
  • Simulation
  • Code Update Support for multiple BMC/BIOS images
  • POWER On Chip Controller (OCC) Support

Features In Progress

  • Full IPMI 2.0 Compliance with DCMI
  • Verified Boot
  • HTML5 Java Script Web User Interface
  • BMC RAS

Features Requested but need help

  • OpenCompute Redfish Compliance
  • OpenBMC performance monitoring
  • cgroup user management and policies
  • Remote KVM
  • Remote USB
  • OpenStack Ironic Integration
  • QEMU enhancements

Finding out more

Dive deeper in to OpenBMC by opening the docs repository.

Contact