linux-kernel - [PATCH v1 RFC 00/10] QEMU: s390: cpu model implementation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 13 May 2014 17:00:12 +0200
From:	Michael Mueller <mimu@...ux.vnet.ibm.com>
To:	qemu-devel@...gnu.org, kvm@...r.kernel.org,
	linux-s390@...r.kernel.org, linux-kernel@...r.kernel.org
Cc:	Cornelia Huck <cornelia.huck@...ibm.com>,
	Christian Borntraeger <borntraeger@...ibm.com>,
	Alexander Graf <agraf@...e.de>, Gleb Natapov <gleb@...nel.org>,
	Paolo Bonzini <pbonzini@...hat.com>,
	Richard Henderson <rth@...ddle.net>,
	Andreas Faerber <afaerber@...e.de>,
	"Jason J. Herne" <jjherne@...ux.vnet.ibm.com>,
	mimu@...ux.vnet.ibm.com
Subject: [PATCH v1 RFC 00/10] QEMU: s390: cpu model implementation

This patch set in combination with its kernel kvm patch set proposes an
implementation of S390 cpu models. The origin of this item is to provide
a means for management interfaces like libvirt to draw decisions if life
guest migration to a target hypervisor is reasonable.

A migration constraint is that a target hypervisor is capable to run a
guest with the same S390 cpu model as the source hypervisor does. To
verify this condition, the administration interface employes the existing
QMP command "query-cpu-definitions" which returns a list of all currently
supported S390 cpu models of a given host system. Together with the newly
defined QMP command "query-cpu-model", which returns the current active
S390 cpu model of a guest, a conclusion can be drawn if a migration is
possible.

A S390 cpu model is defined as a triple of machine type, cpu facility set
and IBC value. Each historic, current and future triple receives a name
composed of the machine type and its general availability counter. This name
forms the cpu model name (e.g.: "2817-GA2".)

With means of the Instruction Blocking Control feature (IBC), the instruction
set available to a given guest is limitable.

Michael Mueller (10):
  QEMU: introduce function cpudesc_avail
  QEMU: s390: cpu model cpu class definition
  QEMU: s390: cpu model facilities support
  QEMU: s390: cpu model alias support
  s390: update linux-headers for kvm VM device attributes
  QEMU: s390: cpu model kvm VM attr interface routines
  QEMU: s390: cpu model class initialization
  QEMU: s390: cpu model QMP query-cpu-definitions
  QEMU: s390: cpu model QMP query-cpu-model
  QEMU: s390: cpu model enablement

 arch_init.c                  |   8 +
 hw/s390x/s390-virtio-ccw.c   |   2 +
 hw/s390x/s390-virtio.c       | 104 ++++++++
 hw/s390x/s390-virtio.h       |   1 +
 include/sysemu/arch_init.h   |   2 +
 linux-headers/asm-s390/kvm.h |  26 ++
 linux-headers/linux/kvm.h    |   1 +
 qapi-schema.json             |  23 ++
 qmp-commands.hx              |   6 +
 qmp.c                        |   5 +
 stubs/Makefile.objs          |   1 +
 stubs/arch-query-cpu-mod.c   |   9 +
 target-s390x/Makefile.objs   |   1 +
 target-s390x/cpu-models.c    | 586 +++++++++++++++++++++++++++++++++++++++++++
 target-s390x/cpu-models.h    | 362 ++++++++++++++++++++++++++
 target-s390x/cpu-qom.h       |  22 ++
 target-s390x/cpu.c           | 171 ++++++++++++-
 target-s390x/cpu.h           |   3 +
 target-s390x/kvm.c           |  66 +++++
 vl.c                         |   2 +-
 20 files changed, 1395 insertions(+), 6 deletions(-)
 create mode 100644 stubs/arch-query-cpu-mod.c
 create mode 100644 target-s390x/cpu-models.c
 create mode 100644 target-s390x/cpu-models.h

-- 
1.8.3.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/