linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: christoffer.dall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH v2 0/4] arm/arm64: vgic-new: Implement API for vGICv3 live migration
Date: Tue, 16 Aug 2016 19:37:47 +0200	[thread overview]
Message-ID: <20160816173747.GH14088@cbox> (raw)
In-Reply-To: <1470740326-27751-1-git-send-email-vijay.kilari@gmail.com>

Hi Vijaya,

On Tue, Aug 09, 2016 at 04:28:42PM +0530, vijay.kilari at gmail.com wrote:
> From: Vijaya Kumar K <Vijaya.Kumar@cavium.com>
> 
> This patchset adds API for saving and restoring
> of VGICv3 registers to support live migration with new vgic feature.
> This API definition is as per version of VGICv3 specification
> http://lists.infradead.org/pipermail/linux-arm-kernel/2016-July/445611.html
> 
> To test live migration with QEMU, use below patch series
> https://lists.gnu.org/archive/html/qemu-devel/2016-08/msg01444.html
> 
> The patch 3 & 4 are picked from the Pavel's previous implementation.
> http://www.spinics.net/lists/kvm/msg122040.html
> 
> v1 => v2:
>  - The init sequence change patch is no more required.
>    Fixed in patch 2 by using static vgic_io_dev regions structure instead
>    of using dynamic allocation pointer.
>  - Updated commit message of patch 4.
>  - Dropped usage of union to manage 32-bit and 64-bit access in patch 1.
>    Used local variable for 32-bit access.
>  - Updated macro __ARM64_SYS_REG and ARM64_SYS_REG in 
>    arch/arm64/include/uapi/asm/kvm.h as per qemu requirements.
> 
I think you should have enough to go on by now for a new revision.  You
can include the two patches I just sent with the series '[PATCH v2]
Rework vgic_attr_regs_access' in the beginning of your series and then
base your work on that, assuming nobody else screams about this.

If you use that approach, and you address the missing soft pending state
etc. that Peter pointed out, then we should be ready for a detailed
review.

Looking forward to the next version.

Thanks,
-Christoffer

  parent reply	other threads:[~2016-08-16 17:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-09 10:58 [RFC PATCH v2 0/4] arm/arm64: vgic-new: Implement API for vGICv3 live migration vijay.kilari at gmail.com
2016-08-09 10:58 ` [RFC PATCH v2 1/4] arm/arm64: vgic-new: Introduce 64-bit reg access support vijay.kilari at gmail.com
2016-08-16 15:01   ` Christoffer Dall
2016-08-09 10:58 ` [RFC PATCH v2 2/4] arm/arm64: vgic-new: Add distributor and redistributor access vijay.kilari at gmail.com
2016-08-16 15:05   ` Christoffer Dall
2016-08-09 10:58 ` [RFC PATCH v2 3/4] arm/arm64: vgic-new: Introduce find_reg_by_id() vijay.kilari at gmail.com
2016-08-09 10:58 ` [RFC PATCH v2 4/4] arm/arm64: vgic-new: Implement VGICv3 CPU interface access vijay.kilari at gmail.com
2016-08-09 11:52 ` [RFC PATCH v2 0/4] arm/arm64: vgic-new: Implement API for vGICv3 live migration Peter Maydell
2016-08-11  5:29   ` Vijay Kilari
2016-08-11  7:45     ` Peter Maydell
2016-08-12  7:38       ` Vijay Kilari
2016-08-15 21:37         ` Christoffer Dall
2016-08-22  6:15       ` Vijay Kilari
2016-08-16 17:37 ` Christoffer Dall [this message]
2016-08-17 11:55   ` Christoffer Dall

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=20160816173747.GH14088@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).