qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Christoffer Dall <christoffer.dall@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Patch Tracking <patches@linaro.org>,
	QEMU Developers <qemu-devel@nongnu.org>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>
Subject: Re: [Qemu-devel] [RFC PATCH v4 0/8] Support arm-gic-kvm save/restore
Date: Mon, 6 Jan 2014 07:29:21 -0800	[thread overview]
Message-ID: <20140106152921.GA27179@cbox> (raw)
In-Reply-To: <CAFEAcA9eiKNW+9PrG-5AM+a-pfNhGJ0o3hRQ8nd89PWTEUa1YA@mail.gmail.com>

On Mon, Jan 06, 2014 at 11:09:28AM +0000, Peter Maydell wrote:
> On 21 December 2013 06:09, Christoffer Dall <christoffer.dall@linaro.org> wrote:
> > Implement support to save/restore the ARM KVM VGIC state from the
> > kernel.  The basic appraoch is to transfer state from the in-kernel VGIC
> > to the emulated arm-gic state representation and let the standard QEMU
> > vmstate save/restore handle saving the arm-gic state.  Restore works by
> > reversing the process.
> >
> > The first patches adds missing features and fixes issues with the
> > arm-gic implementation in qemu in preparation for the actual
> > save/restore logic.
> 
> I still need to review this series, but I'm going to take the
> first two patches into target-arm.next now since they're already
> reviewed and they're straightforward cleanup.
> 
ok, no worries about the review.  The kernel series went into Marcelo's
queue over the holiday, so I expect it to appear in kvm.next any time
soon.

-Christoffer

      reply	other threads:[~2014-01-06 15:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-21  6:09 [Qemu-devel] [RFC PATCH v4 0/8] Support arm-gic-kvm save/restore Christoffer Dall
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 1/8] arm_gic: Rename GIC_X_TRIGGER to GIC_X_EDGE_TRIGGER Christoffer Dall
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 2/8] hw: arm_gic: Introduce gic_set_priority function Christoffer Dall
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 3/8] arm_gic: Fix GIC pending behavior Christoffer Dall
2014-01-19 19:49   ` Peter Maydell
2014-01-28  2:09     ` Christoffer Dall
2014-01-28  9:01       ` Peter Maydell
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 4/8] hw: arm_gic: Keep track of SGI sources Christoffer Dall
2014-01-19 20:44   ` Peter Maydell
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 5/8] arm_gic: Support setting/getting binary point reg Christoffer Dall
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 6/8] vmstate: Add uint32 2D-array support Christoffer Dall
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 7/8] arm_gic: Add GICC_APRn state to the GICState Christoffer Dall
2014-01-19 20:20   ` Peter Maydell
2013-12-21  6:09 ` [Qemu-devel] [RFC PATCH v4 8/8] hw: arm_gic_kvm: Add KVM VGIC save/restore logic Christoffer Dall
2014-01-06 11:09 ` [Qemu-devel] [RFC PATCH v4 0/8] Support arm-gic-kvm save/restore Peter Maydell
2014-01-06 15:29   ` Christoffer Dall [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=20140106152921.GA27179@cbox \
    --to=christoffer.dall@linaro.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).