Linux KVM/arm64 development list
 help / color / mirror / Atom feed
From: Marc Zyngier <marc.zyngier@arm.com>
To: "Vijay Kilari" <vijay.kilari@gmail.com>,
	kvmarm@lists.cs.columbia.edu,
	"Christoffer Dall" <christoffer.dall@linaro.org>,
	"Alex Bennée" <alex.bennee@linaro.org>,
	p.fedin@samsung.com
Subject: Re: KVM Live migration with GICv3
Date: Wed, 12 Aug 2015 17:34:25 +0100	[thread overview]
Message-ID: <55CB7591.5080408@arm.com> (raw)
In-Reply-To: <CALicx6soU-pqs3XgkEHxtBVy9yR-7irSU4ZJvC3D6V2UmKHQqA@mail.gmail.com>

On 11/08/15 06:25, Vijay Kilari wrote:
> Hi,
> 
>    I have prototyped Live migration with GICv3.
> For this I have made following changes
> 
> 1) Save and Restore of GICv3 registers in QEMU.
>     - For GICv2, QEMU is saving/restoring GICD, GICC  registers. For GICv3,
>      we have to save/restore GICD, GICR and ICC registers.
>      However ICC registers are system registers which cannot be
> accessed @ EL0 level (SRE=1). So these ICC registers should be
> accessed as mmio registers by QEMU, for this we have to add ioctl to
> access ICC @ EL1 level similar to GICC registers of GICv2.

I've already replied to this. The ICC_* registers *must* be exposed as
system registers. There is no GICC_* state to save. And I don't get your
EL0 access thing.

> 
> 2) KVM ioctls in kernel provides only 32-bit register access to GIC
> registers, where
>    as some registers in GICD/GICR requires 64-bit register access. I
> propose to use mmio.flag to specify 32/64 bit access.

I don't believe the MMIO registers *require* 64bit access. The spec says:

"For the GITS_*, GICD_* and GICR_* registers, the upper 32 bits and the
lower 32 bits can be accessed independently, unless the register
requires a 64 bit access."

and as far as I can see, no register mandates a 64bit access.

> 
> 3) KVM ioctls to access ICC registers for GICv3
> 
> Please provide your initial feedback. Let me know if some of this
> issues are already fixed
> 
> I am attending KVM-forum next week @ Seattle. We can discuss there as well.

Feel free to come and talk to us.

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

      parent reply	other threads:[~2015-08-12 16:21 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
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 [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=55CB7591.5080408@arm.com \
    --to=marc.zyngier@arm.com \
    --cc=alex.bennee@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --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