[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH v5 7/7] xen/x86: support XENPF_settime64

To: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
From: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
Date: Fri, 20 Nov 2015 09:35:15 -0500
Cc: Ian.Campbell@xxxxxxxxxx, Arnd Bergmann <arnd@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, david.vrabel@xxxxxxxxxx, linux-arm-kernel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 20 Nov 2015 14:35:50 +0000
List-id: Xen developer discussion <xen-devel.lists.xen.org>

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@xxxxxxxxxx>



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

References:
- [Xen-devel] [PATCH v5 0/7] Xen wallclock on arm and arm64
  - From: Stefano Stabellini
- [Xen-devel] [PATCH v5 7/7] xen/x86: support XENPF_settime64
  - From: Stefano Stabellini

Prev by Date: Re: [Xen-devel] [PATCH v2] minios: don't rely on specific page table allocation scheme
Next by Date: Re: [Xen-devel] [PATCH v3 3/4] xen/hvm: introduce a fpu_uninitialised field to the CPU save record
Previous by thread: [Xen-devel] [PATCH v5 7/7] xen/x86: support XENPF_settime64
Next by thread: [Xen-devel] [PATCH v5 1/7] xen: rename dom0_op to platform_op
Index(es):
- Date
- Thread

Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.