[17.10 FEAT] KVM: CPU Model z14

[bugproxy]

Kernel team, could you please consider cherrypicking the below commit into the linux kernel for Artful?

commit b697e435aeee99b7f5b2d8f8dbb51f791be99b16
Author: Jason J. Herne <email address hidden>
Date: Fri Feb 24 10:01:30 2017 -0500

    KVM: s390: Support Configuration z/Architecture Mode

This is related to the following feature:
Enable non transparent hardware functions for KVM guests (crypto CPACF functions)
Commit-ID will follow

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-25 07:23 EDT-------
kernel 4.12

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-26 10:36 EDT-------
Upstream commit IDs:
e000b8e0968dd7bf
b697e435aeee99b7

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-26 12:04 EDT-------
Above were the Linux kernel git commit IDs - here's the ones for QEMU:
ec3aadb13ed601f8
c9ad8a7a53b9f167
6da5c593bb2c27ce
075e52b816648f21
7223bccea3654b6b
cc28a5949bb54df0
c1b364ffd7796ca1

[Dimitri John Ledkov (xnox)]

Upstream commit IDs:
e000b8e0968dd7bf -> in ubuntu, in v4.12

b697e435aeee99b7 -> NOT IN UBUNTU 17.10, it's in v4.14, yet 17.10 is on v4.13. Is this commit required in 17.10 and does it need a matching qemu too? I can check with kernel team, if we can still cherrypick that. But we are past kernel freeze I thought.

[Christian Ehrhardt  (paelzer)]

All in qemu 2.10 which is in artful

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-28 06:31 EDT-------
The patch that went into 4.14 is only required in case we're running a QEMU version without matching z14 support. However, since QEMU 2.10 provides just that, we're safe and can do without that patch.

[Dimitri John Ledkov (xnox)]

Then we defiantly want this patch in artful!

Because linux-hwe kernel will be used as is, on xenial, which may be used with xenial GA qemu v2.5, or any of the cloud-archive backports of qemu - 2.8 and 2.10.

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-09-28 10:22 EDT-------
If you have an older QEMU than 2.10 you cannot choose -cpu z14 so it should not matter.

The last update was not precise. While qemu 2.10 is sufficient, so is 2.5.
Let me explain:

The kernel commit changes the Sigp handling in the kernel. This is only used if the QEMU version is older than 2.3 because since QEMU 2.3 (commit f16d3f58748acff4c23f9149c3261844b4d595d5 s390x/kvm: enable the new SIGP handling in user space) sigp set architecture is handled in QEMU anyway and the kernel part is never executed.

So kernel commit b697e435aeee99b7 is really just a fixup if somebody uses an ancient QEMU and not necessary. for 16.04 or later.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 4.13.0-15.16

---------------
linux (4.13.0-15.16) artful; urgency=low

  * linux: 4.13.0-15.16 -proposed tracker (LP: #1721373)

  * Boot regression on POWER9 (LP: #1721391)
    - Revert "crypto/nx: Add P9 NX support for 842 compression engine"
    - Revert "crypto/nx: Add P9 NX specific error codes for 842 engine"
    - Revert "crypto/nx: Use kzalloc for workmem allocation"
    - Revert "crypto/nx: Add nx842_add_coprocs_list function"
    - Revert "crypto/nx: Create nx842_delete_coprocs function"
    - Revert "crypto/nx: Create nx842_configure_crb function"
    - Revert "crypto/nx: Rename nx842_powernv_function as icswx function"
    - Revert "UBUNTU: [Config] CONFIG_PPC_VAS=y"
    - Revert "powerpc/powernv/vas: Define copy/paste interfaces"
    - Revert "powerpc/powernv/vas: Define vas_tx_win_open()"
    - Revert "powerpc/powernv/vas: Define vas_win_close() interface"
    - Revert "powerpc/powernv/vas: Define vas_rx_win_open() interface"
    - Revert "powerpc/powernv/vas: Define helpers to alloc/free windows"
    - Revert "powerpc/powernv/vas: Define helpers to init window context"
    - Revert "powerpc/powernv/vas: Define helpers to access MMIO regions"
    - Revert "powerpc/powernv/vas: Define vas_init() and vas_exit()"
    - Revert "powerpc/powernv: Move GET_FIELD/SET_FIELD to vas.h"
    - Revert "powerpc/powernv/vas: Define macros, register fields and structures"
    - Revert "powerpc/powernv: Enable PCI peer-to-peer"
    - Revert "powerpc/powernv: Add support to set power-shifting-ratio"
    - Revert "powerpc/powernv: Add support for powercap framework"
    - Revert "powerpc/perf: Add nest IMC PMU support"
    - Revert "powerpc/powernv: Detect and create IMC device"
    - Revert "powerpc/powernv: Add IMC OPAL APIs"

  * smartpqi patches for Artful (LP: #1721381)
    - scsi: smartpqi: add pqi reset quiesce support
    - scsi: smartpqi: enhance BMIC cache flush
    - scsi: smartpqi: update pqi passthru ioctl
    - scsi: smartpqi: cleanup doorbell register usage.
    - scsi: smartpqi: update kexec and power down support
    - scsi: smartpqi: add in new controller ids
    - scsi: smartpqi: change driver version to 1.1.2-125

  * CONFIG_DEBUG_FS is not enabled by "make zfcpdump_defconfig" with Ubuntu
    17.10 (kernel 4.13) (LP: #1719290)
    - SAUCE: s390: update zfcpdump_defconfig

  * [Feature] PXE boot with Intel Omni-Path (LP: #1712031)
    - d-i: Add hfi1 to nic-modules

  * [Feature]CNL:New device IDs for CNL (LP: #1685729)
    - pinctrl: intel: Add Intel Cannon Lake PCH-H pin controller support

linux (4.13.0-14.15) artful; urgency=low

  * linux: 4.13.0-14.15 -proposed tracker (LP: #1721122)

  * [Artful] ltp rwtest - Unable to handle kernel paging request at virtual
    address (LP: #1721067)
    - arm64: mm: Use READ_ONCE when dereferencing pointer to pte table

  * linux 4.13.0-13.14 ADT test failure with linux 4.13.0-13.14 (LP: #1720779)
    - SAUCE: LSM stacking: check for invalid zero sized writes

  * Add installer support for Broadcom BCM573xx network drivers. (LP: #1720466)
    - d-i: Add bnxt_en to nic-modules.

  * Miscellaneous Ubuntu changes
    - [Packaging] Include arch/arm6...

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-11 05:44 EDT-------
IBM Bugzilla Status -> closed; Fix Released within Artful

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-20 07:48 EDT-------
The function needs addl code, which will be provided by kernel 4.14.
Therefore I moved the item to Ubuntu 18.04

[bugproxy (bugproxy)]

------- Comment From <email address hidden> 2017-10-20 07:53 EDT-------
Finalihziing this functionallity will be requested by a new feature reaquest