linux-kernel - [PATCH v2 0/4] VGIC early initialization initiated by user-space

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:	Thu,  4 Dec 2014 10:48:00 +0100
From:	Eric Auger <eric.auger@...aro.org>
To:	eric.auger@...com, eric.auger@...aro.org,
	christoffer.dall@...aro.org, marc.zyngier@....com,
	andre.przywara@....com, linux-arm-kernel@...ts.infradead.org,
	kvmarm@...ts.cs.columbia.edu, kvm@...r.kernel.org,
	alex.williamson@...hat.com, agraf@...e.de, gleb@...nel.org,
	pbonzini@...hat.com
Cc:	linux-kernel@...r.kernel.org, patches@...aro.org,
	will.deacon@....com, a.motakis@...tualopensystems.com
Subject: [PATCH v2 0/4] VGIC early initialization initiated by user-space

Since the advent of dynamic initialization of VGIC, this latter is
initialized very late, on the first vcpu run. This initialization
could be initiated much earlier by the user-space, as soon as it has
set the requested dimensioning parameters: number of IRQs, number of
vCPUs, base addresses.

One motivation behind being able to initialize the VGIC sooner is
related to the setup of IRQ injection in VFIO use case. The VFIO
signaling, especially when used along with irqfd must be set *after*
vgic initialization to prevent any virtual IRQ injection before
vgic initialization. If virtual IRQ injection occurs before the VGIC
init, the IRQ cannot be injected and subsequent injection is blocked
due to VFIO completion mechanism (unmask/mask or forward/unforward).

The series includes the following patch files:
[1] changes the error returned by vgic_init_maps when no online vcpu
    can be found
[2] adds a new entry to the VGIC KVM device that allows
    the user to manually request the VGIC init:
    - a new KVM_DEV_ARM_VGIC_GRP_CTRL group is introduced.
    - its first attribute is KVM_DEV_ARM_VGIC_CTRL_INIT
[3] prevents the user-space from creating a new vcpu while the vgic
    already is initialized
[4] prevents the user-space from changing VGIC base addresses if the
    vgic is already initialized

- can be found at:
  http://git.linaro.org/people/eric.auger/linux.git,
  branch 3.18-rc7-vgic-early-init-MLv2

v1 -> v2:
- 1, 3, 4 patch files added
- some rewording in vgic device documentation

Eric Auger (4):
  KVM: arm/arm64: vgic: vgic_init_maps returns -ENODEV when no online
    vcpu
  KVM: arm/arm64: vgic: add init entry to VGIC KVM device
  KVM: arm/arm64: check vgic_initialized before VCPU creation
  KVM: arm/arm64: vgic: check vgic_initialized in
    KVM_DEV_ARM_VGIC_GRP_ADDR

 Documentation/virtual/kvm/devices/arm-vgic.txt | 13 +++++++++++++
 arch/arm/include/uapi/asm/kvm.h                |  2 ++
 arch/arm/kvm/arm.c                             |  5 +++++
 arch/arm64/include/uapi/asm/kvm.h              |  2 ++
 virt/kvm/arm/vgic.c                            | 19 +++++++++++++++++--
 5 files changed, 39 insertions(+), 2 deletions(-)

-- 
1.9.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/