From: Avi Kivity <avi@redhat.com>
To: Carsten Otte <carsteno@de.ibm.com>
Cc: Alexander Graf <agraf@suse.de>,
qemu-devel <qemu-devel@nongnu.org>,
uli@suse.de, Carsten Otte <cotte@de.ibm.com>,
hare@suse.de, KVM list <kvm@vger.kernel.org>
Subject: Re: [PATCH 0/9] S390x KVM support
Date: Thu, 22 Oct 2009 12:29:57 +0200 [thread overview]
Message-ID: <4AE03425.30603@redhat.com> (raw)
In-Reply-To: <4AE031D0.50002@de.ibm.com>
On 10/22/2009 12:20 PM, Carsten Otte wrote:
> Avi Kivity wrote:
>> gdb is hardly performance critical. Is that the only reason for the
>> change?
> Right, gdb is not performance critical. gdb is the reason for moving
> it out of the union, performance is the reason for having it in
> kvm_run at all.
> There's only more reason to it: with a little tweaking in kuli, we'll
> be able to get rid of KVM_S390_SET_INITIAL_PSW ioctl with this change.
> That removes one oddity that makes us different from other platforms.
In fact qemu/x86 does a KVM_SET_SREGS (which updates pc) on reset.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2009-10-22 10:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1255963059-10298-1-git-send-email-agraf@suse.de>
[not found] ` <4ADDE7E3.9090601@de.ibm.com>
2009-10-22 9:08 ` [PATCH 0/9] S390x KVM support Avi Kivity
2009-10-22 9:11 ` Alexander Graf
2009-10-22 9:53 ` Avi Kivity
2009-10-22 9:55 ` Alexander Graf
2009-10-22 9:58 ` Alexander Graf
2009-10-22 10:03 ` Avi Kivity
2009-10-22 10:13 ` Alexander Graf
2009-10-22 10:22 ` Carsten Otte
2009-10-22 10:28 ` Avi Kivity
2009-10-22 10:43 ` Carsten Otte
2009-10-22 10:49 ` Avi Kivity
2009-10-22 11:10 ` Carsten Otte
2009-11-02 20:23 ` Alexander Graf
2009-11-03 8:55 ` Avi Kivity
2009-10-22 9:18 ` Carsten Otte
2009-10-22 10:02 ` Avi Kivity
2009-10-22 10:20 ` Carsten Otte
2009-10-22 10:29 ` Avi Kivity [this message]
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=4AE03425.30603@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=carsteno@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=hare@suse.de \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.org \
--cc=uli@suse.de \
/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