From: Christoffer Dall <christoffer.dall@linaro.org>
To: Ulrich Hecht <ulrich.hecht@gmail.com>
Cc: kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-sh@vger.kernel.org, magnus.damm@gmail.com, gleb@redhat.com,
horms@verge.net.au
Subject: Re: [PATCH resend] KVM: ARM: enable Cortex A7 hosts
Date: Thu, 26 Sep 2013 14:41:41 +0000 [thread overview]
Message-ID: <20130926144041.GA1389@cbox> (raw)
In-Reply-To: <1380196131-23326-1-git-send-email-ulrich.hecht@gmail.com>
On Thu, Sep 26, 2013 at 01:48:51PM +0200, Ulrich Hecht wrote:
> KVM runs fine on Cortex A7 cores, so they should be enabled. Tested on an
> APE6EVM board (r8a73a4 SoC).
>
> Signed-off-by: Ulrich Hecht <ulrich.hecht@gmail.com>
> ---
> arch/arm/kvm/guest.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/arch/arm/kvm/guest.c b/arch/arm/kvm/guest.c
> index 152d036..05c62d5 100644
> --- a/arch/arm/kvm/guest.c
> +++ b/arch/arm/kvm/guest.c
> @@ -192,6 +192,8 @@ int __attribute_const__ kvm_target_cpu(void)
> switch (part_number) {
> case ARM_CPU_PART_CORTEX_A15:
> return KVM_ARM_TARGET_CORTEX_A15;
> + case ARM_CPU_PART_CORTEX_A7:
> + return KVM_ARM_TARGET_CORTEX_A15;
> default:
> return -EINVAL;
> }
> --
> 1.8.3.1
>
nack
we need to have support and implementation for A7 cores and not try to
shoehorn A7 support by pretending that it's an A15.
The fact that you have tested this and it happens to work with the
workload you ran does not mean it is the right solution. At the very
least, you need to document and think about the different system
register implementation and deal with them correctly.
-Christoffer
next prev parent reply other threads:[~2013-09-26 14:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 11:48 [PATCH resend] KVM: ARM: enable Cortex A7 hosts Ulrich Hecht
2013-09-26 14:41 ` Christoffer Dall [this message]
2013-09-26 15:07 ` Marc Zyngier
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=20130926144041.GA1389@cbox \
--to=christoffer.dall@linaro.org \
--cc=gleb@redhat.com \
--cc=horms@verge.net.au \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=ulrich.hecht@gmail.com \
/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).