From: Will Deacon <will.deacon@arm.com>
To: Anup Patel <anup.patel@linaro.org>
Cc: "kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
"patches@apm.com" <patches@apm.com>,
Marc Zyngier <Marc.Zyngier@arm.com>,
"penberg@kernel.org" <penberg@kernel.org>,
"christoffer.dall@linaro.org" <christoffer.dall@linaro.org>,
"pranavkumar@linaro.org" <pranavkumar@linaro.org>,
Andre Przywara <Andre.Przywara@arm.com>
Subject: Re: [PATCH v5 3/4] kvmtool: Handle exit reason KVM_EXIT_SYSTEM_EVENT
Date: Fri, 3 Oct 2014 17:16:07 +0100 [thread overview]
Message-ID: <20141003161607.GD32451@arm.com> (raw)
In-Reply-To: <1412159695-28062-4-git-send-email-anup.patel@linaro.org>
On Wed, Oct 01, 2014 at 11:34:54AM +0100, Anup Patel wrote:
> The KVM_EXIT_SYSTEM_EVENT exit reason was added to define
> architecture independent system-wide events for a Guest.
>
> Currently, it is used by in-kernel PSCI-0.2 emulation of
> KVM ARM/ARM64 to inform user space about PSCI SYSTEM_OFF
> or PSCI SYSTEM_RESET request.
>
> For now, we simply treat all system-wide guest events as
> shutdown request in KVMTOOL.
>
> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> Reviewed-by: Andre Przywara <andre.przywara@arm.com>
> ---
> tools/kvm/kvm-cpu.c | 21 +++++++++++++++++++++
> 1 file changed, 21 insertions(+)
>
> diff --git a/tools/kvm/kvm-cpu.c b/tools/kvm/kvm-cpu.c
> index ee0a8ec..5180039 100644
> --- a/tools/kvm/kvm-cpu.c
> +++ b/tools/kvm/kvm-cpu.c
> @@ -160,6 +160,27 @@ int kvm_cpu__start(struct kvm_cpu *cpu)
> goto exit_kvm;
> case KVM_EXIT_SHUTDOWN:
> goto exit_kvm;
> + case KVM_EXIT_SYSTEM_EVENT:
> + /*
> + * Print the type of system event and
> + * treat all system events as shutdown request.
> + */
> + switch (cpu->kvm_run->system_event.type) {
> + case KVM_SYSTEM_EVENT_SHUTDOWN:
> + printf(" # Info: shutdown system event\n");
> + goto exit_kvm;
> + case KVM_SYSTEM_EVENT_RESET:
> + printf(" # Info: reset system event\n");
> + printf(" # Info: KVMTOOL does not support VM reset\n");
> + printf(" # Info: please re-launch the VM manually\n");
Can you use pr_info here instead?
> + goto exit_kvm;
> + default:
> + printf(" # Warning: unknown system event type=%d\n",
> + cpu->kvm_run->system_event.type);
and pr_warning here? (be sure to drop the '\n's).
Will
next prev parent reply other threads:[~2014-10-03 16:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 10:34 [PATCH v5 0/4] kvmtool: ARM/ARM64: Misc updates Anup Patel
2014-10-01 10:34 ` [PATCH v5 1/4] kvmtool: ARM: Use KVM_ARM_PREFERRED_TARGET vm ioctl to determine target cpu Anup Patel
2014-10-01 10:34 ` [PATCH v5 2/4] kvmtool: ARM64: Add target type potenza for aarch64 Anup Patel
2014-10-01 10:34 ` [PATCH v5 3/4] kvmtool: Handle exit reason KVM_EXIT_SYSTEM_EVENT Anup Patel
2014-10-03 16:16 ` Will Deacon [this message]
2014-10-01 10:34 ` [PATCH v5 4/4] kvmtool: ARM/ARM64: Provide PSCI-0.2 to guest when KVM supports it Anup Patel
2014-10-01 12:58 ` [PATCH v5 0/4] kvmtool: ARM/ARM64: Misc updates Andre Przywara
2014-10-03 16:17 ` Will Deacon
2014-10-06 9:15 ` Anup Patel
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=20141003161607.GD32451@arm.com \
--to=will.deacon@arm.com \
--cc=Andre.Przywara@arm.com \
--cc=Marc.Zyngier@arm.com \
--cc=anup.patel@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=patches@apm.com \
--cc=penberg@kernel.org \
--cc=pranavkumar@linaro.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.