Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Avi Kivity <avi@redhat.com>,
	Marcelo Tossati <mtosatti@redhat.com>,
	Carsten Otte <cotte@de.ibm.com>,
	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>,
	Heinz Graalfs <graalfs@linux.vnet.ibm.com>,
	KVM <kvm@vger.kernel.org>, "Jason J. herne" <jjherne@us.ibm.com>
Subject: Re: [PATCH 4/4] kvm-s390: onereg for timer related registers
Date: Tue, 05 Jun 2012 14:57:37 +0200	[thread overview]
Message-ID: <4FCE0241.3000808@de.ibm.com> (raw)
In-Reply-To: <8300B56E-8A7F-4E4C-824C-307B6DC94521@suse.de>

On 05/06/12 14:42, Alexander Graf wrote:
> 
> On 15.05.2012, at 14:15, Christian Borntraeger wrote:
> 
>> From: "Jason J. herne" <jjherne@us.ibm.com>
>>
>> Enhance the KVM ONE_REG capability within S390 to allow
>> getting/setting the following special cpu registers: clock comparator
>> and the cpu timer. These are needed for migration.
>>
>> Signed-off-by: Jason J. herne <jjherne@us.ibm.com>
>> Signed-off-by: Christian Borntraeger <borntraeger@de.ibm.com>
> 
> Any other registers we need to expose to user space while we're at it? :)

I hope not. Life guest relocation prototyping indicates that we have at least
the subset that allows a linux guest to continue.

We might need a way for userspace to influence the output of the store
system information and store facility list instruction. Dont know, maybe
we could use ONEREG even for that purpose. Its on my todo list, but there
are too many other things to tidy up.

Since this would be interface/ABI I dont want to rush without really
understanding what I need for those instruction.

Christian


  reply	other threads:[~2012-06-05 12:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 12:15 [PATCH 0/4] kvm-s390: feature patches Christian Borntraeger
2012-05-15 12:15 ` [PATCH 1/4] kvm-s390: add capability indicating COW support Christian Borntraeger
2012-05-15 12:24   ` Avi Kivity
2012-05-15 12:31     ` Christian Borntraeger
2012-05-15 12:33       ` Avi Kivity
2012-05-15 12:38         ` Christian Borntraeger
2012-05-15 12:40           ` Avi Kivity
2012-06-05 12:36           ` Alexander Graf
2012-05-15 12:15 ` [PATCH 2/4] kvm-s390: KVM_GET/SET_ONEREG for s390 Christian Borntraeger
2012-06-05 12:37   ` Alexander Graf
2012-05-15 12:15 ` [PATCH 3/4] kvm-s390: epoch difference and TOD programmable field Christian Borntraeger
2012-06-05 12:40   ` Alexander Graf
2012-05-15 12:15 ` [PATCH 4/4] kvm-s390: onereg for timer related registers Christian Borntraeger
2012-06-05 12:42   ` Alexander Graf
2012-06-05 12:57     ` Christian Borntraeger [this message]
2012-06-05 13:03       ` Alexander Graf
2012-05-15 12:26 ` [PATCH 0/4] kvm-s390: feature patches Avi Kivity
2012-05-15 12:34   ` Christian Borntraeger
2012-05-18  0:06 ` Marcelo Tosatti

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=4FCE0241.3000808@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=graalfs@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=jfrei@linux.vnet.ibm.com \
    --cc=jjherne@us.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