linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Vaibhav <vaibhav@linux.vnet.ibm.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: linuxppc-dev@lists.ozlabs.org,
	Neelesh Gupta <neelegup@linux.vnet.ibm.com>
Subject: Re: [RESEND] powerpc/configs: enable RTC class support
Date: Mon, 06 Jul 2015 12:57:47 +0530	[thread overview]
Message-ID: <1436167667.3332.23.camel@localhost.localdomain> (raw)
In-Reply-To: <20150703065901.696F21402AE@ozlabs.org>

On Fri, 2015-07-03 at 16:59 +1000, Michael Ellerman wrote:
> You still haven't told me what happens on a pseries machine when this
is
> applied.

Was finally able to get my hand over a pseries guest lpar today so
dumping the results below. I have aggregated results for each
configuration namely host & guest version; with each with/without the
patch. So in all results for 4 different configurations.

-------------------------
*host-kernel/without patch
-------------------------

Without the patch the hwclock fails with an error message:

[root@tul169p1 ~]# hwclock
hwclock: Timed out waiting for time change.
hwclock: The Hardware Clock registers contain values that are either
invalid (e.g. 50th day of month) or beyond the range we can handle (e.g.
Year 2095).

Debug message of hwclock reveal that hwclock cannot detect any tick in
the RTC clock. This is due to older genrtc driver being used instead of
newer rtc-opal driver.

-------------------------
*host-kernel/with patch
-------------------------

The patch enables the rtc-opal driver by enabling CONFIG_RTC_CLASS. So
the hwclock starts working. Below is the command log:

[root@tul169p1 ~]# hwclock -r
Fri 03 Jul 2015 03:54:31 AM CDT  -0.876949 seconds

--------------------------
*guest-kernel/without patch
---------------------------
Without the patch hwclock still works but uses the legacy generic-rtc.
Below is the output indicating that:

linux-3bot:/ # hwclock -r
Sun Jul  5 21:19:51 2015  -0.885070 seconds

linux-3bot:/ # ls /dev/class/rtc
ls: cannot access /dev/class/rtc: No such file or directory

--------------------------
*guest-kernel/with patch
---------------------------
With the patch, which enables the new rtc_class framework, the legacy
behavior is still used preserved. Below is the output indicating that:
linux-3bot:~ # hwclock -r
Sun Jul  5 21:36:53 2015  -0.704169 seconds

linux-3bot:~ # ls /sys/class/rtc
rtc0

~Vaibhav

  reply	other threads:[~2015-07-06  7:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03  5:11 [RESEND PATCH] powerpc/configs: enable RTC class support Vaibhav Jain
2015-07-03  6:59 ` [RESEND] " Michael Ellerman
2015-07-06  7:27   ` Vaibhav [this message]
2015-08-19 23:14 ` Michael Ellerman

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=1436167667.3332.23.camel@localhost.localdomain \
    --to=vaibhav@linux.vnet.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=neelegup@linux.vnet.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;
as well as URLs for NNTP newsgroup(s).