[Skiboot] [RFC PATCH 08/23] doc/release-notes/skiboot-5.1.x: rename .txt to .rst
Stewart Smith
stewart at linux.vnet.ibm.com
Wed Jul 27 17:43:09 AEST 2016
Signed-off-by: Stewart Smith <stewart at linux.vnet.ibm.com>
---
doc/release-notes/skiboot-5.1.0.rst | 261 +++++++++++++++++++++++++++++++++++
doc/release-notes/skiboot-5.1.0.txt | 261 -----------------------------------
doc/release-notes/skiboot-5.1.1.rst | 41 ++++++
doc/release-notes/skiboot-5.1.1.txt | 41 ------
doc/release-notes/skiboot-5.1.10.rst | 34 +++++
doc/release-notes/skiboot-5.1.10.txt | 34 -----
doc/release-notes/skiboot-5.1.11.rst | 16 +++
doc/release-notes/skiboot-5.1.11.txt | 16 ---
doc/release-notes/skiboot-5.1.12.rst | 44 ++++++
doc/release-notes/skiboot-5.1.12.txt | 44 ------
doc/release-notes/skiboot-5.1.13.rst | 43 ++++++
doc/release-notes/skiboot-5.1.13.txt | 43 ------
doc/release-notes/skiboot-5.1.14.rst | 20 +++
doc/release-notes/skiboot-5.1.14.txt | 20 ---
doc/release-notes/skiboot-5.1.15.rst | 9 ++
doc/release-notes/skiboot-5.1.15.txt | 9 --
doc/release-notes/skiboot-5.1.16.rst | 52 +++++++
doc/release-notes/skiboot-5.1.16.txt | 52 -------
doc/release-notes/skiboot-5.1.17.rst | 19 +++
doc/release-notes/skiboot-5.1.17.txt | 19 ---
doc/release-notes/skiboot-5.1.2.rst | 125 +++++++++++++++++
doc/release-notes/skiboot-5.1.2.txt | 125 -----------------
doc/release-notes/skiboot-5.1.3.rst | 92 ++++++++++++
doc/release-notes/skiboot-5.1.3.txt | 92 ------------
doc/release-notes/skiboot-5.1.4.rst | 32 +++++
doc/release-notes/skiboot-5.1.4.txt | 32 -----
doc/release-notes/skiboot-5.1.5.rst | 39 ++++++
doc/release-notes/skiboot-5.1.5.txt | 39 ------
doc/release-notes/skiboot-5.1.6.rst | 31 +++++
doc/release-notes/skiboot-5.1.6.txt | 31 -----
doc/release-notes/skiboot-5.1.7.rst | 29 ++++
doc/release-notes/skiboot-5.1.7.txt | 29 ----
doc/release-notes/skiboot-5.1.8.rst | 20 +++
doc/release-notes/skiboot-5.1.8.txt | 20 ---
doc/release-notes/skiboot-5.1.9.rst | 16 +++
doc/release-notes/skiboot-5.1.9.txt | 16 ---
36 files changed, 923 insertions(+), 923 deletions(-)
create mode 100644 doc/release-notes/skiboot-5.1.0.rst
delete mode 100644 doc/release-notes/skiboot-5.1.0.txt
create mode 100644 doc/release-notes/skiboot-5.1.1.rst
delete mode 100644 doc/release-notes/skiboot-5.1.1.txt
create mode 100644 doc/release-notes/skiboot-5.1.10.rst
delete mode 100644 doc/release-notes/skiboot-5.1.10.txt
create mode 100644 doc/release-notes/skiboot-5.1.11.rst
delete mode 100644 doc/release-notes/skiboot-5.1.11.txt
create mode 100644 doc/release-notes/skiboot-5.1.12.rst
delete mode 100644 doc/release-notes/skiboot-5.1.12.txt
create mode 100644 doc/release-notes/skiboot-5.1.13.rst
delete mode 100644 doc/release-notes/skiboot-5.1.13.txt
create mode 100644 doc/release-notes/skiboot-5.1.14.rst
delete mode 100644 doc/release-notes/skiboot-5.1.14.txt
create mode 100644 doc/release-notes/skiboot-5.1.15.rst
delete mode 100644 doc/release-notes/skiboot-5.1.15.txt
create mode 100644 doc/release-notes/skiboot-5.1.16.rst
delete mode 100644 doc/release-notes/skiboot-5.1.16.txt
create mode 100644 doc/release-notes/skiboot-5.1.17.rst
delete mode 100644 doc/release-notes/skiboot-5.1.17.txt
create mode 100644 doc/release-notes/skiboot-5.1.2.rst
delete mode 100644 doc/release-notes/skiboot-5.1.2.txt
create mode 100644 doc/release-notes/skiboot-5.1.3.rst
delete mode 100644 doc/release-notes/skiboot-5.1.3.txt
create mode 100644 doc/release-notes/skiboot-5.1.4.rst
delete mode 100644 doc/release-notes/skiboot-5.1.4.txt
create mode 100644 doc/release-notes/skiboot-5.1.5.rst
delete mode 100644 doc/release-notes/skiboot-5.1.5.txt
create mode 100644 doc/release-notes/skiboot-5.1.6.rst
delete mode 100644 doc/release-notes/skiboot-5.1.6.txt
create mode 100644 doc/release-notes/skiboot-5.1.7.rst
delete mode 100644 doc/release-notes/skiboot-5.1.7.txt
create mode 100644 doc/release-notes/skiboot-5.1.8.rst
delete mode 100644 doc/release-notes/skiboot-5.1.8.txt
create mode 100644 doc/release-notes/skiboot-5.1.9.rst
delete mode 100644 doc/release-notes/skiboot-5.1.9.txt
diff --git a/doc/release-notes/skiboot-5.1.0.rst b/doc/release-notes/skiboot-5.1.0.rst
new file mode 100644
index 0000000..8558378
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.0.rst
@@ -0,0 +1,261 @@
+skiboot-5.1.0
+-------------
+
+skiboot-5.1.0 was released on August 17th, 2015.
+
+skiboot-5.1.0 is the first stable release of 5.1.0 following two beta releases.
+This new stable release replaces skiboot-5.0 as the current stable skiboot
+release (5.0 was released April 14th 2015).
+
+Skiboot 5.1.0 contains all fixes from skiboot-5.0 stable branch up to
+skiboot-5.0.5 and everything from 5.1.0-beta1 and 5.1.0-beta2.
+
+Over skiboot-5.1.0-beta2, we have the following changes:
+- opal_prd now supports multiple socket systems
+- fix compiler warnings in gard and libflash
+
+Below are the changes introduced in previous skiboot-5.1.0 releases over
+the previous stable release, skiboot-5.0:
+
+New features:
+- Add Naples chip (CPU, PHB, LPC serial interrupts) support
+- Added qemu platform
+- improvements to FSI error handling
+- improvements in chip TOD failover (some only on FSP systems)
+- Set Relative Priority Register (RPR) to recommended value
+ - this affects thread priority in SMT modes
+- greatly reduce memory consumption by CPU stacks for non-present CPUs
+ - Previously we would reserve enough memory for max PIR for each CPU
+ type.
+ - This fix frees up 77MB of RAM on a typical P8 system.
+- increased OPAL API documentation
+- Asynchronous preloading of resources from FSP/flash
+ - improves boot time on some systems
+- Basic Garrison platform support
+- Add Mambo platform (P8 Functional Simulator, systemsim)
+ - includes fake NVRAM, RTC
+- Support building with GCOV, increasing memory for skiboot binary to 2MB
+ - includes boot code coverage testing
+- Increased skiboot HEAP size.
+ - We are not aware of any system where you would run out, but on large
+ systems it was getting closer than we liked.
+- add boot_tests.sh for helping automate boot testing on FSP and BMC machines
+- Versioning of pflash and gard utilities to help Linux (or other OS)
+ distributions with packaging.
+- OCC throttle status messages to host
+- CAPP timebase sync ("ibm,capp-timebase-sync" in DT to indicate CAPP timebase
+ was synced by OPAL)
+- opal-api: Add OPAL call to handle abnormal reboots.
+ OPAL_CEC_REBOOT2
+ Currently it will support two reboot types (0). normal reboot, that
+ will behave similar to that of opal_cec_reboot() call, and
+ (1). platform error reboot.
+
+ Long term, this is designed to replace OPAL_CEC_REBOOT.
+
+New features for FSP based machines:
+- in-band IPMI support
+- ethernet adaptor location codes
+- add DIMM frequency information to device tree
+- improvements in FSP error log code paths
+- fix some boot time memory leaks
+ - harmless to end user
+
+New features for AMI BMC based machines:
+- PCIe power workaround for K80
+- Added support for Macronix 128Mbit flash chips
+- Initial PRD support for Firestone platform
+- improved reliability when BMC reboots
+
+The following bugs have been fixed:
+- Increase PHB3 timeout for electrical links coming up to 2 seconds.
+ - fixes issues with some Mellanox cards
+- Hang in opal_reinit_cpus() that could prevent kdump from functioning
+- PHB3: fix crash in phb3_init
+- PHB3: fix crash with fenced PHB in phb3_init_hw()
+- Fix bugs in hw/bt.c (interface for IPMI on BMC machines) that could possibly
+ lead to a crash (dereferencing invalid address, deadlock)
+- ipmi/sel: fix use-after-free
+- Bug fixes in EEH handling
+ - opal_pci_next_error() cleared OPAL_EVENT_PCI_ERROR unconditionally, possibly
+ leading to missed errors.
+- external/opal-prd: Only map each PRD range once
+ - could eventually lead to failing to map PRD ranges
+- On skiboot crash, don't try to print symbol when we didn't find one
+ - makes backtrace prettier
+- On skiboot crash, dump hssr0 and hsrr1 registers correctly.
+- Better support old and biarch compilers
+ - test "new" compiler flags before using them
+ - Specify -mabi=elfv1 if supported (which means it's needed)
+- fix boot-coverage-report makefile target
+- ipmi: Fix the opal_ipmi_recv() call to handle the error path
+ - Could make kernel a sad panda when in continues with other IPMI commands
+- IPMI: truncate SELs at 2kb
+ - it's the limit of the astbmc. We think.
+- IPMI/SEL/PEL:
+ - As per PEL spec, we should log events with severity >= 0x22 and "service
+ action flag" is "on". But in our case, all logs OPAL originagted logs
+ are makred as report externally.
+ We now only report logs with severity >= 0x22
+- IPMI: fixes to eSEL logging
+- hw/phb3: Change reserved PE to 255
+ - Currently, we have reserved PE#0 to which all RIDs are mapped prior
+ to PE assignment request from kernel. The last M64 BAR is configured
+ to have shared mode. So we have to cut off the first M64 segment,
+ which corresponds to reserved PE#0 in kernel. If the first BAR
+ (for example PF's IOV BAR) requires huge alignment in kernel, we
+ have to waste huge M64 space to accommodate the alignment. If we
+ have reserved PE#256, the waste of M64 space will be avoided.
+
+FSP-specific bugs fixed:
+- (also fixed in skiboot-5.0.2) Fix race in firenze_get_slot_info() leading to
+ assert() with many PCI cards
+ With many PCI cards, we'd hit a race where calls to
+ firenze_add_pcidev_to_fsp_inventory would step on each other leading to
+ memory corruption and finally an assert() in the allocator being hit
+ during boot.
+- PCIe power workaround for K80 cards
+- /ibm,opal/led renamed to /ibm,opal/leds in Device Tree
+ - compatible change as no FSP based systems shipped with skiboot-5.0
+
+General improvements:
+- Preliminary Centaur i2c support
+ - lays framework for supporting Centaur i2c
+- don't run pollers on non-boot CPUs in time_wait
+- improvements to opal-prd, pflash, libflash
+ - including new blocklevel interface in libflash
+- many minor fixes to issues found by static analysis
+- improvements in FSP error log code paths
+- code cleanup in memory allocator
+- Don't expose individual nvram partitions in the device tree, just the whole
+ flash device.
+- build improvements for building on ppc64el host
+- improvements in cpu_relax() for idle threads, needed for GCOV on large
+ machines.
+- Optimized memset() for POWER8, greatly reducing number of instructions
+ executed for boot, which helps boot time in simulators.
+- Major improvements in hello_world kernel
+ - Bloat of huge 17 instruction test case reduced to 10.
+- Disable bust_locks for general calls of abort()
+ - Should enable better error messages during abort() when other users of
+ LPC bus exist (e.g. flash)
+- unified version numbers for bundled utilities
+- external/boot_test/boot_test.sh
+ - better usable for automated boot testing
+
+Contributors
+------------
+Since skiboot-5.0, we've had the following changesets:
+
+Processed 372 csets from 27 developers
+2 employers found
+A total of 15868 lines added, 3359 removed (delta 12509)
+
+Developers with the most changesets
+Stewart Smith 117 (31.5%)
+Jeremy Kerr 37 (9.9%)
+Cyril Bur 33 (8.9%)
+Vasant Hegde 32 (8.6%)
+Benjamin Herrenschmidt 32 (8.6%)
+Kamalesh Babulal 22 (5.9%)
+Joel Stanley 12 (3.2%)
+Mahesh Salgaonkar 12 (3.2%)
+Alistair Popple 12 (3.2%)
+Neelesh Gupta 9 (2.4%)
+Gavin Shan 8 (2.2%)
+Cédric Le Goater 8 (2.2%)
+Ananth N Mavinakayanahalli 8 (2.2%)
+Vipin K Parashar 6 (1.6%)
+Michael Neuling 6 (1.6%)
+Samuel Mendoza-Jonas 3 (0.8%)
+Frederic Bonnard 3 (0.8%)
+Andrew Donnellan 2 (0.5%)
+Vaidyanathan Srinivasan 2 (0.5%)
+Philippe Bergheaud 1 (0.3%)
+Shilpasri G Bhat 1 (0.3%)
+Daniel Axtens 1 (0.3%)
+Hari Bathini 1 (0.3%)
+Michael Ellerman 1 (0.3%)
+Andrei Warkentin 1 (0.3%)
+Dan Horák 1 (0.3%)
+Anton Blanchard 1 (0.3%)
+
+Developers with the most changed lines
+Stewart Smith 4499 (27.3%)
+Benjamin Herrenschmidt 3782 (22.9%)
+Jeremy Kerr 1887 (11.4%)
+Cyril Bur 1654 (10.0%)
+Vasant Hegde 959 (5.8%)
+Mahesh Salgaonkar 886 (5.4%)
+Neelesh Gupta 473 (2.9%)
+Samuel Mendoza-Jonas 387 (2.3%)
+Vipin K Parashar 332 (2.0%)
+Philippe Bergheaud 171 (1.0%)
+Shilpasri G Bhat 165 (1.0%)
+Alistair Popple 151 (0.9%)
+Joel Stanley 105 (0.6%)
+Cédric Le Goater 89 (0.5%)
+Gavin Shan 83 (0.5%)
+Frederic Bonnard 76 (0.5%)
+Kamalesh Babulal 65 (0.4%)
+Michael Neuling 46 (0.3%)
+Daniel Axtens 31 (0.2%)
+Andrew Donnellan 22 (0.1%)
+Ananth N Mavinakayanahalli 20 (0.1%)
+Anton Blanchard 3 (0.0%)
+Vaidyanathan Srinivasan 2 (0.0%)
+Hari Bathini 2 (0.0%)
+Michael Ellerman 1 (0.0%)
+Andrei Warkentin 1 (0.0%)
+Dan Horák 1 (0.0%)
+
+Developers with the most lines removed
+Michael Neuling 24 (0.7%)
+Hari Bathini 1 (0.0%)
+
+Developers with the most signoffs (total 253)
+Stewart Smith 249 (98.4%)
+Mahesh Salgaonkar 4 (1.6%)
+
+Developers with the most reviews (total 24)
+Vasant Hegde 9 (37.5%)
+Joel Stanley 3 (12.5%)
+Gavin Shan 2 (8.3%)
+Kamalesh Babulal 2 (8.3%)
+Samuel Mendoza-Jonas 2 (8.3%)
+Alistair Popple 2 (8.3%)
+Stewart Smith 1 (4.2%)
+Andrei Warkentin 1 (4.2%)
+Preeti U Murthy 1 (4.2%)
+Ananth N Mavinakayanahalli 1 (4.2%)
+
+Developers with the most test credits (total 1)
+Chad Larson 1 (100.0%)
+
+Developers who gave the most tested-by credits (total 1)
+Gavin Shan 1 (100.0%)
+
+Developers with the most report credits (total 4)
+Benjamin Herrenschmidt 2 (50.0%)
+Chad Larson 1 (25.0%)
+Andrei Warkentin 1 (25.0%)
+
+Developers who gave the most report credits (total 4)
+Stewart Smith 3 (75.0%)
+Gavin Shan 1 (25.0%)
+
+Top changeset contributors by employer
+IBM 369 (99.2%)
+(Unknown) 3 (0.8%)
+
+Top lines changed by employer
+IBM 16497 (100.0%)
+(Unknown) 3 (0.0%)
+
+Employers with the most signoffs (total 253)
+IBM 253 (100.0%)
+
+Employers with the most hackers (total 27)
+IBM 24 (88.9%)
+(Unknown) 3 (11.1%)
+
diff --git a/doc/release-notes/skiboot-5.1.0.txt b/doc/release-notes/skiboot-5.1.0.txt
deleted file mode 100644
index 8558378..0000000
--- a/doc/release-notes/skiboot-5.1.0.txt
+++ /dev/null
@@ -1,261 +0,0 @@
-skiboot-5.1.0
--------------
-
-skiboot-5.1.0 was released on August 17th, 2015.
-
-skiboot-5.1.0 is the first stable release of 5.1.0 following two beta releases.
-This new stable release replaces skiboot-5.0 as the current stable skiboot
-release (5.0 was released April 14th 2015).
-
-Skiboot 5.1.0 contains all fixes from skiboot-5.0 stable branch up to
-skiboot-5.0.5 and everything from 5.1.0-beta1 and 5.1.0-beta2.
-
-Over skiboot-5.1.0-beta2, we have the following changes:
-- opal_prd now supports multiple socket systems
-- fix compiler warnings in gard and libflash
-
-Below are the changes introduced in previous skiboot-5.1.0 releases over
-the previous stable release, skiboot-5.0:
-
-New features:
-- Add Naples chip (CPU, PHB, LPC serial interrupts) support
-- Added qemu platform
-- improvements to FSI error handling
-- improvements in chip TOD failover (some only on FSP systems)
-- Set Relative Priority Register (RPR) to recommended value
- - this affects thread priority in SMT modes
-- greatly reduce memory consumption by CPU stacks for non-present CPUs
- - Previously we would reserve enough memory for max PIR for each CPU
- type.
- - This fix frees up 77MB of RAM on a typical P8 system.
-- increased OPAL API documentation
-- Asynchronous preloading of resources from FSP/flash
- - improves boot time on some systems
-- Basic Garrison platform support
-- Add Mambo platform (P8 Functional Simulator, systemsim)
- - includes fake NVRAM, RTC
-- Support building with GCOV, increasing memory for skiboot binary to 2MB
- - includes boot code coverage testing
-- Increased skiboot HEAP size.
- - We are not aware of any system where you would run out, but on large
- systems it was getting closer than we liked.
-- add boot_tests.sh for helping automate boot testing on FSP and BMC machines
-- Versioning of pflash and gard utilities to help Linux (or other OS)
- distributions with packaging.
-- OCC throttle status messages to host
-- CAPP timebase sync ("ibm,capp-timebase-sync" in DT to indicate CAPP timebase
- was synced by OPAL)
-- opal-api: Add OPAL call to handle abnormal reboots.
- OPAL_CEC_REBOOT2
- Currently it will support two reboot types (0). normal reboot, that
- will behave similar to that of opal_cec_reboot() call, and
- (1). platform error reboot.
-
- Long term, this is designed to replace OPAL_CEC_REBOOT.
-
-New features for FSP based machines:
-- in-band IPMI support
-- ethernet adaptor location codes
-- add DIMM frequency information to device tree
-- improvements in FSP error log code paths
-- fix some boot time memory leaks
- - harmless to end user
-
-New features for AMI BMC based machines:
-- PCIe power workaround for K80
-- Added support for Macronix 128Mbit flash chips
-- Initial PRD support for Firestone platform
-- improved reliability when BMC reboots
-
-The following bugs have been fixed:
-- Increase PHB3 timeout for electrical links coming up to 2 seconds.
- - fixes issues with some Mellanox cards
-- Hang in opal_reinit_cpus() that could prevent kdump from functioning
-- PHB3: fix crash in phb3_init
-- PHB3: fix crash with fenced PHB in phb3_init_hw()
-- Fix bugs in hw/bt.c (interface for IPMI on BMC machines) that could possibly
- lead to a crash (dereferencing invalid address, deadlock)
-- ipmi/sel: fix use-after-free
-- Bug fixes in EEH handling
- - opal_pci_next_error() cleared OPAL_EVENT_PCI_ERROR unconditionally, possibly
- leading to missed errors.
-- external/opal-prd: Only map each PRD range once
- - could eventually lead to failing to map PRD ranges
-- On skiboot crash, don't try to print symbol when we didn't find one
- - makes backtrace prettier
-- On skiboot crash, dump hssr0 and hsrr1 registers correctly.
-- Better support old and biarch compilers
- - test "new" compiler flags before using them
- - Specify -mabi=elfv1 if supported (which means it's needed)
-- fix boot-coverage-report makefile target
-- ipmi: Fix the opal_ipmi_recv() call to handle the error path
- - Could make kernel a sad panda when in continues with other IPMI commands
-- IPMI: truncate SELs at 2kb
- - it's the limit of the astbmc. We think.
-- IPMI/SEL/PEL:
- - As per PEL spec, we should log events with severity >= 0x22 and "service
- action flag" is "on". But in our case, all logs OPAL originagted logs
- are makred as report externally.
- We now only report logs with severity >= 0x22
-- IPMI: fixes to eSEL logging
-- hw/phb3: Change reserved PE to 255
- - Currently, we have reserved PE#0 to which all RIDs are mapped prior
- to PE assignment request from kernel. The last M64 BAR is configured
- to have shared mode. So we have to cut off the first M64 segment,
- which corresponds to reserved PE#0 in kernel. If the first BAR
- (for example PF's IOV BAR) requires huge alignment in kernel, we
- have to waste huge M64 space to accommodate the alignment. If we
- have reserved PE#256, the waste of M64 space will be avoided.
-
-FSP-specific bugs fixed:
-- (also fixed in skiboot-5.0.2) Fix race in firenze_get_slot_info() leading to
- assert() with many PCI cards
- With many PCI cards, we'd hit a race where calls to
- firenze_add_pcidev_to_fsp_inventory would step on each other leading to
- memory corruption and finally an assert() in the allocator being hit
- during boot.
-- PCIe power workaround for K80 cards
-- /ibm,opal/led renamed to /ibm,opal/leds in Device Tree
- - compatible change as no FSP based systems shipped with skiboot-5.0
-
-General improvements:
-- Preliminary Centaur i2c support
- - lays framework for supporting Centaur i2c
-- don't run pollers on non-boot CPUs in time_wait
-- improvements to opal-prd, pflash, libflash
- - including new blocklevel interface in libflash
-- many minor fixes to issues found by static analysis
-- improvements in FSP error log code paths
-- code cleanup in memory allocator
-- Don't expose individual nvram partitions in the device tree, just the whole
- flash device.
-- build improvements for building on ppc64el host
-- improvements in cpu_relax() for idle threads, needed for GCOV on large
- machines.
-- Optimized memset() for POWER8, greatly reducing number of instructions
- executed for boot, which helps boot time in simulators.
-- Major improvements in hello_world kernel
- - Bloat of huge 17 instruction test case reduced to 10.
-- Disable bust_locks for general calls of abort()
- - Should enable better error messages during abort() when other users of
- LPC bus exist (e.g. flash)
-- unified version numbers for bundled utilities
-- external/boot_test/boot_test.sh
- - better usable for automated boot testing
-
-Contributors
-------------
-Since skiboot-5.0, we've had the following changesets:
-
-Processed 372 csets from 27 developers
-2 employers found
-A total of 15868 lines added, 3359 removed (delta 12509)
-
-Developers with the most changesets
-Stewart Smith 117 (31.5%)
-Jeremy Kerr 37 (9.9%)
-Cyril Bur 33 (8.9%)
-Vasant Hegde 32 (8.6%)
-Benjamin Herrenschmidt 32 (8.6%)
-Kamalesh Babulal 22 (5.9%)
-Joel Stanley 12 (3.2%)
-Mahesh Salgaonkar 12 (3.2%)
-Alistair Popple 12 (3.2%)
-Neelesh Gupta 9 (2.4%)
-Gavin Shan 8 (2.2%)
-Cédric Le Goater 8 (2.2%)
-Ananth N Mavinakayanahalli 8 (2.2%)
-Vipin K Parashar 6 (1.6%)
-Michael Neuling 6 (1.6%)
-Samuel Mendoza-Jonas 3 (0.8%)
-Frederic Bonnard 3 (0.8%)
-Andrew Donnellan 2 (0.5%)
-Vaidyanathan Srinivasan 2 (0.5%)
-Philippe Bergheaud 1 (0.3%)
-Shilpasri G Bhat 1 (0.3%)
-Daniel Axtens 1 (0.3%)
-Hari Bathini 1 (0.3%)
-Michael Ellerman 1 (0.3%)
-Andrei Warkentin 1 (0.3%)
-Dan Horák 1 (0.3%)
-Anton Blanchard 1 (0.3%)
-
-Developers with the most changed lines
-Stewart Smith 4499 (27.3%)
-Benjamin Herrenschmidt 3782 (22.9%)
-Jeremy Kerr 1887 (11.4%)
-Cyril Bur 1654 (10.0%)
-Vasant Hegde 959 (5.8%)
-Mahesh Salgaonkar 886 (5.4%)
-Neelesh Gupta 473 (2.9%)
-Samuel Mendoza-Jonas 387 (2.3%)
-Vipin K Parashar 332 (2.0%)
-Philippe Bergheaud 171 (1.0%)
-Shilpasri G Bhat 165 (1.0%)
-Alistair Popple 151 (0.9%)
-Joel Stanley 105 (0.6%)
-Cédric Le Goater 89 (0.5%)
-Gavin Shan 83 (0.5%)
-Frederic Bonnard 76 (0.5%)
-Kamalesh Babulal 65 (0.4%)
-Michael Neuling 46 (0.3%)
-Daniel Axtens 31 (0.2%)
-Andrew Donnellan 22 (0.1%)
-Ananth N Mavinakayanahalli 20 (0.1%)
-Anton Blanchard 3 (0.0%)
-Vaidyanathan Srinivasan 2 (0.0%)
-Hari Bathini 2 (0.0%)
-Michael Ellerman 1 (0.0%)
-Andrei Warkentin 1 (0.0%)
-Dan Horák 1 (0.0%)
-
-Developers with the most lines removed
-Michael Neuling 24 (0.7%)
-Hari Bathini 1 (0.0%)
-
-Developers with the most signoffs (total 253)
-Stewart Smith 249 (98.4%)
-Mahesh Salgaonkar 4 (1.6%)
-
-Developers with the most reviews (total 24)
-Vasant Hegde 9 (37.5%)
-Joel Stanley 3 (12.5%)
-Gavin Shan 2 (8.3%)
-Kamalesh Babulal 2 (8.3%)
-Samuel Mendoza-Jonas 2 (8.3%)
-Alistair Popple 2 (8.3%)
-Stewart Smith 1 (4.2%)
-Andrei Warkentin 1 (4.2%)
-Preeti U Murthy 1 (4.2%)
-Ananth N Mavinakayanahalli 1 (4.2%)
-
-Developers with the most test credits (total 1)
-Chad Larson 1 (100.0%)
-
-Developers who gave the most tested-by credits (total 1)
-Gavin Shan 1 (100.0%)
-
-Developers with the most report credits (total 4)
-Benjamin Herrenschmidt 2 (50.0%)
-Chad Larson 1 (25.0%)
-Andrei Warkentin 1 (25.0%)
-
-Developers who gave the most report credits (total 4)
-Stewart Smith 3 (75.0%)
-Gavin Shan 1 (25.0%)
-
-Top changeset contributors by employer
-IBM 369 (99.2%)
-(Unknown) 3 (0.8%)
-
-Top lines changed by employer
-IBM 16497 (100.0%)
-(Unknown) 3 (0.0%)
-
-Employers with the most signoffs (total 253)
-IBM 253 (100.0%)
-
-Employers with the most hackers (total 27)
-IBM 24 (88.9%)
-(Unknown) 3 (11.1%)
-
diff --git a/doc/release-notes/skiboot-5.1.1.rst b/doc/release-notes/skiboot-5.1.1.rst
new file mode 100644
index 0000000..982c082
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.1.rst
@@ -0,0 +1,41 @@
+skiboot-5.1.1
+-------------
+
+skiboot-5.1.1 was released on August 18th, 2015.
+
+skiboot-5.1.1 is the send stable release of 5.1, it follows skiboot-5.1.0.
+
+Skiboot 5.1.1 contains all fixes from skiboot-5.1.0 and is a minor bugfix
+release.
+
+Over skiboot-5.1.0, we have the following changes:
+- Fix detection of compiler options on ancient GCC (e.g. gcc 4.4, shipped with
+ RHEL6)
+- ensure the GNUC version defines for GCOV are coming from target CC rather
+ than host CC for extract-gcov
+- phb3: Continue CAPP setup even if PHB is already in CAPP mode
+ This fixes a critical bug in CAPI support.
+
+ CAPI requires that all faults are escalated into a fence, not a
+ freeze. This is done by setting bits in a number of MMIO
+ registers. phb3_set_capi_mode() calls phb3_init_capp_errors() to do
+ this. However, if the PHB is already in CAPP mode - for example in the
+ recovery case - phb3_set_capi_mode() will bail out early, and those
+ registers will not be set.
+
+ This is quite easy to verify. PCI config space access errors, for
+ example, normally cause a freeze. On a CAPI-mode PHB, they should
+ cause a fence. Say we have a CAPI card on PHB 0, and we inject a
+ PCI config space error:
+
+ echo 0x8000000000000000 > /sys/kernel/debug/powerpc/PCI0000/err_injct_inboundA;
+ lspci;
+
+ The first time we inject this, the PHB will fence and recover, but
+ won't reset the registers. Therefore, the second time we inject it,
+ we will incorrectly freeze, not fence.
+
+ Worse, the recovery for the resultant EEH freeze event interacts
+ poorly with the CAPP, triggering an EEH recovery of the PHB. The
+ combination of the two attempted recoveries will get the PHB into
+ an inoperable state.
diff --git a/doc/release-notes/skiboot-5.1.1.txt b/doc/release-notes/skiboot-5.1.1.txt
deleted file mode 100644
index 982c082..0000000
--- a/doc/release-notes/skiboot-5.1.1.txt
+++ /dev/null
@@ -1,41 +0,0 @@
-skiboot-5.1.1
--------------
-
-skiboot-5.1.1 was released on August 18th, 2015.
-
-skiboot-5.1.1 is the send stable release of 5.1, it follows skiboot-5.1.0.
-
-Skiboot 5.1.1 contains all fixes from skiboot-5.1.0 and is a minor bugfix
-release.
-
-Over skiboot-5.1.0, we have the following changes:
-- Fix detection of compiler options on ancient GCC (e.g. gcc 4.4, shipped with
- RHEL6)
-- ensure the GNUC version defines for GCOV are coming from target CC rather
- than host CC for extract-gcov
-- phb3: Continue CAPP setup even if PHB is already in CAPP mode
- This fixes a critical bug in CAPI support.
-
- CAPI requires that all faults are escalated into a fence, not a
- freeze. This is done by setting bits in a number of MMIO
- registers. phb3_set_capi_mode() calls phb3_init_capp_errors() to do
- this. However, if the PHB is already in CAPP mode - for example in the
- recovery case - phb3_set_capi_mode() will bail out early, and those
- registers will not be set.
-
- This is quite easy to verify. PCI config space access errors, for
- example, normally cause a freeze. On a CAPI-mode PHB, they should
- cause a fence. Say we have a CAPI card on PHB 0, and we inject a
- PCI config space error:
-
- echo 0x8000000000000000 > /sys/kernel/debug/powerpc/PCI0000/err_injct_inboundA;
- lspci;
-
- The first time we inject this, the PHB will fence and recover, but
- won't reset the registers. Therefore, the second time we inject it,
- we will incorrectly freeze, not fence.
-
- Worse, the recovery for the resultant EEH freeze event interacts
- poorly with the CAPP, triggering an EEH recovery of the PHB. The
- combination of the two attempted recoveries will get the PHB into
- an inoperable state.
diff --git a/doc/release-notes/skiboot-5.1.10.rst b/doc/release-notes/skiboot-5.1.10.rst
new file mode 100644
index 0000000..2ba85b3
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.10.rst
@@ -0,0 +1,34 @@
+skiboot-5.1.10
+--------------
+
+skiboot-5.1.10 was released on Friday November 13th, 2015.
+
+skiboot-5.1.10 is the 11th stable release of 5.1, it follows skiboot-5.1.9
+(which was released October 30th, 2015).
+
+Skiboot 5.1.10 contains all fixes from skiboot-5.1.9 and is a minor bug
+fix release.
+
+Over skiboot-5.1.9, we have the following change:
+
+IBM FSP machines:
+- FSP: Handle Delayed Power Off initiated CEC shutdown with FSP in Reset/Reload
+
+ In a scenario where the DPO has been initiated, but the FSP then went into
+ reset before the CEC power down came in, OPAL may not give up the link since
+ it may never see the PSI interrupt. So, if we are in dpo_pending and an FSP
+ reset is detected via the DISR, give up the PSI link voluntarily.
+
+Generic:
+- sensor: add a compatible property
+ OPAL needs an extra compatible property "ibm,opal-sensor" to make
+ module autoload work smoothly in Linux for ibmpowernv driver.
+- console: Completely flush output buffer before power down and reboot
+ Completely flush the output buffer of the console driver before
+ power down and reboot. Implements the flushing function for uart
+ consoles, which includes the astbmc and rhesus platforms.
+
+ This fixes an issue where some console output is sometimes lost before
+ power down or reboot in uart consoles. If this issue is also prevalent
+ in other console types then it can be fixed later by adding a .flush
+ to that driver's con_ops.
diff --git a/doc/release-notes/skiboot-5.1.10.txt b/doc/release-notes/skiboot-5.1.10.txt
deleted file mode 100644
index 2ba85b3..0000000
--- a/doc/release-notes/skiboot-5.1.10.txt
+++ /dev/null
@@ -1,34 +0,0 @@
-skiboot-5.1.10
---------------
-
-skiboot-5.1.10 was released on Friday November 13th, 2015.
-
-skiboot-5.1.10 is the 11th stable release of 5.1, it follows skiboot-5.1.9
-(which was released October 30th, 2015).
-
-Skiboot 5.1.10 contains all fixes from skiboot-5.1.9 and is a minor bug
-fix release.
-
-Over skiboot-5.1.9, we have the following change:
-
-IBM FSP machines:
-- FSP: Handle Delayed Power Off initiated CEC shutdown with FSP in Reset/Reload
-
- In a scenario where the DPO has been initiated, but the FSP then went into
- reset before the CEC power down came in, OPAL may not give up the link since
- it may never see the PSI interrupt. So, if we are in dpo_pending and an FSP
- reset is detected via the DISR, give up the PSI link voluntarily.
-
-Generic:
-- sensor: add a compatible property
- OPAL needs an extra compatible property "ibm,opal-sensor" to make
- module autoload work smoothly in Linux for ibmpowernv driver.
-- console: Completely flush output buffer before power down and reboot
- Completely flush the output buffer of the console driver before
- power down and reboot. Implements the flushing function for uart
- consoles, which includes the astbmc and rhesus platforms.
-
- This fixes an issue where some console output is sometimes lost before
- power down or reboot in uart consoles. If this issue is also prevalent
- in other console types then it can be fixed later by adding a .flush
- to that driver's con_ops.
diff --git a/doc/release-notes/skiboot-5.1.11.rst b/doc/release-notes/skiboot-5.1.11.rst
new file mode 100644
index 0000000..b2493b2
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.11.rst
@@ -0,0 +1,16 @@
+skiboot-5.1.11
+--------------
+
+skiboot-5.1.11 was released on Friday November 13th, 2015.
+
+Since it was Friday 13th, we had to find a bug right after we tagged
+and released skiboot-5.1.10.
+
+skiboot-5.1.11 is the 12th stable release of 5.1, it follows skiboot-5.1.10
+(which was released November 13th, 2015).
+
+Skiboot 5.1.11 contains one additional bug fix over skiboot-5.1.10.
+
+It is:
+- On IBM FSP machines, if IPMI/Serial console is not connected during shutdown
+ or reboot, machine would enter termination state rather than shut down.
diff --git a/doc/release-notes/skiboot-5.1.11.txt b/doc/release-notes/skiboot-5.1.11.txt
deleted file mode 100644
index b2493b2..0000000
--- a/doc/release-notes/skiboot-5.1.11.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-skiboot-5.1.11
---------------
-
-skiboot-5.1.11 was released on Friday November 13th, 2015.
-
-Since it was Friday 13th, we had to find a bug right after we tagged
-and released skiboot-5.1.10.
-
-skiboot-5.1.11 is the 12th stable release of 5.1, it follows skiboot-5.1.10
-(which was released November 13th, 2015).
-
-Skiboot 5.1.11 contains one additional bug fix over skiboot-5.1.10.
-
-It is:
-- On IBM FSP machines, if IPMI/Serial console is not connected during shutdown
- or reboot, machine would enter termination state rather than shut down.
diff --git a/doc/release-notes/skiboot-5.1.12.rst b/doc/release-notes/skiboot-5.1.12.rst
new file mode 100644
index 0000000..49a7e25
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.12.rst
@@ -0,0 +1,44 @@
+skiboot-5.1.12
+--------------
+
+skiboot-5.1.12 was released on Friday December 4th, 2015.
+
+skiboot-5.1.12 is the 13th stable release of 5.1, it follows skiboot-5.1.11
+(which was released November 13th, 2015).
+
+Skiboot 5.1.12 contains bug fixes and a performance improvement.
+
+opal-prd:
+- Display an explict and obvious message if running on a system that does
+ not support opal-prd, such as an IBM FSP based POWER system, where the
+ FSP takes on the role of opal-prd.
+
+pflash:
+- Fix a missing (C) header
+ - cherry-picked from master.
+
+General:
+- Don't link with libgcc
+ - On some toolchains, we don't have libgcc available.
+
+POWER8 PHB (PCIe) specific:
+- hw/phb3: Flush cache line after updating P/Q bits
+ When doing an MSI EOI, we update the P and Q bits in the IVE. That causes
+ the corresponding cache line to be dirty in the L3 which will cause a
+ subsequent update by the PHB (upon receiving the next MSI) to get a few
+ retries until it gets flushed.
+
+ We improve the situation (and thus performance) by doing a dcbf
+ instruction to force a flush of the update we do in SW.
+
+ This improves interrupt performance, reducing latency per interrupt.
+ The improvement will vary by workload.
+
+IBM FSP based machines:
+- FSP: Give up PSI link on shutdown
+ This clears up some erroneous SRCs (error logs) in some situations.
+- Correctly report back Real Time Clock errors to host
+ Under certain rare error conditions, we could return an error code
+ to the host OS that would cause current Linux kernels to get stuck
+ in an infinite loop during boot.
+ This was introduced in skiboot-5.0-rc1.
diff --git a/doc/release-notes/skiboot-5.1.12.txt b/doc/release-notes/skiboot-5.1.12.txt
deleted file mode 100644
index 49a7e25..0000000
--- a/doc/release-notes/skiboot-5.1.12.txt
+++ /dev/null
@@ -1,44 +0,0 @@
-skiboot-5.1.12
---------------
-
-skiboot-5.1.12 was released on Friday December 4th, 2015.
-
-skiboot-5.1.12 is the 13th stable release of 5.1, it follows skiboot-5.1.11
-(which was released November 13th, 2015).
-
-Skiboot 5.1.12 contains bug fixes and a performance improvement.
-
-opal-prd:
-- Display an explict and obvious message if running on a system that does
- not support opal-prd, such as an IBM FSP based POWER system, where the
- FSP takes on the role of opal-prd.
-
-pflash:
-- Fix a missing (C) header
- - cherry-picked from master.
-
-General:
-- Don't link with libgcc
- - On some toolchains, we don't have libgcc available.
-
-POWER8 PHB (PCIe) specific:
-- hw/phb3: Flush cache line after updating P/Q bits
- When doing an MSI EOI, we update the P and Q bits in the IVE. That causes
- the corresponding cache line to be dirty in the L3 which will cause a
- subsequent update by the PHB (upon receiving the next MSI) to get a few
- retries until it gets flushed.
-
- We improve the situation (and thus performance) by doing a dcbf
- instruction to force a flush of the update we do in SW.
-
- This improves interrupt performance, reducing latency per interrupt.
- The improvement will vary by workload.
-
-IBM FSP based machines:
-- FSP: Give up PSI link on shutdown
- This clears up some erroneous SRCs (error logs) in some situations.
-- Correctly report back Real Time Clock errors to host
- Under certain rare error conditions, we could return an error code
- to the host OS that would cause current Linux kernels to get stuck
- in an infinite loop during boot.
- This was introduced in skiboot-5.0-rc1.
diff --git a/doc/release-notes/skiboot-5.1.13.rst b/doc/release-notes/skiboot-5.1.13.rst
new file mode 100644
index 0000000..0bc3100
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.13.rst
@@ -0,0 +1,43 @@
+skiboot-5.1.13
+--------------
+
+skiboot-5.1.13 was released on Wed January 27th, 2016.
+
+skiboot-5.1.13 is the 14th stable release of 5.1, it follows skiboot-5.1.12
+(which was released December 4th, 2015). This release contains bug fixes.
+
+General:
+- core/device.c: Sort nodes with name at unit names by unit
+ - This gives predictable device tree ordering to the payload
+ (usually petitboot)
+ - This means that utilities such as "lspci" will always return the same
+ ordering.
+- Add OPAL_CONSOLE_FLUSH to the OPAL API
+ uart consoles only flush output when polled. The Linux kernel calls
+ these pollers frequently, except when in a panic state. As such, panic
+ messages are not fully printed unless the system is configured to reboot
+ after panic.
+
+ This patch adds a new call to the OPAL API to flush the buffer. If the
+ system has a uart console (i.e. BMC machines), it will incrementally
+ flush the buffer, returning if there is more to be flushed or not. If
+ the system has a different console, the function will have no effect.
+ This will allow the Linux kernel to ensure that panic message have been
+ fully printed out.
+
+CAPI:
+- hmi: Identify the phb upon CAPI malfunction alert
+ Previously, any error on a CAPI adapter would assume PHB0.
+ This could cause issues on Firestone machines.
+
+gard utility:
+- Fix displaying 'cleared' gard records
+ When a garded component is replaced hostboot detects this and updates the
+ gard partition.
+
+ Previously, there was ambiguity on if the gard record ID or the whole gard
+ record needed to be erased. This fix makes gard and hostboot agree.
+
+firestone platform:
+- fix spacing in slot name
+ The other SlotN names have no space.
diff --git a/doc/release-notes/skiboot-5.1.13.txt b/doc/release-notes/skiboot-5.1.13.txt
deleted file mode 100644
index 0bc3100..0000000
--- a/doc/release-notes/skiboot-5.1.13.txt
+++ /dev/null
@@ -1,43 +0,0 @@
-skiboot-5.1.13
---------------
-
-skiboot-5.1.13 was released on Wed January 27th, 2016.
-
-skiboot-5.1.13 is the 14th stable release of 5.1, it follows skiboot-5.1.12
-(which was released December 4th, 2015). This release contains bug fixes.
-
-General:
-- core/device.c: Sort nodes with name at unit names by unit
- - This gives predictable device tree ordering to the payload
- (usually petitboot)
- - This means that utilities such as "lspci" will always return the same
- ordering.
-- Add OPAL_CONSOLE_FLUSH to the OPAL API
- uart consoles only flush output when polled. The Linux kernel calls
- these pollers frequently, except when in a panic state. As such, panic
- messages are not fully printed unless the system is configured to reboot
- after panic.
-
- This patch adds a new call to the OPAL API to flush the buffer. If the
- system has a uart console (i.e. BMC machines), it will incrementally
- flush the buffer, returning if there is more to be flushed or not. If
- the system has a different console, the function will have no effect.
- This will allow the Linux kernel to ensure that panic message have been
- fully printed out.
-
-CAPI:
-- hmi: Identify the phb upon CAPI malfunction alert
- Previously, any error on a CAPI adapter would assume PHB0.
- This could cause issues on Firestone machines.
-
-gard utility:
-- Fix displaying 'cleared' gard records
- When a garded component is replaced hostboot detects this and updates the
- gard partition.
-
- Previously, there was ambiguity on if the gard record ID or the whole gard
- record needed to be erased. This fix makes gard and hostboot agree.
-
-firestone platform:
-- fix spacing in slot name
- The other SlotN names have no space.
diff --git a/doc/release-notes/skiboot-5.1.14.rst b/doc/release-notes/skiboot-5.1.14.rst
new file mode 100644
index 0000000..3032e77
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.14.rst
@@ -0,0 +1,20 @@
+skiboot-5.1.14
+--------------
+
+skiboot-5.1.14 was released on Wed March 9th, 2016.
+
+skiboot-5.1.14 is the 15th stable release of 5.1, it follows skiboot-5.1.13
+(which was released January 27th, 2016). This release contains a spelling
+fix in a log message and an added device tree property to enable older
+kernels (with bootloader support) to use a framebuffer that is redirected
+to the BMC VGA port.
+
+As such, skiboot-5.1.14 has no advantage over skiboot-5.1.13 unless you
+are wanting the neat offb framebuffer trick.
+
+Changes are:
+- fsp: fix spelling of "advertise" in log message
+ See: https://www.youtube.com/watch?v=8Gv0H-vPoDc
+- Explicit 1:1 mapping in ranges properties have been added to PCI
+ bridges. This allows a neat trick with offb and VGA ports that should
+ probably not be told to young children.
diff --git a/doc/release-notes/skiboot-5.1.14.txt b/doc/release-notes/skiboot-5.1.14.txt
deleted file mode 100644
index 3032e77..0000000
--- a/doc/release-notes/skiboot-5.1.14.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-skiboot-5.1.14
---------------
-
-skiboot-5.1.14 was released on Wed March 9th, 2016.
-
-skiboot-5.1.14 is the 15th stable release of 5.1, it follows skiboot-5.1.13
-(which was released January 27th, 2016). This release contains a spelling
-fix in a log message and an added device tree property to enable older
-kernels (with bootloader support) to use a framebuffer that is redirected
-to the BMC VGA port.
-
-As such, skiboot-5.1.14 has no advantage over skiboot-5.1.13 unless you
-are wanting the neat offb framebuffer trick.
-
-Changes are:
-- fsp: fix spelling of "advertise" in log message
- See: https://www.youtube.com/watch?v=8Gv0H-vPoDc
-- Explicit 1:1 mapping in ranges properties have been added to PCI
- bridges. This allows a neat trick with offb and VGA ports that should
- probably not be told to young children.
diff --git a/doc/release-notes/skiboot-5.1.15.rst b/doc/release-notes/skiboot-5.1.15.rst
new file mode 100644
index 0000000..05f3658
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.15.rst
@@ -0,0 +1,9 @@
+skiboot-5.1.15
+--------------
+
+skiboot-5.1.15 was released on Wed March 16th, 2016.
+
+skiboot-5.1.15 is the 16th stable release of 5.1, it follows skiboot-5.1.14
+(which was released March 9th, 2016). This release contains one bug fix, a
+fix for a memory leak in an error path for AMI BMC based systems when
+logging non-severe errors. As such, it is a minor bug fix update.
diff --git a/doc/release-notes/skiboot-5.1.15.txt b/doc/release-notes/skiboot-5.1.15.txt
deleted file mode 100644
index 05f3658..0000000
--- a/doc/release-notes/skiboot-5.1.15.txt
+++ /dev/null
@@ -1,9 +0,0 @@
-skiboot-5.1.15
---------------
-
-skiboot-5.1.15 was released on Wed March 16th, 2016.
-
-skiboot-5.1.15 is the 16th stable release of 5.1, it follows skiboot-5.1.14
-(which was released March 9th, 2016). This release contains one bug fix, a
-fix for a memory leak in an error path for AMI BMC based systems when
-logging non-severe errors. As such, it is a minor bug fix update.
diff --git a/doc/release-notes/skiboot-5.1.16.rst b/doc/release-notes/skiboot-5.1.16.rst
new file mode 100644
index 0000000..b33a42e
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.16.rst
@@ -0,0 +1,52 @@
+skiboot-5.1.16
+--------------
+
+skiboot-5.1.16 was released on Friday April 29th, 2016.
+
+skiboot-5.1.16 is the 17th stable release of 5.1, it follows skiboot-5.1.15
+(which was released March 16th, 2016).
+
+This release contains a few bug fixes and is a recommended upgrade.
+
+Changes are:
+
+PHB3 (all POWER8 platforms):
+- hw/phb3: Ensure PQ bits are cleared in the IVC when masking IRQ
+ When we mask an interrupt, we may race with another interrupt coming
+ in from the hardware. If this occurs, the P and/or Q bit may end up
+ being set but we never EOI/clear them. This could result in a lost
+ interrupt or the next interrupt that comes in after re-enabling never
+ being presented.
+
+ This fixes a bug seen with some CAPI workloads which have lots of
+ interrupt masking at the same time as high interrupt load. The fix is
+ not specific to CAPI though.
+- hw/phb3: Fix potential race in EOI
+ When we EOI we need to clear the present (P) bit in the Interrupt
+ Vector Cache (IVC). We must clear P ensuring that any additional
+ interrupts that come in aren't lost while also maintaining coherency
+ with the Interrupt Vector Table (IVT).
+
+ To do this, the hardware provides a conditional update bit in the
+ IVC. This bit ensures that generation counts between the IVT and the
+ IVC updates are synchronised.
+
+ Unfortunately we never set this the bit to conditionally update the P
+ bit in the IVC based on the generation count. Also, we didn't set
+ what we wanted the new generation count to be if the update was
+ successful.
+
+FSP platforms:
+- OPAL:Handle mbox response with bad status:0x24 during FSP termination
+ OPAL committed a predictive log with SRC BB822411 in some situations.
+
+Generic:
+- hmi: Fix a bug where partial hmi event was reported to host.
+ This bug fix ensures the CPU PIR is reported correctly:
+ [ 305.628283] Fatal Hypervisor Maintenance interrupt [Not recovered]
+ [ 305.628341] Error detail: Malfunction Alert
+ [ 305.628388] HMER: 8040000000000000
+ - [ 305.628423] CPU PIR: 00000000
+ + [ 200.123021] CPU PIR: 000008e8
+ [ 305.628458] [Unit: VSU] Logic core check stop
+
diff --git a/doc/release-notes/skiboot-5.1.16.txt b/doc/release-notes/skiboot-5.1.16.txt
deleted file mode 100644
index b33a42e..0000000
--- a/doc/release-notes/skiboot-5.1.16.txt
+++ /dev/null
@@ -1,52 +0,0 @@
-skiboot-5.1.16
---------------
-
-skiboot-5.1.16 was released on Friday April 29th, 2016.
-
-skiboot-5.1.16 is the 17th stable release of 5.1, it follows skiboot-5.1.15
-(which was released March 16th, 2016).
-
-This release contains a few bug fixes and is a recommended upgrade.
-
-Changes are:
-
-PHB3 (all POWER8 platforms):
-- hw/phb3: Ensure PQ bits are cleared in the IVC when masking IRQ
- When we mask an interrupt, we may race with another interrupt coming
- in from the hardware. If this occurs, the P and/or Q bit may end up
- being set but we never EOI/clear them. This could result in a lost
- interrupt or the next interrupt that comes in after re-enabling never
- being presented.
-
- This fixes a bug seen with some CAPI workloads which have lots of
- interrupt masking at the same time as high interrupt load. The fix is
- not specific to CAPI though.
-- hw/phb3: Fix potential race in EOI
- When we EOI we need to clear the present (P) bit in the Interrupt
- Vector Cache (IVC). We must clear P ensuring that any additional
- interrupts that come in aren't lost while also maintaining coherency
- with the Interrupt Vector Table (IVT).
-
- To do this, the hardware provides a conditional update bit in the
- IVC. This bit ensures that generation counts between the IVT and the
- IVC updates are synchronised.
-
- Unfortunately we never set this the bit to conditionally update the P
- bit in the IVC based on the generation count. Also, we didn't set
- what we wanted the new generation count to be if the update was
- successful.
-
-FSP platforms:
-- OPAL:Handle mbox response with bad status:0x24 during FSP termination
- OPAL committed a predictive log with SRC BB822411 in some situations.
-
-Generic:
-- hmi: Fix a bug where partial hmi event was reported to host.
- This bug fix ensures the CPU PIR is reported correctly:
- [ 305.628283] Fatal Hypervisor Maintenance interrupt [Not recovered]
- [ 305.628341] Error detail: Malfunction Alert
- [ 305.628388] HMER: 8040000000000000
- - [ 305.628423] CPU PIR: 00000000
- + [ 200.123021] CPU PIR: 000008e8
- [ 305.628458] [Unit: VSU] Logic core check stop
-
diff --git a/doc/release-notes/skiboot-5.1.17.rst b/doc/release-notes/skiboot-5.1.17.rst
new file mode 100644
index 0000000..baacf48
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.17.rst
@@ -0,0 +1,19 @@
+skiboot-5.1.17
+--------------
+
+skiboot-5.1.17 was released on Thursday 21st July 2016.
+
+skiboot-5.1.17 is the 18th stable release of 5.1, it follows skiboot-5.1.16
+(which was released April 29th, 2016).
+
+This release contains a few minor bug fixes.
+
+Changes are:
+
+All platforms:
+- Fix a few typos in user visible (OPAL log) strings
+- pci: Do a dummy config write to devices to establish bus number
+- Make the XSCOM engine code more resilient to errors:
+ - hw/xscom: Reset XSCOM engine after querying sleeping core FIR
+ - hw/xscom: Reset XSCOM engine after finite number of retries when busy
+ - xscom: Return OPAL_WRONG_STATE on XSCOM ops if CPU is asleep
diff --git a/doc/release-notes/skiboot-5.1.17.txt b/doc/release-notes/skiboot-5.1.17.txt
deleted file mode 100644
index baacf48..0000000
--- a/doc/release-notes/skiboot-5.1.17.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-skiboot-5.1.17
---------------
-
-skiboot-5.1.17 was released on Thursday 21st July 2016.
-
-skiboot-5.1.17 is the 18th stable release of 5.1, it follows skiboot-5.1.16
-(which was released April 29th, 2016).
-
-This release contains a few minor bug fixes.
-
-Changes are:
-
-All platforms:
-- Fix a few typos in user visible (OPAL log) strings
-- pci: Do a dummy config write to devices to establish bus number
-- Make the XSCOM engine code more resilient to errors:
- - hw/xscom: Reset XSCOM engine after querying sleeping core FIR
- - hw/xscom: Reset XSCOM engine after finite number of retries when busy
- - xscom: Return OPAL_WRONG_STATE on XSCOM ops if CPU is asleep
diff --git a/doc/release-notes/skiboot-5.1.2.rst b/doc/release-notes/skiboot-5.1.2.rst
new file mode 100644
index 0000000..e64932e
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.2.rst
@@ -0,0 +1,125 @@
+skiboot-5.1.2
+-------------
+
+skiboot-5.1.2 was released on September 9th, 2015.
+
+skiboot-5.1.2 is the third stable release of 5.1, it follows skiboot-5.1.1
+(which was released August 18th, 2015).
+
+Skiboot 5.1.2 contains all fixes from skiboot-5.1.1 and is a minor bugfix
+release.
+
+Over skiboot-5.1.1, we have the following changes:
+- phb3: Handle fence in phb3_pci_msi_check_q to fix hang
+
+ If the PHB is fenced during phb3_pci_msi_check_q, it can get stuck in an
+ infinite loop waiting to lock the FFI. Further, as the phb lock is held
+ during this function it will prevent any other CPUs from dealing with
+ the fence, leading to the entire system hanging.
+
+ If the PHB_FFI_LOCK returns all Fs, return immediately to allow the
+ fence to be dealt with.
+- phb3: Continue CAPP setup even if PHB is already in CAPP mode
+ This fixes a critical bug in CAPI support.
+- Platform hook for terminate call
+ - on assert() or other firmware failure, we will make a SEL callout
+ on ASTBMC platforms
+ - (slight) refactor of code for IBM-FSP platforms
+- refactor slot naming code
+- Slot names for Habanero platform
+- misc improvements in userspace utilities (incl pflash, gard)
+- build improvements
+ - fixes for two compiler warnings were squashed in 5.1.1 commit,
+ re-introduce the fixes.
+ - misc compiler/static analysis warning fixes
+
+- gard utility:
+ - If gard tool detects the GUARD PNOR partition is corrupted, it will
+ pro-actively re-initialize it.
+ Modern Hostboot is more sensitive to the content of the GUARD partition
+ in order to boot.
+ - Update record clearing to match Hostboots expectations
+ We now write ECC bytes throughout the whole partition.
+ Without this fix, hostboot may not bring up the machine.
+ - In the event of a corrupted GUARD partition so that even the first entry
+ cannot be read, the gard utility now provides the user with the option
+ to wipe the entirety of the GUARD partition to attempt recovery.
+
+- opal_prd utility:
+ - Add run command to pass through commands to HostBoot RunTime (HBRT)
+ - this is for OpenPower firmware developers only.
+ - Add htmght-passthru command.
+ - this is for OpenPower firmware developers only.
+ - Add override interface to pass attribute-override information to HBRT.
+ - Server sends response in error path, so that client doesn't block forever
+
+- external/mambo tcl scripts
+ - Running little-endian kernels in mambo requires HILE to be set properly,
+ which requires a bump in the machine's pvr value to a DD2.x chip.
+
+Stats
+-----
+For skiboot-5.1.0 to 5.1.2:
+Processed 67 csets from 11 developers
+1 employers found
+A total of 2258 lines added, 784 removed (delta 1474)
+
+Developers with the most changesets
+Stewart Smith 24 (35.8%)
+Cyril Bur 18 (26.9%)
+Vasant Hegde 8 (11.9%)
+Neelesh Gupta 5 (7.5%)
+Benjamin Herrenschmidt 5 (7.5%)
+Daniel Axtens 2 (3.0%)
+Samuel Mendoza-Jonas 1 (1.5%)
+Vaidyanathan Srinivasan 1 (1.5%)
+Vipin K Parashar 1 (1.5%)
+Ian Munsie 1 (1.5%)
+Michael Neuling 1 (1.5%)
+
+Developers with the most changed lines
+Cyril Bur 969 (42.5%)
+Neelesh Gupta 433 (19.0%)
+Benjamin Herrenschmidt 304 (13.3%)
+Vasant Hegde 236 (10.3%)
+Stewart Smith 163 (7.1%)
+Vaidyanathan Srinivasan 135 (5.9%)
+Vipin K Parashar 8 (0.4%)
+Ian Munsie 8 (0.4%)
+Daniel Axtens 2 (0.1%)
+Michael Neuling 2 (0.1%)
+Samuel Mendoza-Jonas 1 (0.0%)
+
+Developers with the most lines removed
+Daniel Axtens 2 (0.3%)
+Michael Neuling 1 (0.1%)
+
+Developers with the most signoffs (total 44)
+Stewart Smith 43 (97.7%)
+Neelesh Gupta 1 (2.3%)
+
+Developers with the most reviews (total 8)
+Patrick Williams 5 (62.5%)
+Samuel Mendoza-Jonas 3 (37.5%)
+
+Developers with the most test credits (total 0)
+
+Developers who gave the most tested-by credits (total 0)
+
+Developers with the most report credits (total 1)
+Benjamin Herrenschmidt 1 (100.0%)
+
+Developers who gave the most report credits (total 1)
+Samuel Mendoza-Jonas 1 (100.0%)
+
+Top changeset contributors by employer
+IBM 67 (100.0%)
+
+Top lines changed by employer
+IBM 2281 (100.0%)
+
+Employers with the most signoffs (total 44)
+IBM 44 (100.0%)
+
+Employers with the most hackers (total 11)
+IBM 11 (100.0%)
diff --git a/doc/release-notes/skiboot-5.1.2.txt b/doc/release-notes/skiboot-5.1.2.txt
deleted file mode 100644
index e64932e..0000000
--- a/doc/release-notes/skiboot-5.1.2.txt
+++ /dev/null
@@ -1,125 +0,0 @@
-skiboot-5.1.2
--------------
-
-skiboot-5.1.2 was released on September 9th, 2015.
-
-skiboot-5.1.2 is the third stable release of 5.1, it follows skiboot-5.1.1
-(which was released August 18th, 2015).
-
-Skiboot 5.1.2 contains all fixes from skiboot-5.1.1 and is a minor bugfix
-release.
-
-Over skiboot-5.1.1, we have the following changes:
-- phb3: Handle fence in phb3_pci_msi_check_q to fix hang
-
- If the PHB is fenced during phb3_pci_msi_check_q, it can get stuck in an
- infinite loop waiting to lock the FFI. Further, as the phb lock is held
- during this function it will prevent any other CPUs from dealing with
- the fence, leading to the entire system hanging.
-
- If the PHB_FFI_LOCK returns all Fs, return immediately to allow the
- fence to be dealt with.
-- phb3: Continue CAPP setup even if PHB is already in CAPP mode
- This fixes a critical bug in CAPI support.
-- Platform hook for terminate call
- - on assert() or other firmware failure, we will make a SEL callout
- on ASTBMC platforms
- - (slight) refactor of code for IBM-FSP platforms
-- refactor slot naming code
-- Slot names for Habanero platform
-- misc improvements in userspace utilities (incl pflash, gard)
-- build improvements
- - fixes for two compiler warnings were squashed in 5.1.1 commit,
- re-introduce the fixes.
- - misc compiler/static analysis warning fixes
-
-- gard utility:
- - If gard tool detects the GUARD PNOR partition is corrupted, it will
- pro-actively re-initialize it.
- Modern Hostboot is more sensitive to the content of the GUARD partition
- in order to boot.
- - Update record clearing to match Hostboots expectations
- We now write ECC bytes throughout the whole partition.
- Without this fix, hostboot may not bring up the machine.
- - In the event of a corrupted GUARD partition so that even the first entry
- cannot be read, the gard utility now provides the user with the option
- to wipe the entirety of the GUARD partition to attempt recovery.
-
-- opal_prd utility:
- - Add run command to pass through commands to HostBoot RunTime (HBRT)
- - this is for OpenPower firmware developers only.
- - Add htmght-passthru command.
- - this is for OpenPower firmware developers only.
- - Add override interface to pass attribute-override information to HBRT.
- - Server sends response in error path, so that client doesn't block forever
-
-- external/mambo tcl scripts
- - Running little-endian kernels in mambo requires HILE to be set properly,
- which requires a bump in the machine's pvr value to a DD2.x chip.
-
-Stats
------
-For skiboot-5.1.0 to 5.1.2:
-Processed 67 csets from 11 developers
-1 employers found
-A total of 2258 lines added, 784 removed (delta 1474)
-
-Developers with the most changesets
-Stewart Smith 24 (35.8%)
-Cyril Bur 18 (26.9%)
-Vasant Hegde 8 (11.9%)
-Neelesh Gupta 5 (7.5%)
-Benjamin Herrenschmidt 5 (7.5%)
-Daniel Axtens 2 (3.0%)
-Samuel Mendoza-Jonas 1 (1.5%)
-Vaidyanathan Srinivasan 1 (1.5%)
-Vipin K Parashar 1 (1.5%)
-Ian Munsie 1 (1.5%)
-Michael Neuling 1 (1.5%)
-
-Developers with the most changed lines
-Cyril Bur 969 (42.5%)
-Neelesh Gupta 433 (19.0%)
-Benjamin Herrenschmidt 304 (13.3%)
-Vasant Hegde 236 (10.3%)
-Stewart Smith 163 (7.1%)
-Vaidyanathan Srinivasan 135 (5.9%)
-Vipin K Parashar 8 (0.4%)
-Ian Munsie 8 (0.4%)
-Daniel Axtens 2 (0.1%)
-Michael Neuling 2 (0.1%)
-Samuel Mendoza-Jonas 1 (0.0%)
-
-Developers with the most lines removed
-Daniel Axtens 2 (0.3%)
-Michael Neuling 1 (0.1%)
-
-Developers with the most signoffs (total 44)
-Stewart Smith 43 (97.7%)
-Neelesh Gupta 1 (2.3%)
-
-Developers with the most reviews (total 8)
-Patrick Williams 5 (62.5%)
-Samuel Mendoza-Jonas 3 (37.5%)
-
-Developers with the most test credits (total 0)
-
-Developers who gave the most tested-by credits (total 0)
-
-Developers with the most report credits (total 1)
-Benjamin Herrenschmidt 1 (100.0%)
-
-Developers who gave the most report credits (total 1)
-Samuel Mendoza-Jonas 1 (100.0%)
-
-Top changeset contributors by employer
-IBM 67 (100.0%)
-
-Top lines changed by employer
-IBM 2281 (100.0%)
-
-Employers with the most signoffs (total 44)
-IBM 44 (100.0%)
-
-Employers with the most hackers (total 11)
-IBM 11 (100.0%)
diff --git a/doc/release-notes/skiboot-5.1.3.rst b/doc/release-notes/skiboot-5.1.3.rst
new file mode 100644
index 0000000..7c69fd6
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.3.rst
@@ -0,0 +1,92 @@
+skiboot-5.1.3
+-------------
+
+skiboot-5.1.3 was released on September 15th, 2015.
+
+skiboot-5.1.3 is the 4th stable release of 5.1, it follows skiboot-5.1.2
+(which was released September 9th, 2015).
+
+Skiboot 5.1.3 contains all fixes from skiboot-5.1.2 and is a minor bugfix
+release.
+
+Over skiboot-5.1.2, we have the following changes:
+
+- slot names for firestone platform
+- fix display of LPC errors
+- SBE based timer support
+ - on supported platforms limits reliance on Linux heartbeat
+- fix use-after-free in fsp/ipmi
+- fix hang on TOD/TB errors (time-of-day/timebase) on OpenPower systems
+ - On getting a Hypervizor Maintenance Interrupt to get the timebase
+ back into a running state, we would call prlog which would use
+ the LPC UART console driver on OpenPower systems, which depends on
+ a working timebase, leading to a hang.
+ We now don't depend on a working timebase in this recovery codepath.
+- enable prd for garrison platform
+- PCI: Clear error bits after changing MPS
+ Chaning MPS on PCI upstream bridge might cause error bits set on
+ downstream endpoints when system boots into Linux as below case
+ shows:
+ host# lspci -vvs 0001:06:00.0
+ 0001:06:00.0 Ethernet controller: Broadcom Corporation \
+ NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
+ DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
+ CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
+
+ This clears those error bits in AER and PCIe capability after MPS
+ is changed. With the patch applied, no more error bits are seen.
+
+Contributors
+------------
+Processed 14 csets from 6 developers
+1 employers found
+A total of 462 lines added, 163 removed (delta 299)
+
+Developers with the most changesets
+Benjamin Herrenschmidt 5 (35.7%)
+Stewart Smith 4 (28.6%)
+Mahesh Salgaonkar 2 (14.3%)
+Gavin Shan 1 (7.1%)
+Jeremy Kerr 1 (7.1%)
+Neelesh Gupta 1 (7.1%)
+
+Developers with the most changed lines
+Benjamin Herrenschmidt 407 (80.8%)
+Mahesh Salgaonkar 23 (4.6%)
+Gavin Shan 19 (3.8%)
+Stewart Smith 18 (3.6%)
+Jeremy Kerr 5 (1.0%)
+Neelesh Gupta 2 (0.4%)
+
+Developers with the most lines removed
+Stewart Smith 8 (4.9%)
+Jeremy Kerr 3 (1.8%)
+Neelesh Gupta 1 (0.6%)
+
+Developers with the most signoffs (total 10)
+Stewart Smith 10 (100.0%)
+
+Developers with the most reviews (total 1)
+Joel Stanley 1 (100.0%)
+
+Developers with the most test credits (total 0)
+
+Developers who gave the most tested-by credits (total 0)
+
+Developers with the most report credits (total 1)
+John Walthour 1 (100.0%)
+
+Developers who gave the most report credits (total 1)
+Gavin Shan 1 (100.0%)
+
+Top changeset contributors by employer
+IBM 14 (100.0%)
+
+Top lines changed by employer
+IBM 504 (100.0%)
+
+Employers with the most signoffs (total 10)
+IBM 10 (100.0%)
+
+Employers with the most hackers (total 6)
+IBM 6 (100.0%)
diff --git a/doc/release-notes/skiboot-5.1.3.txt b/doc/release-notes/skiboot-5.1.3.txt
deleted file mode 100644
index 7c69fd6..0000000
--- a/doc/release-notes/skiboot-5.1.3.txt
+++ /dev/null
@@ -1,92 +0,0 @@
-skiboot-5.1.3
--------------
-
-skiboot-5.1.3 was released on September 15th, 2015.
-
-skiboot-5.1.3 is the 4th stable release of 5.1, it follows skiboot-5.1.2
-(which was released September 9th, 2015).
-
-Skiboot 5.1.3 contains all fixes from skiboot-5.1.2 and is a minor bugfix
-release.
-
-Over skiboot-5.1.2, we have the following changes:
-
-- slot names for firestone platform
-- fix display of LPC errors
-- SBE based timer support
- - on supported platforms limits reliance on Linux heartbeat
-- fix use-after-free in fsp/ipmi
-- fix hang on TOD/TB errors (time-of-day/timebase) on OpenPower systems
- - On getting a Hypervizor Maintenance Interrupt to get the timebase
- back into a running state, we would call prlog which would use
- the LPC UART console driver on OpenPower systems, which depends on
- a working timebase, leading to a hang.
- We now don't depend on a working timebase in this recovery codepath.
-- enable prd for garrison platform
-- PCI: Clear error bits after changing MPS
- Chaning MPS on PCI upstream bridge might cause error bits set on
- downstream endpoints when system boots into Linux as below case
- shows:
- host# lspci -vvs 0001:06:00.0
- 0001:06:00.0 Ethernet controller: Broadcom Corporation \
- NetXtreme II BCM57810 10 Gigabit Ethernet (rev 10)
- DevSta: CorrErr+ UncorrErr- FatalErr- UnsuppReq+ AuxPwr- TransPend-
- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- NonFatalErr+
-
- This clears those error bits in AER and PCIe capability after MPS
- is changed. With the patch applied, no more error bits are seen.
-
-Contributors
-------------
-Processed 14 csets from 6 developers
-1 employers found
-A total of 462 lines added, 163 removed (delta 299)
-
-Developers with the most changesets
-Benjamin Herrenschmidt 5 (35.7%)
-Stewart Smith 4 (28.6%)
-Mahesh Salgaonkar 2 (14.3%)
-Gavin Shan 1 (7.1%)
-Jeremy Kerr 1 (7.1%)
-Neelesh Gupta 1 (7.1%)
-
-Developers with the most changed lines
-Benjamin Herrenschmidt 407 (80.8%)
-Mahesh Salgaonkar 23 (4.6%)
-Gavin Shan 19 (3.8%)
-Stewart Smith 18 (3.6%)
-Jeremy Kerr 5 (1.0%)
-Neelesh Gupta 2 (0.4%)
-
-Developers with the most lines removed
-Stewart Smith 8 (4.9%)
-Jeremy Kerr 3 (1.8%)
-Neelesh Gupta 1 (0.6%)
-
-Developers with the most signoffs (total 10)
-Stewart Smith 10 (100.0%)
-
-Developers with the most reviews (total 1)
-Joel Stanley 1 (100.0%)
-
-Developers with the most test credits (total 0)
-
-Developers who gave the most tested-by credits (total 0)
-
-Developers with the most report credits (total 1)
-John Walthour 1 (100.0%)
-
-Developers who gave the most report credits (total 1)
-Gavin Shan 1 (100.0%)
-
-Top changeset contributors by employer
-IBM 14 (100.0%)
-
-Top lines changed by employer
-IBM 504 (100.0%)
-
-Employers with the most signoffs (total 10)
-IBM 10 (100.0%)
-
-Employers with the most hackers (total 6)
-IBM 6 (100.0%)
diff --git a/doc/release-notes/skiboot-5.1.4.rst b/doc/release-notes/skiboot-5.1.4.rst
new file mode 100644
index 0000000..0ee06e1
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.4.rst
@@ -0,0 +1,32 @@
+skiboot-5.1.4
+-------------
+
+skiboot-5.1.4 was released on September 26th, 2015.
+
+skiboot-5.1.4 is the 5th stable release of 5.1, it follows skiboot-5.1.3
+(which was released September 15th, 2015).
+
+Skiboot 5.1.4 contains all fixes from skiboot-5.1.3 and is an important bug
+fix release and a strongly recommended update from any prior skiboot-5.1.x
+release.
+
+Over skiboot-5.1.3, we have the following changes:
+
+- Rate limit OPAL_MSG_OCC to only one outstanding message to host
+
+ In the event of a lot of OCC events (or many CPU cores), we could
+ send many OCC messages to the host, which if it wasn't calling
+ opal_get_msg really often, would cause skiboot to malloc() additional
+ messages until we ran out of skiboot heap and things didn't end up
+ being much fun.
+
+ When running certain hardware exercisers, they seem to steal all time
+ from Linux being able to call opal_get_msg, causing these to queue up
+ and get "opalmsg: No available node in the free list, allocating" warnings
+ followed by tonnes of backtraces of failing memory allocations.
+
+- Ensure reserved memory ranges are exposed correctly to host
+ (fix corrupted SLW image)
+
+ We seem to have not hit this on ASTBMC based OpenPower machines, but was
+ certainly hit on FSP based machines
diff --git a/doc/release-notes/skiboot-5.1.4.txt b/doc/release-notes/skiboot-5.1.4.txt
deleted file mode 100644
index 0ee06e1..0000000
--- a/doc/release-notes/skiboot-5.1.4.txt
+++ /dev/null
@@ -1,32 +0,0 @@
-skiboot-5.1.4
--------------
-
-skiboot-5.1.4 was released on September 26th, 2015.
-
-skiboot-5.1.4 is the 5th stable release of 5.1, it follows skiboot-5.1.3
-(which was released September 15th, 2015).
-
-Skiboot 5.1.4 contains all fixes from skiboot-5.1.3 and is an important bug
-fix release and a strongly recommended update from any prior skiboot-5.1.x
-release.
-
-Over skiboot-5.1.3, we have the following changes:
-
-- Rate limit OPAL_MSG_OCC to only one outstanding message to host
-
- In the event of a lot of OCC events (or many CPU cores), we could
- send many OCC messages to the host, which if it wasn't calling
- opal_get_msg really often, would cause skiboot to malloc() additional
- messages until we ran out of skiboot heap and things didn't end up
- being much fun.
-
- When running certain hardware exercisers, they seem to steal all time
- from Linux being able to call opal_get_msg, causing these to queue up
- and get "opalmsg: No available node in the free list, allocating" warnings
- followed by tonnes of backtraces of failing memory allocations.
-
-- Ensure reserved memory ranges are exposed correctly to host
- (fix corrupted SLW image)
-
- We seem to have not hit this on ASTBMC based OpenPower machines, but was
- certainly hit on FSP based machines
diff --git a/doc/release-notes/skiboot-5.1.5.rst b/doc/release-notes/skiboot-5.1.5.rst
new file mode 100644
index 0000000..7b594bf
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.5.rst
@@ -0,0 +1,39 @@
+skiboot-5.1.5
+-------------
+
+skiboot-5.1.5 was released on October 1st, 2015.
+
+skiboot-5.1.5 is the 6th stable release of 5.1, it follows skiboot-5.1.4
+(which was released September 26th, 2015).
+
+Skiboot 5.1.5 contains all fixes from skiboot-5.1.4 and is a minor bug
+fix release.
+
+Over skiboot-5.1.4, we have the following changes:
+
+Generic:
+- centaur: Add indirect XSCOM support
+ Fixes a bug where opal-prd would not be able to recover from a bunch
+ of errors as the indirect XSCOMs to centaurs would fail.
+- xscom: Fix logging of indirect XSCOM errors
+ Better logging of error messages.
+- PHB3: Fix wrong PE number in error injection
+- Improvement in boot_test.sh utility to support copying a pflash binary
+ to BMCs.
+
+AST BMC machines:
+- ipmi-sel: Run power action immediately if host not up
+ Our normal sequence for a soft power action (IPMI 'power soft' or
+ 'power cycle') involve receiving a SEL from the BMC, sending a message
+ to Linux's opal platform support which instructs the host OS to shut
+ down, and finally the host will request OPAL to cut power.
+
+ When the host is not yet up we will send the message to /dev/null, and
+ no action will be taken. This patches changes that behaviour to perform
+ the action immediately if we know how.
+
+OpenPower machines:
+- opal-prd: Increase IPMI timeout to a slightly better value
+ Proactively bump the timeout to 5seconds to match current value in petitboot
+ Observed in the wild that this fixes bugs for petitboot.
+
diff --git a/doc/release-notes/skiboot-5.1.5.txt b/doc/release-notes/skiboot-5.1.5.txt
deleted file mode 100644
index 7b594bf..0000000
--- a/doc/release-notes/skiboot-5.1.5.txt
+++ /dev/null
@@ -1,39 +0,0 @@
-skiboot-5.1.5
--------------
-
-skiboot-5.1.5 was released on October 1st, 2015.
-
-skiboot-5.1.5 is the 6th stable release of 5.1, it follows skiboot-5.1.4
-(which was released September 26th, 2015).
-
-Skiboot 5.1.5 contains all fixes from skiboot-5.1.4 and is a minor bug
-fix release.
-
-Over skiboot-5.1.4, we have the following changes:
-
-Generic:
-- centaur: Add indirect XSCOM support
- Fixes a bug where opal-prd would not be able to recover from a bunch
- of errors as the indirect XSCOMs to centaurs would fail.
-- xscom: Fix logging of indirect XSCOM errors
- Better logging of error messages.
-- PHB3: Fix wrong PE number in error injection
-- Improvement in boot_test.sh utility to support copying a pflash binary
- to BMCs.
-
-AST BMC machines:
-- ipmi-sel: Run power action immediately if host not up
- Our normal sequence for a soft power action (IPMI 'power soft' or
- 'power cycle') involve receiving a SEL from the BMC, sending a message
- to Linux's opal platform support which instructs the host OS to shut
- down, and finally the host will request OPAL to cut power.
-
- When the host is not yet up we will send the message to /dev/null, and
- no action will be taken. This patches changes that behaviour to perform
- the action immediately if we know how.
-
-OpenPower machines:
-- opal-prd: Increase IPMI timeout to a slightly better value
- Proactively bump the timeout to 5seconds to match current value in petitboot
- Observed in the wild that this fixes bugs for petitboot.
-
diff --git a/doc/release-notes/skiboot-5.1.6.rst b/doc/release-notes/skiboot-5.1.6.rst
new file mode 100644
index 0000000..12ad0f9
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.6.rst
@@ -0,0 +1,31 @@
+skiboot-5.1.6
+-------------
+
+skiboot-5.1.6 was released on October 8th, 2015.
+
+skiboot-5.1.6 is the 7th stable release of 5.1, it follows skiboot-5.1.5
+(which was released October 1st, 2015).
+
+Skiboot 5.1.6 contains all fixes from skiboot-5.1.5 and is a minor bug
+fix release.
+
+Over skiboot-5.1.5, we have the following changes:
+
+Generic:
+- Ensure we run pollers in cpu_wait_job()
+
+ In root causing a bug on AST BMC Alistair found that pollers weren't
+ being run for around 3800ms.
+
+ This could show as not resetting the boot count sensor on successful
+ boot.
+
+AST BMC Machines:
+- hw/bt.c: Check for timeout after checking for message response
+
+ When deciding if a BT message has timed out we should first check for
+ a message response. This will ensure that messages will not time out
+ if there was a delay calling the pollers.
+
+ This could show as not resetting the boot count sensor on successful
+ boot.
diff --git a/doc/release-notes/skiboot-5.1.6.txt b/doc/release-notes/skiboot-5.1.6.txt
deleted file mode 100644
index 12ad0f9..0000000
--- a/doc/release-notes/skiboot-5.1.6.txt
+++ /dev/null
@@ -1,31 +0,0 @@
-skiboot-5.1.6
--------------
-
-skiboot-5.1.6 was released on October 8th, 2015.
-
-skiboot-5.1.6 is the 7th stable release of 5.1, it follows skiboot-5.1.5
-(which was released October 1st, 2015).
-
-Skiboot 5.1.6 contains all fixes from skiboot-5.1.5 and is a minor bug
-fix release.
-
-Over skiboot-5.1.5, we have the following changes:
-
-Generic:
-- Ensure we run pollers in cpu_wait_job()
-
- In root causing a bug on AST BMC Alistair found that pollers weren't
- being run for around 3800ms.
-
- This could show as not resetting the boot count sensor on successful
- boot.
-
-AST BMC Machines:
-- hw/bt.c: Check for timeout after checking for message response
-
- When deciding if a BT message has timed out we should first check for
- a message response. This will ensure that messages will not time out
- if there was a delay calling the pollers.
-
- This could show as not resetting the boot count sensor on successful
- boot.
diff --git a/doc/release-notes/skiboot-5.1.7.rst b/doc/release-notes/skiboot-5.1.7.rst
new file mode 100644
index 0000000..29f9ed5
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.7.rst
@@ -0,0 +1,29 @@
+skiboot-5.1.7
+-------------
+
+skiboot-5.1.7 was released on October 13th, 2015.
+
+skiboot-5.1.7 is the 8th stable release of 5.1, it follows skiboot-5.1.6
+(which was released October 8th, 2015).
+
+Skiboot 5.1.7 contains all fixes from skiboot-5.1.6 and is a minor bug
+fix release with one important bug fix for FSP systems.
+
+Over skiboot-5.1.6, we have the following changes:
+
+Generic:
+- PHB3: Retry fundamental reset
+ This introduces another PHB3 state (PHB3_STATE_FRESET_START)
+ allowing to redo fundamental reset if the link doesn't come up
+ in time at the first attempt, to improve the robustness of PHB's
+ fundamental reset. If the link comes up after the first reset,
+ the 2nd reset won't be issued at all.
+
+FSP based systems:
+- hw/fsp/fsp-leds.c: use allocated buffer for FSP_CMD_GET_LED_LIST response
+
+ This fixes a bug where we would overwrite roughly 4kb of memory belonging
+ to Linux when the FSP would ask firmware for a list of LEDs in the system.
+ This wouldn't happen often (once before Linux was running and possibly
+ only once during runtime, and *early* runtime at that) but it was possible
+ for this corruption to show up and be detected.
diff --git a/doc/release-notes/skiboot-5.1.7.txt b/doc/release-notes/skiboot-5.1.7.txt
deleted file mode 100644
index 29f9ed5..0000000
--- a/doc/release-notes/skiboot-5.1.7.txt
+++ /dev/null
@@ -1,29 +0,0 @@
-skiboot-5.1.7
--------------
-
-skiboot-5.1.7 was released on October 13th, 2015.
-
-skiboot-5.1.7 is the 8th stable release of 5.1, it follows skiboot-5.1.6
-(which was released October 8th, 2015).
-
-Skiboot 5.1.7 contains all fixes from skiboot-5.1.6 and is a minor bug
-fix release with one important bug fix for FSP systems.
-
-Over skiboot-5.1.6, we have the following changes:
-
-Generic:
-- PHB3: Retry fundamental reset
- This introduces another PHB3 state (PHB3_STATE_FRESET_START)
- allowing to redo fundamental reset if the link doesn't come up
- in time at the first attempt, to improve the robustness of PHB's
- fundamental reset. If the link comes up after the first reset,
- the 2nd reset won't be issued at all.
-
-FSP based systems:
-- hw/fsp/fsp-leds.c: use allocated buffer for FSP_CMD_GET_LED_LIST response
-
- This fixes a bug where we would overwrite roughly 4kb of memory belonging
- to Linux when the FSP would ask firmware for a list of LEDs in the system.
- This wouldn't happen often (once before Linux was running and possibly
- only once during runtime, and *early* runtime at that) but it was possible
- for this corruption to show up and be detected.
diff --git a/doc/release-notes/skiboot-5.1.8.rst b/doc/release-notes/skiboot-5.1.8.rst
new file mode 100644
index 0000000..c856ba9
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.8.rst
@@ -0,0 +1,20 @@
+skiboot-5.1.8
+-------------
+
+skiboot-5.1.8 was released on October 19th, 2015.
+
+skiboot-5.1.8 is the 9th stable release of 5.1, it follows skiboot-5.1.7
+(which was released October 13th, 2015).
+
+Skiboot 5.1.8 contains all fixes from skiboot-5.1.7 and is a minor bug
+fix release, with a single fix for recovery from a (rare) error.
+
+Over skiboot-5.1.7, we have the following change:
+
+- opal/hmi: Fix a soft lockup issue on Hypervisor Maintenance Interrupt
+ for certain timebase errors.
+
+ We also introduce a timeout to handle the worst situation where all other
+ threads are badly stuck without setting a cleanup done bit. Under such
+ situation timeout will help to avoid soft lockups and report failure to
+ kernel.
diff --git a/doc/release-notes/skiboot-5.1.8.txt b/doc/release-notes/skiboot-5.1.8.txt
deleted file mode 100644
index c856ba9..0000000
--- a/doc/release-notes/skiboot-5.1.8.txt
+++ /dev/null
@@ -1,20 +0,0 @@
-skiboot-5.1.8
--------------
-
-skiboot-5.1.8 was released on October 19th, 2015.
-
-skiboot-5.1.8 is the 9th stable release of 5.1, it follows skiboot-5.1.7
-(which was released October 13th, 2015).
-
-Skiboot 5.1.8 contains all fixes from skiboot-5.1.7 and is a minor bug
-fix release, with a single fix for recovery from a (rare) error.
-
-Over skiboot-5.1.7, we have the following change:
-
-- opal/hmi: Fix a soft lockup issue on Hypervisor Maintenance Interrupt
- for certain timebase errors.
-
- We also introduce a timeout to handle the worst situation where all other
- threads are badly stuck without setting a cleanup done bit. Under such
- situation timeout will help to avoid soft lockups and report failure to
- kernel.
diff --git a/doc/release-notes/skiboot-5.1.9.rst b/doc/release-notes/skiboot-5.1.9.rst
new file mode 100644
index 0000000..f6460ee
--- /dev/null
+++ b/doc/release-notes/skiboot-5.1.9.rst
@@ -0,0 +1,16 @@
+skiboot-5.1.9
+-------------
+
+skiboot-5.1.9 was released on October 30th, 2015.
+
+skiboot-5.1.9 is the 10th stable release of 5.1, it follows skiboot-5.1.8
+(which was released October 19th, 2015).
+
+Skiboot 5.1.9 contains all fixes from skiboot-5.1.8 and is a minor bug
+fix release, with a single fix to help diagnosis after a rare error condition.
+
+Over skiboot-5.1.8, we have the following change:
+- opal/hmi: Signal PRD about NX unit checkstop.
+ We now signal Processor Recovery & Diagnostics (PRD) correctly following
+ an NX unit checkstop
+- minor fix to the boot_test.sh test script
diff --git a/doc/release-notes/skiboot-5.1.9.txt b/doc/release-notes/skiboot-5.1.9.txt
deleted file mode 100644
index f6460ee..0000000
--- a/doc/release-notes/skiboot-5.1.9.txt
+++ /dev/null
@@ -1,16 +0,0 @@
-skiboot-5.1.9
--------------
-
-skiboot-5.1.9 was released on October 30th, 2015.
-
-skiboot-5.1.9 is the 10th stable release of 5.1, it follows skiboot-5.1.8
-(which was released October 19th, 2015).
-
-Skiboot 5.1.9 contains all fixes from skiboot-5.1.8 and is a minor bug
-fix release, with a single fix to help diagnosis after a rare error condition.
-
-Over skiboot-5.1.8, we have the following change:
-- opal/hmi: Signal PRD about NX unit checkstop.
- We now signal Processor Recovery & Diagnostics (PRD) correctly following
- an NX unit checkstop
-- minor fix to the boot_test.sh test script
--
2.7.4
More information about the Skiboot
mailing list