All of lore.kernel.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH 5/5] kvmtool: ARM/ARM64: Provide PSCI-0.2 guest when in-kernel KVM supports it
Date: Thu, 7 Aug 2014 10:09:46 +0100	[thread overview]
Message-ID: <20140807090946.GE13703@arm.com> (raw)
In-Reply-To: <CALrVBku8PvYA19vkyNWiGM+GV9thLQnqsH9W2ebMdnoJ4q=V2g@mail.gmail.com>

On Thu, Aug 07, 2014 at 10:00:13AM +0100, Anup Patel wrote:
> On 6 August 2014 18:26, Will Deacon <will.deacon@arm.com> wrote:
> > On Tue, Aug 05, 2014 at 09:49:59AM +0100, Anup Patel wrote:
> >> If in-kernel KVM support PSCI-0.2 emulation then we should set
> >> KVM_ARM_VCPU_PSCI_0_2 feature for each guest VCPU and also
> >> provide "arm,psci-0.2","arm,psci" as PSCI compatible string.
> >>
> >> This patch updates kvm_cpu__arch_init() and setup_fdt() as
> >> per above.
> >>
> >> Signed-off-by: Pranavkumar Sawargaonkar <pranavkumar@linaro.org>
> >> Signed-off-by: Anup Patel <anup.patel@linaro.org>
> >> ---
> >>  tools/kvm/arm/fdt.c     |   39 +++++++++++++++++++++++++++++++++------
> >>  tools/kvm/arm/kvm-cpu.c |    5 +++++
> >>  2 files changed, 38 insertions(+), 6 deletions(-)
> >
> > [...]
> >
> >> diff --git a/tools/kvm/arm/kvm-cpu.c b/tools/kvm/arm/kvm-cpu.c
> >> index 7478f8f..76c28a0 100644
> >> --- a/tools/kvm/arm/kvm-cpu.c
> >> +++ b/tools/kvm/arm/kvm-cpu.c
> >> @@ -74,6 +74,11 @@ struct kvm_cpu *kvm_cpu__arch_init(struct kvm *kvm, unsigned long cpu_id)
> >>               die("preferred target not available\n");
> >>       }
> >>
> >> +     /* Set KVM_ARM_VCPU_PSCI_0_2 if available */
> >> +     if (kvm__supports_extension(kvm, KVM_CAP_ARM_PSCI_0_2)) {
> >> +             vcpu_init.features[0] |= (1UL << KVM_ARM_VCPU_PSCI_0_2);
> >> +     }
> >
> > Where is this used?
> 
> If we want to provide PSCI-0.2 to Guest then we should inform
> in-kernel KVM ARM/ARM64 using init features.
> 
> By default KVM ARM/ARM64 provides PSCI-0.1 to Guest. If we don't set
> this feature then Guest will get undefined exception for PSCI-0.2
> calls.

Gotcha, thanks for the explanation.

Will

  reply	other threads:[~2014-08-07  9:09 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  8:49 [PATCH 0/5] kvmtool: ARM/ARM64: Misc updates Anup Patel
2014-08-05  8:49 ` [PATCH 1/5] kvmtool: ARM: Use KVM_ARM_PREFERRED_TARGET vm ioctl to determine target cpu Anup Patel
2014-08-06 12:48   ` Will Deacon
2014-08-07  8:44     ` Anup Patel
2014-08-07  8:52       ` Peter Maydell
2014-08-05  8:49 ` [PATCH 2/5] kvmtool: ARM64: Fix compile error for aarch64 Anup Patel
2014-08-06 12:50   ` Will Deacon
2014-08-07  8:50     ` Anup Patel
2014-08-07  9:12       ` Will Deacon
2014-08-28  9:56         ` Pekka Enberg
2014-08-28 10:03           ` Will Deacon
2014-08-05  8:49 ` [PATCH 3/5] kvmtool: ARM64: Add target type potenza " Anup Patel
2014-08-06 12:52   ` Will Deacon
2014-08-07  8:56     ` Anup Patel
2014-08-07  9:01       ` Will Deacon
2014-08-05  8:49 ` [PATCH 4/5] kvmtool: Handle exit reason KVM_EXIT_SYSTEM_EVENT Anup Patel
2014-08-06 12:53   ` Will Deacon
2014-08-07  8:57     ` Anup Patel
2014-08-05  8:49 ` [PATCH 5/5] kvmtool: ARM/ARM64: Provide PSCI-0.2 guest when in-kernel KVM supports it Anup Patel
2014-08-06 12:56   ` Will Deacon
2014-08-07  9:00     ` Anup Patel
2014-08-07  9:09       ` Will Deacon [this message]
2014-08-05  8:53 ` [PATCH 0/5] kvmtool: ARM/ARM64: Misc updates 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=20140807090946.GE13703@arm.com \
    --to=will.deacon@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.