qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org,
	Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 0/4] KVM pull request: Various fixes and cleanups
Date: Wed, 03 Feb 2010 15:35:54 -0600	[thread overview]
Message-ID: <4B69EC3A.8090901@codemonkey.ws> (raw)
In-Reply-To: <cover.1265232578.git.jan.kiszka@siemens.com>

Hi Jan,

Thanks for sending this out.

On 02/03/2010 03:29 PM, Jan Kiszka wrote:
> As discussed in http://www.spinics.net/lists/kvm/msg28517.html, this is
> the first part of the KVM upstream patches developed while cleaning up
> qemu-kvm.
>    

I'd prefer if Marcelo/Avi took this first into qemu-kvm.git and then did 
a pull request for me to pull it into upstream qemu.

I'm also happy to pull from multiple sources but I think the former work 
flow will do a better job at ensuring that qemu-kvm.git becomes the 
primary location of this work.

Regards,

Anthony Liguori

> Please pull from
>
> 	git://git.kiszka.org/qemu.git queues/kvm
>
> Jan Kiszka (4):
>    KVM: x86: Fix up misreported CPU features
>    KVM: Make vmport KVM-compatible
>    KVM: Move and rename regs_modified
>    KVM: Rework of guest debug state writing
>
>   cpu-defs.h        |    3 ++-
>   hw/vmport.c       |    3 +++
>   kvm-all.c         |   21 ++++++++-------------
>   target-i386/cpu.h |    9 ++++++++-
>   target-i386/kvm.c |   19 ++++++++++++++++++-
>   5 files changed, 39 insertions(+), 16 deletions(-)
>
>
>
>    

  parent reply	other threads:[~2010-02-03 21:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-03 21:29 [Qemu-devel] [PATCH 0/4] KVM pull request: Various fixes and cleanups Jan Kiszka
2010-02-03 21:29 ` [Qemu-devel] [PATCH 1/4] KVM: x86: Fix up misreported CPU features Jan Kiszka
2010-02-03 21:29 ` [Qemu-devel] [PATCH 2/4] KVM: Make vmport KVM-compatible Jan Kiszka
2010-02-03 21:29 ` [Qemu-devel] [PATCH 3/4] KVM: Move and rename regs_modified Jan Kiszka
2010-02-03 21:29 ` [Qemu-devel] [PATCH 4/4] KVM: Rework of guest debug state writing Jan Kiszka
2010-02-03 23:49   ` [Qemu-devel] " Marcelo Tosatti
2010-02-04  0:33     ` Jan Kiszka
2010-02-04 13:00       ` Marcelo Tosatti
2010-02-04 15:04         ` Jan Kiszka
2010-02-04 15:41           ` Jan Kiszka
2010-02-04 18:05             ` Marcelo Tosatti
2010-02-04 18:53               ` Jan Kiszka
2010-02-04 19:00                 ` Jan Kiszka
2010-02-08 15:52                   ` Marcelo Tosatti
2010-02-08 16:07                     ` Jan Kiszka
2010-02-04 19:21                 ` Jan Kiszka
2010-02-04 20:50                   ` Marcelo Tosatti
2010-02-08 15:52                   ` Marcelo Tosatti
2010-02-03 21:35 ` Anthony Liguori [this message]
2010-02-03 21:54   ` [Qemu-devel] [PATCH 0/4] KVM pull request: Various fixes and cleanups 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=4B69EC3A.8090901@codemonkey.ws \
    --to=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;
as well as URLs for NNTP newsgroup(s).