From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 3/6] xen: introduce XENPF_settime64
Date: Thu, 12 Nov 2015 20:27:49 +0100 [thread overview]
Message-ID: <9604059.Dn94ENEdgP@wuerfel> (raw)
In-Reply-To: <5644C97F.7070502@oracle.com>
On Thursday 12 November 2015 12:16:47 Boris Ostrovsky wrote:
> >>> diff --git a/arch/x86/xen/time.c b/arch/x86/xen/time.c
> >>> index 663c2ea..3bbd377 100644
> >>> --- a/arch/x86/xen/time.c
> >>> +++ b/arch/x86/xen/time.c
> >>> @@ -134,10 +134,10 @@ static int xen_pvclock_gtod_notify(struct
> >>> notifier_block *nb,
> >>> if (!was_set && timespec_compare(&now, &next_sync) < 0)
> >>> return NOTIFY_OK;
> >>> - op.cmd = XENPF_settime;
> >>> - op.u.settime.secs = now.tv_sec;
> >>> - op.u.settime.nsecs = now.tv_nsec;
> >>> - op.u.settime.system_time = xen_clocksource_read();
> >>> + op.cmd = XENPF_settime32;
> >>> + op.u.settime32.secs = now.tv_sec;
> >>> + op.u.settime32.nsecs = now.tv_nsec;
> >>> + op.u.settime32.system_time = xen_clocksource_read();
> >> Can/should we switch to time64 here? (This would require a couple more changes
> >> but they would all be local to this routine).
> > I can do that, but it should be a separate patch. I'll queue it at the
> > end of the series.
>
> Didn't Arnd just say that something needs to be done in the hypervisor
> for that to work? Or did I misunderstood him?
What I meant is that we need to do both sides in order to actually use
64-bit times, but the patches are otherwise independent of one another
because a change to either side is not allowed to break the other.
Arnd
next prev parent reply other threads:[~2015-11-12 19:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-11 16:49 [PATCH v3 0/6] Xen wallclock on arm and arm64 Stefano Stabellini
2015-11-11 16:51 ` [PATCH v3 1/6] xen: rename dom0_op to platform_op Stefano Stabellini
2015-11-12 15:01 ` Stefano Stabellini
2015-11-12 15:23 ` Boris Ostrovsky
2015-11-11 16:51 ` [PATCH v3 2/6] xen/arm: introduce HYPERVISOR_platform_op on arm and arm64 Stefano Stabellini
2015-11-11 16:51 ` [PATCH v3 3/6] xen: introduce XENPF_settime64 Stefano Stabellini
2015-11-12 15:30 ` Boris Ostrovsky
2015-11-12 16:10 ` Arnd Bergmann
2015-11-12 16:34 ` Stefano Stabellini
2015-11-12 17:16 ` Boris Ostrovsky
2015-11-12 19:27 ` Arnd Bergmann [this message]
2015-11-11 16:51 ` [PATCH v3 4/6] arm: extend pvclock_wall_clock with sec_hi Stefano Stabellini
2015-11-11 16:51 ` [PATCH v3 5/6] xen/arm: introduce xen_read_wallclock Stefano Stabellini
2015-11-11 20:33 ` Arnd Bergmann
2015-11-12 11:28 ` Stefano Stabellini
2015-11-11 16:51 ` [PATCH v3 6/6] xen/arm: set the system time in Xen via the XENPF_settime64 hypercall Stefano Stabellini
2015-11-11 20:35 ` Arnd Bergmann
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=9604059.Dn94ENEdgP@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).