All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoffer Dall <cdall@linaro.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"marc.zyngier@arm.com" <marc.zyngier@arm.com>,
	"Andrew Jones" <drjones@redhat.com>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>
Subject: Re: [kvm-unit-tests PATCH v2 2/3] arm/run: ensure we use processor=host for kvm
Date: Fri, 19 May 2017 08:29:11 +0200	[thread overview]
Message-ID: <CAMJs5B_b_NiPv4-8JN0uLsi2zcE2c4tgGL48NebbnTrFUekLZQ@mail.gmail.com> (raw)
In-Reply-To: <461f1654-ed2c-327a-20e0-da59322333d8@redhat.com>

On Thu, May 18, 2017 at 6:03 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>
>
> On 18/05/2017 18:02, Alex Bennée wrote:
>> The configure script will happily default to cortex-a15 even when
>> running on a cortex-a7. This runs into problems when running KVM on
>> common dev boards as we should be using the "host" processor.
>>
>> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> x86 can use different "-cpu" parameters for each test.  Would that make
> sense for ARM?  Can the tests run successfully with cortex-a7 on an A15?
>

For now, we only support same-guest-as-host-cpu configurations with
KVM.  In the future we may add the cross CPU-type support for KVM, and
I suppose we can do this with TCG already.

I would suggest merging this now though, to get kvm-unit-tests working
on the platforms we have available and then add the more complicated
tests when there's an actual need, but it's obviously up to you.

Thanks,
-Christoffer

  reply	other threads:[~2017-05-19  6:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-18 16:02 [kvm-unit-tests PATCH v2 0/3] ARM debug register test Alex Bennée
2017-05-18 16:02 ` [kvm-unit-tests PATCH v2 1/3] sysregs: add __ACCESS_CP14 macro Alex Bennée
2017-05-22 17:27   ` Andrew Jones
2017-05-18 16:02 ` [kvm-unit-tests PATCH v2 2/3] arm/run: ensure we use processor=host for kvm Alex Bennée
2017-05-18 16:03   ` Paolo Bonzini
2017-05-19  6:29     ` Christoffer Dall [this message]
2017-05-19  8:11       ` Paolo Bonzini
2017-05-22 17:25   ` Andrew Jones
2017-05-18 16:02 ` [kvm-unit-tests PATCH v2 3/3] arm/debugtest: test access to the debug registers for guest Alex Bennée
2017-05-22 16:56   ` Radim Krčmář
2017-05-22 18:40     ` Alex Bennée
2017-05-22 17:22   ` Andrew Jones
2017-05-22 18:41     ` Alex Bennée
2017-05-23  9:41       ` Andrew Jones
2017-05-23  9:50         ` Andrew Jones
2017-05-25 15:32 ` [kvm-unit-tests PATCH v2 0/3] ARM debug register test Paolo Bonzini

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=CAMJs5B_b_NiPv4-8JN0uLsi2zcE2c4tgGL48NebbnTrFUekLZQ@mail.gmail.com \
    --to=cdall@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=drjones@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=marc.zyngier@arm.com \
    --cc=pbonzini@redhat.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 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.