Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openbmc / 469e377d6e39fd8f82e221a3e9c555808fcc926b
commit469e377d6e39fd8f82e221a3e9c555808fcc926b[log] [tgz]
authorAndrew Geissler <geissonator@yahoo.com>Tue Sep 25 16:12:14 2018 -0500
committerBrad Bishop <bradleyb@fuzziesquirrel.com>Wed Sep 26 15:43:49 2018 -0400
tree8487dd22a1c05d6997c943666aac202279880a59
parent862e477bfd365df3919b84929561259c51480e34 [diff]
Remove mapper nice priority

This is a revert of eff3d02a180ef60102f1f25d765b2ddf72831be3
A direct revert is not possible due to our subtree refactoring

Prioritizing one application over another seems to cause more
problems then it solves. In this case it appears that mapper
can starve other process's in which mapper depends on responding.
So that dependent process times out, restarts, which then causes
the whole cycle to start over.

Hoping this is the fix to openbmc/openbmc#3369 but will require
some testing.

Tested: George was kind enough to run this through some BMC reboot
tests and a regression bucket. openbmc/openbmc#3369 did not recreate
but not willing to declare success yet with that bug.

(From meta-ibm rev: 9effdef83644fff90a2bcb6f4d6fb97ac28fcb28)

Change-Id: I9af8ab369966a69c09d807d888b0bf5a0f0b3e07
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
2 files changed
tree: 8487dd22a1c05d6997c943666aac202279880a59
  1. meta-arm/
  2. meta-aspeed/
  3. meta-evb/
  4. meta-facebook/
  5. meta-google/
  6. meta-ibm/
  7. meta-ingrasys/
  8. meta-intel/
  9. meta-inventec/
  10. meta-mellanox/
  11. meta-nuvoton/
  12. meta-openembedded/
  13. meta-openpower/
  14. meta-phosphor/
  15. meta-portwell/
  16. meta-qualcomm/
  17. meta-quanta/
  18. meta-raspberrypi/
  19. meta-security/
  20. meta-x86/
  21. poky/
  22. bitbake ⇨ poky/bitbake/
  23. LICENSE ⇨ poky/LICENSE
  24. meta ⇨ poky/meta
  25. meta-poky ⇨ poky/meta-poky/
  26. oe-init-build-env ⇨ poky/oe-init-build-env
  27. scripts ⇨ poky/scripts/
  28. .gitignore
  29. .gitreview
  30. .templateconf
  31. MAINTAINERS
  32. openbmc-env
  33. README.md
  34. 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