From: eric.auger@linaro.org (Eric Auger)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/2] VGIC early initialization initiated by user-space
Date: Mon, 15 Dec 2014 18:43:31 +0100 [thread overview]
Message-ID: <1418665413-31521-1-git-send-email-eric.auger@linaro.org> (raw)
Since the advent of VGIC dynamic initialization, this latter is
initialized quite late on the first vcpu run or "on-demand", when
injecting an IRQ or when the guest sets its registers.
This series now allows the user space to explicitly request the VGIC init,
when the dimensioning parameters have been set: number of IRQs, number of
vCPUs. The target state is "initialized".
- the first patch file changes the error returned by vgic_init when no
online vcpu can be found.
- the second adds a new entry to the VGIC KVM device that allows
the user-space 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
Applies on top of Christoffer's series:
"[PATCH v2 0/6] Fix vgic initialization problems"
- can be found at:
http://git.linaro.org/people/eric.auger/linux.git,
branch kvmarm-next-vgic-early-init-v3-official)
v2 -> v3:
- in KVM_DEV_ARM_VGIC_GRP_CTRL: vgic_init is called in place of former
kvm_vgic_init. Means this control moves the VGIC in initialized state
and not in ready state as before.
- "[PATCH v2 3/4] KVM: arm/arm64: check vgic_initialized before VCPU creation"
removed since included in Christoffer's
"arm/arm64: KVM: Don't allow creating VCPUs after vgic_initialized"
- [PATCH v2 4/4] KVM: arm/arm64: vgic: check vgic_initialized in
KVM_DEV_ARM_VGIC_GRP_ADDR removed since I noticed vgic_ioaddr_assign
would return -EEXIST in case vgic_map_resources were already been called.
- rewording in cover letter
v1 -> v2:
- 1, 3, 4 patch files added
- some rewording in vgic device documentation
Eric Auger (2):
KVM: arm/arm64: vgic: vgic_init returns -ENODEV when no online vcpu
KVM: arm/arm64: vgic: add init entry to VGIC KVM device
Documentation/virtual/kvm/devices/arm-vgic.txt | 11 +++++++++++
arch/arm/include/uapi/asm/kvm.h | 2 ++
arch/arm64/include/uapi/asm/kvm.h | 2 ++
virt/kvm/arm/vgic.c | 16 ++++++++++++++--
4 files changed, 29 insertions(+), 2 deletions(-)
--
1.9.1
next reply other threads:[~2014-12-15 17:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:43 Eric Auger [this message]
2014-12-15 17:43 ` [PATCH v3 1/2] KVM: arm/arm64: vgic: vgic_init returns -ENODEV when no online vcpu Eric Auger
2015-01-11 12:40 ` Christoffer Dall
2014-12-15 17:43 ` [PATCH v3 2/2] KVM: arm/arm64: vgic: add init entry to VGIC KVM device Eric Auger
2015-01-11 12:39 ` Christoffer Dall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1418665413-31521-1-git-send-email-eric.auger@linaro.org \
--to=eric.auger@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).