qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [PATCH 0/9] [PULL] qemu-kvm.git uq/master queue
Date: Mon, 02 May 2011 13:54:21 -0500	[thread overview]
Message-ID: <4DBEFDDD.9010803@us.ibm.com> (raw)
In-Reply-To: <cover.1304361165.git.mtosatti@redhat.com>

On 05/02/2011 01:32 PM, Marcelo Tosatti wrote:
> The following changes since commit cd18f05e248bb916028021634058da06a4657e26:
>
>    Don't zero out buffer in sched_getaffinity (2011-05-02 10:00:01 +0300)

Applied.  Thanks.

Regards,

Anthony Liguori

>
> are available in the git repository at:
>    git://git.kernel.org/pub/scm/virt/kvm/qemu-kvm.git uq/master
>
> Glauber Costa (3):
>        kvm: use kernel-provided para_features instead of statically coming up with new capabilities
>        kvm: add kvmclock to its second bit
>        kvm: create kvmclock when one of the flags are present
>
> Jan Kiszka (4):
>        x86: Allow multiple cpu feature matches of lookup_feature
>        Break up user and system cpu_interrupt implementations
>        Redirect cpu_interrupt to callback handler
>        kvm: Install specialized interrupt handler
>
> Michael Tokarev (1):
>        fix crash in migration, 32-bit userspace on 64-bit host
>
> Paolo Bonzini (1):
>        kvm: use qemu_free consistently
>
>   cpu-all.h           |   14 ++++++++-
>   exec.c              |   18 ++++++++---
>   hw/kvmclock.c       |    6 +++-
>   kvm-all.c           |   30 +++++++++++++++++--
>   target-i386/cpuid.c |   16 ++++++----
>   target-i386/kvm.c   |   80 ++++++++++++++++++++++++++++++++-------------------
>   6 files changed, 117 insertions(+), 47 deletions(-)
>

  parent reply	other threads:[~2011-05-02 18:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-02 18:32 [Qemu-devel] [PATCH 0/9] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 1/9] kvm: use kernel-provided para_features instead of statically coming up with new capabilities Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 2/9] x86: Allow multiple cpu feature matches of lookup_feature Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 3/9] kvm: add kvmclock to its second bit Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 4/9] kvm: create kvmclock when one of the flags are present Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 5/9] Break up user and system cpu_interrupt implementations Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 6/9] Redirect cpu_interrupt to callback handler Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 7/9] kvm: Install specialized interrupt handler Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 8/9] fix crash in migration, 32-bit userspace on 64-bit host Marcelo Tosatti
2011-05-02 18:32 ` [Qemu-devel] [PATCH 9/9] kvm: use qemu_free consistently Marcelo Tosatti
2011-05-02 18:54 ` Anthony Liguori [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-09-11 21:26 [Qemu-devel] [PATCH 0/9] [PULL] qemu-kvm.git uq/master queue Marcelo Tosatti
2012-09-17 18:20 ` 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=4DBEFDDD.9010803@us.ibm.com \
    --to=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).