From: David Gibson <david@gibson.dropbear.id.au>
To: agraf@suse.de, aik@ozlabs.ru, mdroth@us.ibm.com
Cc: paulus@samba.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/5] pseries: Fix and extend PAPR RTC implementation
Date: Tue, 16 Dec 2014 11:43:43 +1100 [thread overview]
Message-ID: <1418690628-20652-1-git-send-email-david@gibson.dropbear.id.au> (raw)
At the moment, the PAPR RTC implementation (actually a paravirt
firmware interface, rather than a normal device) works directly off
host time, and so doesn't respect the options such as clock=vm which
can be specified in the -rtc command line option.
This patch addresses this also making some other cleanups and small
fixes to the PAPR RTC. I'm confident patches 1..4 are ready to apply,
I'm little less sure about 5. I think it's an improvement over the
current code, but it may still have problems in certain edge cases,
and I've minimally tested it with migration.
next reply other threads:[~2014-12-16 0:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-16 0:43 David Gibson [this message]
2014-12-16 0:43 ` [Qemu-devel] [PATCH 1/5] pseries: Move sPAPR RTC code into its own file David Gibson
2014-12-16 0:59 ` Alexander Graf
2014-12-16 1:24 ` David Gibson
2014-12-16 9:41 ` Alexander Graf
2014-12-18 5:43 ` David Gibson
2014-12-18 23:36 ` Alexander Graf
2014-12-19 5:39 ` David Gibson
2014-12-19 9:59 ` Alexander Graf
2014-12-16 0:43 ` [Qemu-devel] [PATCH 2/5] pseries: Add spapr_rtc_read() helper function David Gibson
2014-12-16 1:01 ` Alexander Graf
2014-12-16 1:25 ` David Gibson
2014-12-16 0:43 ` [Qemu-devel] [PATCH 3/5] pseries: Add more parameter validation in RTAS time of day functions David Gibson
2014-12-16 0:43 ` [Qemu-devel] [PATCH 4/5] pseries: Export /machine "rtc-time" property David Gibson
2014-12-16 1:04 ` Alexander Graf
2014-12-16 2:18 ` David Gibson
2014-12-16 9:42 ` Alexander Graf
2014-12-16 0:43 ` [Qemu-devel] [PATCH 5/5] pseries: Make RTAS time of day functions respect -rtc options David Gibson
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=1418690628-20652-1-git-send-email-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=mdroth@us.ibm.com \
--cc=paulus@samba.org \
--cc=qemu-devel@nongnu.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 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).