linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Yejune Deng <yejune.deng@gmail.com>
Cc: james.morse@arm.com, julien.thierry.kdev@gmail.com,
	suzuki.poulose@arm.com, catalin.marinas@arm.com, will@kernel.org,
	linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.cs.columbia.edu, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] KVM: arm64: Add big.LITTLE architecture support for vcpu
Date: Fri, 05 Mar 2021 12:02:20 +0000	[thread overview]
Message-ID: <87h7lpzu43.wl-maz@kernel.org> (raw)
In-Reply-To: <20210305103425.73380-1-yejune.deng@gmail.com>

On Fri, 05 Mar 2021 10:34:25 +0000,
Yejune Deng <yejune.deng@gmail.com> wrote:
> 
> In big.LITTLE architecture,the application layer calls KVM_ARM_VCPU_INIT
> several times.Sometimes the thread will run on the big core, sometimes
> will run on the little core.The big core and the little core has always
> different cpuid, but the init target is fixed. and that leads to
> init->target != phys_target. So modify phys target from the current core
> to all cpu online.

This is done on purpose, and it is userspace's responsibility to pin
its vcpu threads to a certain type of CPUs if it cares at all.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2021-03-05 12:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-05 10:34 [PATCH] KVM: arm64: Add big.LITTLE architecture support for vcpu Yejune Deng
2021-03-05 12:02 ` Marc Zyngier [this message]

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=87h7lpzu43.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=julien.thierry.kdev@gmail.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yejune.deng@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).