From: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
To: kvm@vger.kernel.org,
Christian Borntraeger <borntraeger@de.ibm.com>,
Alexander Graf <agraf@suse.de>,
aik@ozlabs.ru, Cornelia Huck <cornelia.huck@de.ibm.com>
Subject: Re: [[RFC] KVM-S390: Provide guest TOD Clock Get/Set Controls
Date: Wed, 08 Oct 2014 10:22:25 -0400 [thread overview]
Message-ID: <543548A1.9000905@linux.vnet.ibm.com> (raw)
This is a reply to the following thread:
http://www.spinics.net/lists/kvm/msg108448.html
I'm sending it in this fashion because my normal mail client
is not allowing me to send it in plain text and the html is
getting rejected by the mailing list. Sorry to those of you who
received both this and the original.
Ping. Does anyone feel strongly about this issue? I'm interested in
opinions so we can get s390 TOD clock migration working :).
We need to decide which interface to use, s390 specific ioctl or
KVM_SET_CLOCK.
Then we need to decide if we're going to snap a guest clock forward
on the resume of a "suspend to disk" type operation. The alternative
is to fix up the guest TOD value such that the guest notices no
change of time, which as Christian points out, seems wrong. Unless we
really want to show no time change and force the guest to use ntp to
figure out that he is behind.
--
-- Jason J. Herne (jjherne@linux.vnet.ibm.com)
next reply other threads:[~2014-10-08 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 14:22 Jason J. Herne [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-09-19 14:19 [[RFC] KVM-S390: Provide guest TOD Clock Get/Set Controls Jason J. Herne
2014-09-19 18:51 ` Christian Borntraeger
2014-09-19 20:38 ` Alexander Graf
2014-09-22 9:08 ` Christian Borntraeger
[not found] ` <OFBB97D6FC.48AF23F2-ON87257D6B.004D1813-85257D6B.004DC089@us.ibm.com>
2014-10-08 14:55 ` Alexander Graf
2014-10-09 8:12 ` Christian Borntraeger
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=543548A1.9000905@linux.vnet.ibm.com \
--to=jjherne@linux.vnet.ibm.com \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=kvm@vger.kernel.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.