From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52598) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0gFA-0000sH-Gd for qemu-devel@nongnu.org; Mon, 15 Dec 2014 19:44:10 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Y0gF2-0006Lw-57 for qemu-devel@nongnu.org; Mon, 15 Dec 2014 19:44:04 -0500 Received: from ozlabs.org ([103.22.144.67]:48206) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Y0gF1-0006LF-Rd for qemu-devel@nongnu.org; Mon, 15 Dec 2014 19:43:56 -0500 From: David Gibson Date: Tue, 16 Dec 2014 11:43:43 +1100 Message-Id: <1418690628-20652-1-git-send-email-david@gibson.dropbear.id.au> Subject: [Qemu-devel] [PATCH 0/5] pseries: Fix and extend PAPR RTC implementation List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: agraf@suse.de, aik@ozlabs.ru, mdroth@us.ibm.com Cc: 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 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.