KVM ARM Archive on lore.kernel.org
 help / color / Atom feed
From: Shaokun Zhang <zhangshaokun@hisilicon.com>
To: Marc Zyngier <maz@kernel.org>
Cc: wangwudi <wangwudi@hisilicon.com>,
	Lizixian <lizixian@hisilicon.com>,
	jiayanlei@huawei.com, fanhenglong@huawei.com,
Subject: Re: [Question about KVM on arm64] Consider putting VINVALL to deactivation
Date: Thu, 16 Jan 2020 14:21:49 +0800
Message-ID: <d41bcfbd-69b1-641b-fc54-9255ac3e82b2@hisilicon.com> (raw)
In-Reply-To: <37126a877e1160ed50ee6d95a03d1574@kernel.org>

Hi Marc,

On 2020/1/15 21:50, Marc Zyngier wrote:
> Hi Shaokun,
> On 2020-01-14 14:20, Shaokun Zhang wrote:
>> Hi Marc,
>> On activation, VMAPP command is followed by a VINVALL, which could be
>> quite expensive for the start-up of virtual machine. If a vpeid is allowed
>> successfully, it is not used in system.
> How expensive? This is exactly similar to what happens on a physical machine
> where we perform an INVALL on MAPC. And yet you don't complain about that.

Agree, I didn't consider this before.

> Please provide numbers.
>> We may consider put VINVALL to deactivation to ensure all cache of certain
>> vpeid is invalid, to simplify activation. We consider start-up may be more
>> common and more time-consuming-sensitive than shutdown process.
> In my world, they cost the same thing, and happen just as often. Also, I want
> guarantees that on VMAPP, there is no stale information even if this is the
> first time we're using this VPEid (who knows what happens over kexec, for
> example).
>> Do you think it's all right?
> I don't, for the reasons stated above. You also provide no numbers showing
> how bad the overhead is, so I'm left guessing.

Got it, you are right :-).

Thanks for your explaination

> Thanks,
>         M.

kvmarm mailing list

      reply index

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 14:20 Shaokun Zhang
2020-01-15 13:50 ` Marc Zyngier
2020-01-16  6:21   ` Shaokun Zhang [this message]

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=d41bcfbd-69b1-641b-fc54-9255ac3e82b2@hisilicon.com \
    --to=zhangshaokun@hisilicon.com \
    --cc=fanhenglong@huawei.com \
    --cc=jiayanlei@huawei.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lizixian@hisilicon.com \
    --cc=maz@kernel.org \
    --cc=wangwudi@hisilicon.com \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

KVM ARM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kvmarm/0 kvmarm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kvmarm kvmarm/ https://lore.kernel.org/kvmarm \
	public-inbox-index kvmarm

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone https://public-inbox.org/public-inbox.git