qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/6] [PULL] qemu-kvm.git uq/master queue
Date: Thu, 04 Mar 2010 09:15:25 -0600	[thread overview]
Message-ID: <4B8FCE8D.4060609@codemonkey.ws> (raw)
In-Reply-To: <cover.1267715116.git.mtosatti@redhat.com>

On 03/04/2010 09:05 AM, Marcelo Tosatti wrote:
> The following changes since commit 55b1e61f640bb2cf3bed0b4cc6d4ba1326c625d9:
>    Samuel Thibault (1):
>          (curses) Use more descriptive values
>
> are available in the git repository at:
>
>    git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>
> Avi Kivity (1):
>        Allocate memory below 4GB as one chunk
>
> Jan Kiszka (4):
>        KVM: Rework of guest debug state writing
>        KVM: Rework VCPU state writeback API
>        KVM: x86: Restrict writeback of VCPU state
>        x86: Extend validity of bsp_to_cpu
>
> Marcelo Tosatti (1):
>        Add option to use file backed guest memory
>    

Pulled.  Thanks.

Regards,

Anthony Liguori

>   cpu-all.h             |    3 +
>   exec.c                |  132 ++++++++++++++++++++++++++++++++++++++++--------
>   hw/apic.c             |    2 -
>   hw/pc.c               |   14 ++----
>   hw/ppc_newworld.c     |    3 -
>   hw/ppc_oldworld.c     |    3 -
>   hw/s390-virtio.c      |    1 -
>   kvm-all.c             |   43 +++++++++++-----
>   kvm.h                 |   26 +++++++++-
>   qemu-options.hx       |   16 ++++++
>   savevm.c              |    4 ++
>   sysemu.h              |    4 ++
>   target-i386/kvm.c     |   77 +++++++++++++++++++++++------
>   target-i386/machine.c |   11 ----
>   target-ppc/kvm.c      |    2 +-
>   target-ppc/machine.c  |    4 --
>   target-s390x/kvm.c    |    3 +-
>   vl.c                  |   41 +++++++++++++++
>   18 files changed, 300 insertions(+), 89 deletions(-)
>
>
>
>    

  parent reply	other threads:[~2010-03-04 15:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04 15:05 [Qemu-devel] [PATCH 0/6] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 1/6] Allocate memory below 4GB as one chunk Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 2/6] Add option to use file backed guest memory Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 3/6] KVM: Rework of guest debug state writing Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 4/6] KVM: Rework VCPU state writeback API Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 5/6] KVM: x86: Restrict writeback of VCPU state Marcelo Tosatti
2010-03-04 15:05 ` [Qemu-devel] [PATCH 6/6] x86: Extend validity of bsp_to_cpu Marcelo Tosatti
2010-03-04 15:15 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-16 22:10 [Qemu-devel] [PATCH 0/6] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2011-04-16 23:57 ` Anthony Liguori
2011-08-05 20:55 Marcelo Tosatti
2011-08-08 20:07 ` Anthony Liguori
2011-10-27 12:10 Marcelo Tosatti
2011-10-31 16:52 ` Anthony Liguori

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=4B8FCE8D.4060609@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=aliguori@us.ibm.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).