public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sheng Yang <sheng@linux.intel.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	Avi Kivity <avi@redhat.com>,
	Anthony Liguori <anthony@codemonkey.ws>,
	kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3] qemu: kvm: Enable XSAVE live migration support
Date: Thu, 17 Jun 2010 10:01:59 +0800	[thread overview]
Message-ID: <201006171001.59401.sheng@linux.intel.com> (raw)
In-Reply-To: <20100616160544.GA3826@amt.cnet>

On Thursday 17 June 2010 00:05:44 Marcelo Tosatti wrote:
> On Wed, Jun 16, 2010 at 05:48:46PM +0200, Jan Kiszka wrote:
> > Marcelo Tosatti wrote:
> > > On Fri, Jun 11, 2010 at 12:36:49PM +0800, Sheng Yang wrote:
> > >> Signed-off-by: Sheng Yang <sheng@linux.intel.com>
> > >> ---
> > >> 
> > >>  qemu-kvm-x86.c        |  109
> > >>  ++++++++++++++++++++++++++++++++++++++++--------- qemu-kvm.c        
> > >>     |   24 +++++++++++
> > >>  qemu-kvm.h            |   28 +++++++++++++
> > >>  target-i386/cpu.h     |    5 ++
> > >>  target-i386/kvm.c     |    2 +
> > >>  target-i386/machine.c |   20 +++++++++
> > >>  6 files changed, 169 insertions(+), 19 deletions(-)
> > > 
> > > Applied, thanks.
> > 
> > Oops, late remark: Why introducing this feature against qemu-kvm instead
> > of upstream? Doesn't this just generate additional conversion work and
> > the risk of divergence to upstream in the migration protocol?

Hi Jan

You're late... Hope you could raise the comment earlier next time so we can work 
together more efficient.
> 
> Thats true. Sheng, can you add save/restore support to uq/master to
> avoid these problems?

Yes, there is divergence risk, would send an upstream version as well.

But I think as long as qemu-kvm and qemu upstream use different LM path, the 
duplicate code/work can't be avoid. 
 
> Then the cpuid bits can be also merged upstream.

--
regards
Yang, Sheng

  reply	other threads:[~2010-06-17  2:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-11  4:36 [PATCH v3] qemu: kvm: Enable XSAVE live migration support Sheng Yang
2010-06-14 20:39 ` Marcelo Tosatti
2010-06-16 15:48   ` Jan Kiszka
2010-06-16 16:05     ` Marcelo Tosatti
2010-06-17  2:01       ` Sheng Yang [this message]
2010-06-17  7:26         ` Jan Kiszka

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=201006171001.59401.sheng@linux.intel.com \
    --to=sheng@linux.intel.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@redhat.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --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