From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/2] KVM: arm/arm64: vgic: add init entry to VGIC KVM device
Date: Sun, 11 Jan 2015 13:39:54 +0100 [thread overview]
Message-ID: <20150111123954.GW21092@cbox> (raw)
In-Reply-To: <1418665413-31521-3-git-send-email-eric.auger@linaro.org>
On Mon, Dec 15, 2014 at 06:43:33PM +0100, Eric Auger wrote:
> 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 initialization could be initiated explicitly much earlier
> by the users-space, as soon as it has provided the requested
> dimensioning parameters.
>
> This patch 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
>
> The rationale behind introducing a group is to be able to add other
> controls later on, if needed.
>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>
This looks good to me:
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
WARNING: multiple messages have this Message-ID (diff)
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Eric Auger <eric.auger@linaro.org>
Cc: eric.auger@st.com, marc.zyngier@arm.com, andre.przywara@arm.com,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
gleb@kernel.org, pbonzini@redhat.com,
linux-kernel@vger.kernel.org, patches@linaro.org
Subject: Re: [PATCH v3 2/2] KVM: arm/arm64: vgic: add init entry to VGIC KVM device
Date: Sun, 11 Jan 2015 13:39:54 +0100 [thread overview]
Message-ID: <20150111123954.GW21092@cbox> (raw)
In-Reply-To: <1418665413-31521-3-git-send-email-eric.auger@linaro.org>
On Mon, Dec 15, 2014 at 06:43:33PM +0100, Eric Auger wrote:
> 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 initialization could be initiated explicitly much earlier
> by the users-space, as soon as it has provided the requested
> dimensioning parameters.
>
> This patch 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
>
> The rationale behind introducing a group is to be able to add other
> controls later on, if needed.
>
> Signed-off-by: Eric Auger <eric.auger@linaro.org>
>
This looks good to me:
Reviewed-by: Christoffer Dall <christoffer.dall@linaro.org>
next prev parent reply other threads:[~2015-01-11 12:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 17:43 [PATCH v3 0/2] VGIC early initialization initiated by user-space Eric Auger
2014-12-15 17:43 ` Eric Auger
2014-12-15 17:43 ` [PATCH v3 1/2] KVM: arm/arm64: vgic: vgic_init returns -ENODEV when no online vcpu Eric Auger
2014-12-15 17:43 ` Eric Auger
2015-01-11 12:40 ` Christoffer Dall
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
2014-12-15 17:43 ` Eric Auger
2015-01-11 12:39 ` Christoffer Dall [this message]
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=20150111123954.GW21092@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.