From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] VGIC early initialization initiated by user-space
Date: Thu, 4 Dec 2014 11:54:52 +0100 [thread overview]
Message-ID: <20141204105452.GB4526@cbox> (raw)
In-Reply-To: <1417686484-20828-1-git-send-email-eric.auger@linaro.org>
On Thu, Dec 04, 2014 at 10:48:00AM +0100, Eric Auger wrote:
> 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 looks overall pretty good to me.
-Christoffer
prev parent reply other threads:[~2014-12-04 10:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 9:48 [PATCH v2 0/4] VGIC early initialization initiated by user-space Eric Auger
2014-12-04 9:48 ` [PATCH v2 1/4] KVM: arm/arm64: vgic: vgic_init_maps returns -ENODEV when no online vcpu Eric Auger
2014-12-04 9:48 ` [PATCH v2 2/4] KVM: arm/arm64: vgic: add init entry to VGIC KVM device Eric Auger
2014-12-04 9:48 ` [PATCH v2 3/4] KVM: arm/arm64: check vgic_initialized before VCPU creation Eric Auger
2014-12-04 9:48 ` [PATCH v2 4/4] KVM: arm/arm64: vgic: check vgic_initialized in KVM_DEV_ARM_VGIC_GRP_ADDR Eric Auger
2014-12-04 10:54 ` Christoffer Dall [this message]
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=20141204105452.GB4526@cbox \
--to=christoffer.dall@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).