From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Avi Kivity <avi@redhat.com>, Marcelo Tossati <mtosatti@redhat.com>
Cc: Carsten Otte <cotte@de.ibm.com>, Alexander Graf <agraf@suse.de>,
Jens Freimann <jfrei@linux.vnet.ibm.com>,
Cornelia Huck <cornelia.huck@de.ibm.com>,
Heiko Carstens <heiko.carstens@de.ibm.com>,
Martin Schwidefsky <schwidefsky@de.ibm.com>,
KVM <kvm@vger.kernel.org>
Subject: Re: synchronous register in kvm_run
Date: Mon, 09 Jan 2012 13:37:17 +0100 [thread overview]
Message-ID: <4F0ADF7D.4080209@de.ibm.com> (raw)
In-Reply-To: <1325757285-59875-1-git-send-email-borntraeger@de.ibm.com>
On 05/01/12 10:54, Christian Borntraeger wrote:
> Avi, Marcelo,
>
> here is the latest update of my patch set about guest registers in kvm_run.
> I have added an u64 flag field to make the whole structure extensible
> (and shrinkable).
> For s390 I added the prefix register as read-only and access and general
> purpose as read write.
Any feedback or suggestions on these patches?
next prev parent reply other threads:[~2012-01-09 12:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 9:54 synchronous register in kvm_run Christian Borntraeger
2012-01-05 9:54 ` [PATCH 1/4] kvm: provide synchronous registers " Christian Borntraeger
2012-01-09 13:01 ` Alexander Graf
2012-01-09 13:06 ` Avi Kivity
2012-01-05 9:54 ` [PATCH 2/4] kvm-s390: provide the prefix register via kvm_run Christian Borntraeger
2012-01-09 13:06 ` Alexander Graf
2012-01-05 9:54 ` [PATCH 3/4] kvm-s390: provide general purpose guest registers " Christian Borntraeger
2012-01-09 13:10 ` Alexander Graf
2012-01-05 9:54 ` [PATCH 4/4] kvm-s390: provide access " Christian Borntraeger
2012-01-09 12:37 ` Christian Borntraeger [this message]
2012-01-09 12:49 ` synchronous register in kvm_run Marcelo Tosatti
2012-01-09 12:58 ` 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=4F0ADF7D.4080209@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=agraf@suse.de \
--cc=avi@redhat.com \
--cc=cornelia.huck@de.ibm.com \
--cc=cotte@de.ibm.com \
--cc=heiko.carstens@de.ibm.com \
--cc=jfrei@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=schwidefsky@de.ibm.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;
as well as URLs for NNTP newsgroup(s).