If you download any software from this web site please be aware of the Warranty Disclaimer and Limitation of Liabilities.

Kernel downloads for the "Development stream"

Download Description
upstream kernel 3.2 kernel 3.2 - upstream with feature descriptions.
linux-3.2-s390-message-catalog.tar.gz / MD5 "Development Stream" kernel 3.2 - message-catalog (optional)

2012-02-29: kernel 3.2 - upstream (feature description)

To download the linux-3.2.tar.gz visit: http://www.kernel.org/pub/linux/kernel/v3.x

Since kernel 2.6.35, no more kernel kerntypes-patches (required for work with lcrash, from lkcdutils/LKCD) are provided: Use crash instead of lcrash.

The upstream kernel 3.2 contains the following functionality developed by the Linux on System z development team:

Summary:
kernel: kdump framework for Linux on System z
Description:
The Linux kdump framework is integrated into the already available System z stand-alone dump tools and shutdown actions framework. This leads to the following enhancements for System z kernel-dumps:

Using kdump also requires s390-tools 1.17 and kexec-tools with s390 kdump support.

When running Linux on System z as a VM-guest, the PTFs for APAR VM64960 are required (z/VM 5.4: PTF UM33322; z/VM 6.1: PTF UM33323).

See Using the Dump Tools, Chapter "Using kdump".

Summary:
qdio/qeth: Support for HiperSockets Completion Queue via AF_IUCV
Description:
HiperSockets provide a low-latency high-bandwidth transport mechanism; HiperSockets Completion Queue provides an additional mechanism to manage congestion.

The AF_IUCV socket address family is extended to use HiperSockets as a transport layer making use of the HiperSockets Completion Queue hardware-feature. Note that lsqeth (attribute hsuid) and the af_iucv manpage in s390-toö1.17 reflect this support.

HiperSockets Completion Queue is a new feature of z196 and z114 - see the 2011-07-12 U.S. Hardware Announcement Letters:

This support is available only, when running Linux on System z in an LPAR.

See Device Drivers, Features, and Commands, Chapter "Configuring a HiperSockets device for AF_IUCV addressing".

Summary:
qdio: Support for the FCP hardware data router
Description:
See the description for "zfcp: Support for the FCP hardware data router in z196/z114", below.
Summary:
qdio: Support for end-to-end data consistency checking (T10-DIF and DIX)
Description:
See the description for "zfcp: Support for end-to-end data consistency checking (T10-DIF and DIX), below.
Summary:
zfcp: Support for the FCP hardware data router in z196/z114
Description:
This feature makes use of the hardware data router, that has been added to FICON Express 8S (in z196 and z114) for path length reduction and increased throughput. See the 2011-07-12 U.S. Hardware Announcement Letters:

This support is available only, when running Linux on System z in an LPAR.

See Device Drivers, Features, and Commands, Chapter "Setting up the zfcp device driver".

Summary:
zfcp: Support for end-to-end data consistency checking (T10-DIF and DIX)
Description:
End-to-end data consistency checking is based on a data integrity field (DIF) that is added to transferred data blocks. DIF data is used to confirm that a data block originates from the expected source and has not been modified during the transfer between the storage system and the FCP device. The SCSI standard defines several types of DIF. Data integrity extension (DIX) builds on DIF to extend consistency checking, for example, to the operating system, middleware, or an application.

This functionality requires FCP channels supporting T10-DIF in z196 and z114. See the 2011-07-12 U.S. Hardware Announcement Letters:

This feature can only be used to the full extent with FCP-attached storage providing SCSI disks implementing T10-DIF.

When running Linux on System z as a VM-guest, z/VM 5.4 with PTFs is required.

See Device Drivers, Features, and Commands, Chapter "Confirming end-to-end data consistency checking".

2012-02-29: "Development Stream" kernel 3.2 message catalog (feature - optional patch)

linux-3.2-s390-message-catalog.tar.gz / MD5 ... recommended (2012-02-29)

This patch contains:

Summary:
Kernel message catalog.
Description:
Add support for automatic message tags to the printk macro families dev_xyz and pr_xyz. The message tag consists of a component name and a 24 bit hash of the message text. For each message that is documented in the included kernel message catalog a man page can be created with a script (which is included in the patch). The generated man pages contain explanatory text that is intended to help understand the messages.

Note that only s390 specific messages are prepared appropriately and included in the generated message catalog.

This patch is optional as it is very unlikely to be accepted in upstream kernel, but is recommended for all distributions which are built based on the 'Development stream'.

Contact the IBM team

If you want to contact the Linux on System z IBM team refer to the Contact the Linux on System z IBM team page.