diff options
author | Angelos Mouzakitis <a.mouzakitis@virtualopensystems.com> | 2023-10-10 14:33:42 +0000 |
---|---|---|
committer | Angelos Mouzakitis <a.mouzakitis@virtualopensystems.com> | 2023-10-10 14:33:42 +0000 |
commit | af1a266670d040d2f4083ff309d732d648afba2a (patch) | |
tree | 2fc46203448ddcc6f81546d379abfaeb323575e9 /roms/skiboot/doc/release-notes/skiboot-5.1.4.rst | |
parent | e02cda008591317b1625707ff8e115a4841aa889 (diff) |
Change-Id: Iaf8d18082d3991dec7c0ebbea540f092188eb4ec
Diffstat (limited to 'roms/skiboot/doc/release-notes/skiboot-5.1.4.rst')
-rw-r--r-- | roms/skiboot/doc/release-notes/skiboot-5.1.4.rst | 34 |
1 files changed, 34 insertions, 0 deletions
diff --git a/roms/skiboot/doc/release-notes/skiboot-5.1.4.rst b/roms/skiboot/doc/release-notes/skiboot-5.1.4.rst new file mode 100644 index 000000000..1d5ec7d04 --- /dev/null +++ b/roms/skiboot/doc/release-notes/skiboot-5.1.4.rst @@ -0,0 +1,34 @@ +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. + +Changes +^^^^^^^ +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 |