All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Peng Fan <van.freenix@gmail.com>,
	andre.przywara@arm.com, christoffer.dall@linaro.org
Cc: kvm@vger.kernel.org
Subject: Re: Question about KVM on Big.Little SoC
Date: Tue, 6 Sep 2016 09:12:26 +0100	[thread overview]
Message-ID: <57CE7A6A.1010508@arm.com> (raw)
In-Reply-To: <20160906080005.GB5493@linux-7smt.suse>

Peng,

On 06/09/16 09:00, Peng Fan wrote:
> Hi Andre,
> 
> I came across your patch which try to fix kvm on big.little.
> https://lists.cs.columbia.edu/pipermail/kvmarm/2013-April/003989.html
> 
> I am trying KVM on a big.little SoC with 4 A53 and 2 A72.
> I wonder whether kvm supports running on big.little SoC now?
> 
> I am checking arch/{arm,arm64}/kvm code, but I think you may give a quick answer.
> 
> And If kvm supports running on big.Little SoC, is it ok for me to pass "-cpu host"
> to qemu? Can guest vcpu be scheduled freely on big and little SoCs?
> 
> Would you please kindly give me some clues about where is the piece code to handle
> kvm on big.little?

The current situation is that:

- Yes, KVM works on big-little systems (it always had)
- The only useful option you can pass to qemu is "-cpu host"
- There is no guarantee that QEMU will even start, unless you constraint
its affinity to one single type of CPUs (use taskset).
- If you use taskset, there will be no scheduling between types of cores
- If you do not, scheduling will happen, but that's a fairly unsafe
thing to do (the guest doesn't know it is being migrated between CPUs
that may have different behaviours...).

Hope this helps,

	M.
-- 
Jazz is not dead. It just smells funny...

  reply	other threads:[~2016-09-06  8:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-06  8:00 Question about KVM on Big.Little SoC Peng Fan
2016-09-06  8:12 ` Marc Zyngier [this message]
2016-09-08  1:46   ` Peng Fan

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=57CE7A6A.1010508@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=kvm@vger.kernel.org \
    --cc=van.freenix@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 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.