All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: [PATCH 0/6] [uq/master] More KVM upstream cleanups, fixes, enhancements
Date: Wed, 29 Dec 2010 20:09:51 +0100	[thread overview]
Message-ID: <cover.1293649792.git.jan.kiszka@web.de> (raw)

Nothing critical, see patches for details.

Jan Kiszka (6):
  kvm: Fix coding style violations
  kvm: Drop return value of kvm_cpu_exec
  kvm: x86: Align kvm_arch_put_registers code with comment
  kvm: Stop on all fatal exit reasons
  kvm: Improve reporting of fatal errors
  kvm: x86: Prepare kvm_get_mp_state for in-kernel irqchip

 kvm-all.c           |  171 ++++++++++++++++++++++++++++-----------------------
 kvm-stub.c          |    4 +-
 kvm.h               |    2 +-
 target-i386/cpu.h   |    2 +
 target-i386/cpuid.c |    5 +-
 target-i386/kvm.c   |   46 +++++++++++++-
 target-ppc/kvm.c    |    4 +
 7 files changed, 148 insertions(+), 86 deletions(-)


WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@web.de>
To: Avi Kivity <avi@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [PATCH 0/6] [uq/master] More KVM upstream cleanups, fixes, enhancements
Date: Wed, 29 Dec 2010 20:09:51 +0100	[thread overview]
Message-ID: <cover.1293649792.git.jan.kiszka@web.de> (raw)

Nothing critical, see patches for details.

Jan Kiszka (6):
  kvm: Fix coding style violations
  kvm: Drop return value of kvm_cpu_exec
  kvm: x86: Align kvm_arch_put_registers code with comment
  kvm: Stop on all fatal exit reasons
  kvm: Improve reporting of fatal errors
  kvm: x86: Prepare kvm_get_mp_state for in-kernel irqchip

 kvm-all.c           |  171 ++++++++++++++++++++++++++++-----------------------
 kvm-stub.c          |    4 +-
 kvm.h               |    2 +-
 target-i386/cpu.h   |    2 +
 target-i386/cpuid.c |    5 +-
 target-i386/kvm.c   |   46 +++++++++++++-
 target-ppc/kvm.c    |    4 +
 7 files changed, 148 insertions(+), 86 deletions(-)

             reply	other threads:[~2010-12-29 19:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29 19:09 Jan Kiszka [this message]
2010-12-29 19:09 ` [Qemu-devel] [PATCH 0/6] [uq/master] More KVM upstream cleanups, fixes, enhancements Jan Kiszka
2010-12-29 19:09 ` [PATCH 1/6] kvm: Fix coding style violations Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " Jan Kiszka
2010-12-29 19:09 ` [PATCH 2/6] kvm: Drop return value of kvm_cpu_exec Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " Jan Kiszka
2010-12-29 19:09 ` [PATCH 3/6] kvm: x86: Align kvm_arch_put_registers code with comment Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " Jan Kiszka
2010-12-29 19:09 ` [PATCH 4/6] kvm: Stop on all fatal exit reasons Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " Jan Kiszka
2010-12-29 19:09 ` [PATCH 5/6] kvm: Improve reporting of fatal errors Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " Jan Kiszka
2010-12-29 19:09 ` [PATCH 6/6] kvm: x86: Prepare kvm_get_mp_state for in-kernel irqchip Jan Kiszka
2010-12-29 19:09   ` [Qemu-devel] " 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=cover.1293649792.git.jan.kiszka@web.de \
    --to=jan.kiszka@web.de \
    --cc=avi@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.