[PATCH 0/17][REVIEW] Backport candidates for stable-0.10

From: Anthony Liguori <aliguori@us.ibm.com>
To: kvm@vger.kernel.org
Cc: Glauber Costa <glommer@gmail.com>, Avi Kivity <avi@redhat.com>
Subject: [PATCH 0/17][REVIEW] Backport candidates for stable-0.10
Date: Sun, 17 May 2009 10:43:01 -0500	[thread overview]
Message-ID: <1242574999-20887-1-git-send-email-aliguori@us.ibm.com> (raw)

This is a set of patches from master that I think are candidates for the
stable-0.10 branch.   They're all KVM specific.

I tried to be conservative and didn't include any ia64, PPC, or passthrough
fixes.  I don't know the state of those subsystems well enough to judge whether
the commits help or not.

To detect set of candidates to consider, I used the following git command:

 git log ^kvm-stable-start origin/master..kvm

This gives a range of commits that do not include anything reachable from
kvm-stable-start or origin/master (which is upstream QEMU) starting at the
master branch in kvm.

kvm-stable-start is a local tag to:

  commit 8d890e234cdf5860395c4cb93b831ae37aab41e9
  Author: Zhang, Yang <yang.zhang@intel.com>
  Date:   Thu Mar 5 15:10:22 2009 +0800

      kvm: external module: add kvm-ia64.c to hack files list

As best I can tell, the is the point where KVM's stable branch forked from the
master branch.  If anyone knows a better way to figure this out in git, please
let me know.

I've done some regression testing.  It looks like savevm/loadvm is broken in
stable-0.10 right now (KVM only) so that limits the testing I can do there.

One of the patches required enough fuzzing that I'd like to get an Ack on it.
I've marked it appropriately.