From: Christoph Hellwig <hch@infradead.org>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org
Subject: Re: [PATCH 09/10] qemu-kvm: Use upstream kvm_cpu_exec
Date: Fri, 20 May 2011 13:17:54 -0400 [thread overview]
Message-ID: <20110520171754.GA20376@infradead.org> (raw)
In-Reply-To: <5a3fe9039c17ca20fdc5538a84283c9d75da28ce.1305911554.git.jan.kiszka@siemens.com>
On Fri, May 20, 2011 at 07:12:39PM +0200, Jan Kiszka wrote:
> Upstream's and qemu-kvm's kvm_cpu_exec are not logically equivalent so
s/not/now/?
next prev parent reply other threads:[~2011-05-20 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 17:12 [PATCH 00/10] qemu-kvm: Cleanup and switch to upstream - Part III Jan Kiszka
2011-05-20 17:12 ` [PATCH 01/10] qemu-kvm: Remove obsolete inclusions Jan Kiszka
2011-05-20 17:12 ` [PATCH 02/10] qemu-kvm: Remove remaining s390 fragments Jan Kiszka
2011-05-20 17:12 ` [PATCH 03/10] qemu-kvm: ppc: Drop diff to upstream Jan Kiszka
2011-05-20 17:12 ` [PATCH 04/10] qemu-kvm: Refactor vm exit in kvm_run Jan Kiszka
2011-05-20 17:12 ` [PATCH 05/10] qemu-kvm: Use thread_kicked instead of KVMCPUState::signalled Jan Kiszka
2011-05-20 17:12 ` [PATCH 06/10] qemu-kvm: Activate iothread version of qemu_cpu_kick_self Jan Kiszka
2011-05-20 17:12 ` [PATCH 07/10] qemu-kvm: Refactor exit_request processing in kvm_run Jan Kiszka
2011-05-20 17:12 ` [PATCH 08/10] qemu-kvm: Use upstream kvm_arch_process_async_events Jan Kiszka
2011-05-20 17:12 ` [PATCH 09/10] qemu-kvm: Use upstream kvm_cpu_exec Jan Kiszka
2011-05-20 17:17 ` Christoph Hellwig [this message]
2011-05-22 10:55 ` Jan Kiszka
2011-05-20 17:12 ` [PATCH 10/10] qemu-kvm: Rework ioport access management Jan Kiszka
2011-05-20 17:14 ` [PATCH 00/10] qemu-kvm: Cleanup and switch to upstream - Part III Alexander Graf
2011-05-20 17:16 ` Jan Kiszka
2011-05-26 8:29 ` Avi Kivity
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=20110520171754.GA20376@infradead.org \
--to=hch@infradead.org \
--cc=avi@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/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