Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: Pavel Fedin <p.fedin@samsung.com>,
	'Vijay Kilari' <vijay.kilari@gmail.com>
Cc: kvmarm@lists.cs.columbia.edu
Subject: Re: KVM Live migration with GICv3
Date: Wed, 12 Aug 2015 17:17:25 +0100	[thread overview]
Message-ID: <55CB7195.2070505@arm.com> (raw)
In-Reply-To: <019101d0d449$c6721210$53563630$@samsung.com>

On 11/08/15 16:24, Pavel Fedin wrote:
>  Hello!
> 
>> I mean CPU interface registers GICC* defined for vgicv2 under
>> "vgic_cpu_ranges[]" in
>> virt/kvm/arm/vgic-v2-emul.c needs to be saved and restored for vgicv3 as well.
>> So to  access vgic_cpu_ranges[] for vgicv3, we need to register device
>> for CPU registers space
>> similar to gicv2 in QEMU for gicv3.
> 
> This thing is optional and can be missing. It is for backwards
> compatibility only, it allows to run GICv2 guests on GICv3. You
> should not use this API for accessing system registers.

Even more than that.

The KVM emulation of GICv3 doesn't have *any* GICv2 compatibility. And
that's on purpose. So trying to save the GICC registers should give you
an error, because these registers *do not exist* as far as a guest is
concerned.

If you plan to do anything for GICv3, you should only deal with with the
system register version of the CPU interface.

Thanks,

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

  reply	other threads:[~2015-08-12 16:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  5:25 KVM Live migration with GICv3 Vijay Kilari
2015-08-11  6:41 ` Pavel Fedin
2015-08-11 15:15   ` Vijay Kilari
2015-08-11 15:24     ` Pavel Fedin
2015-08-12 16:17       ` Marc Zyngier [this message]
2015-08-12 16:33         ` Peter Maydell
2015-08-25 11:27     ` Pavel Fedin
2015-08-26 14:24       ` Vijay Kilari
2015-08-12 16:34 ` 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=55CB7195.2070505@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=p.fedin@samsung.com \
    --cc=vijay.kilari@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