From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
xen-devel@lists.xensource.com
Cc: linux-arm-kernel@lists.infradead.org, Ian.Campbell@citrix.com,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
konrad.wilk@oracle.com, david.vrabel@citrix.com
Subject: Re: [PATCH v5 7/7] xen/x86: support XENPF_settime64
Date: Fri, 20 Nov 2015 09:35:15 -0500 [thread overview]
Message-ID: <564F2FA3.6010603@oracle.com> (raw)
In-Reply-To: <1448029064-22285-7-git-send-email-stefano.stabellini@eu.citrix.com>
On 11/20/2015 09:17 AM, Stefano Stabellini wrote:
> Try XENPF_settime64 first, if it is not available fall back to
> XENPF_settime32.
>
> No need to call __current_kernel_time() when all the info needed are
> already passed via the struct timekeeper * argument.
>
> Return NOTIFY_BAD in case of errors.
Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>
prev parent reply other threads:[~2015-11-20 14:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 14:15 [PATCH v5 0/7] Xen wallclock on arm and arm64 Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 1/7] xen: rename dom0_op to platform_op Stefano Stabellini
2015-11-20 14:23 ` Juergen Gross
2015-11-20 14:17 ` [PATCH v5 2/7] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64 Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 3/7] xen: introduce XENPF_settime64 Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 4/7] arm: extend pvclock_wall_clock with sec_hi Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 5/7] xen/arm: introduce xen_read_wallclock Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 6/7] xen/arm: set the system time in Xen via the XENPF_settime64 hypercall Stefano Stabellini
2015-11-20 14:17 ` [PATCH v5 7/7] xen/x86: support XENPF_settime64 Stefano Stabellini
2015-11-20 14:35 ` Boris Ostrovsky [this message]
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=564F2FA3.6010603@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=Ian.Campbell@citrix.com \
--cc=arnd@arndb.de \
--cc=david.vrabel@citrix.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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).