From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:4830:134:3::10]:46479)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <dgibson@ozlabs.org>) id 1XyvlX-0003WP-DS
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 23:54:21 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <dgibson@ozlabs.org>) id 1XyvlR-0000SZ-9e
	for qemu-devel@nongnu.org; Wed, 10 Dec 2014 23:54:15 -0500
From: David Gibson <david@gibson.dropbear.id.au>
Date: Thu, 11 Dec 2014 15:53:58 +1100
Message-Id: <1418273641-11437-1-git-send-email-david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [RFC PATCH 0/3] pseries: Fix and extend PAPR RTC
	implementation
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: agraf@suse.de, aik@ozlabs.ru, mdroth@us.ibm.com
Cc: qemu-ppc@nongnu.org, paulus@samba.org, qemu-devel@nongnu.org

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 series is a first cut at addressing this.  Caveats:

  * I haven't yet investigated how clock=vm will interact with
    migration.  I suspect badly.

  * We also use a time stamp when delivering RTAS events in
    spapr_events.c.  For now I haven't changed the code here which
    uses host time (via qemu_get_timedate()).  It's not entirely clear
    which clock these timestamps should be linked to.