From: Cornelia Huck <cohuck@redhat.com>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: "Laszlo Ersek" <lersek@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v3] qga: fence guest-set-time if hwclock not available
Date: Tue, 10 Dec 2019 18:07:39 +0100 [thread overview]
Message-ID: <20191210180739.273f2117.cohuck@redhat.com> (raw)
In-Reply-To: <20191205115350.18713-1-cohuck@redhat.com>
On Thu, 5 Dec 2019 12:53:50 +0100
Cornelia Huck <cohuck@redhat.com> wrote:
> The Posix implementation of guest-set-time invokes hwclock to
> set/retrieve the time to/from the hardware clock. If hwclock
> is not available, the user is currently informed that "hwclock
> failed to set hardware clock to system time", which is quite
> misleading. This may happen e.g. on s390x, which has a different
> timekeeping concept anyway.
>
> Let's check for the availability of the hwclock command and
> return QERR_UNSUPPORTED for guest-set-time if it is not available.
>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> Reviewed-by: Michael Roth <mdroth@linux.vnet.ibm.com>
> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
> ---
>
> v2->v3:
> - added 'static' keyword to hwclock_path
>
> Not sure what tree this is going through; if there's no better place,
> I can also take this through the s390 tree.
>
> ---
> qga/commands-posix.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
Queued to s390-next.
prev parent reply other threads:[~2019-12-10 17:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 11:53 [PATCH v3] qga: fence guest-set-time if hwclock not available Cornelia Huck
2019-12-05 13:05 ` Philippe Mathieu-Daudé
2019-12-05 13:12 ` Cornelia Huck
2019-12-05 13:20 ` Philippe Mathieu-Daudé
2019-12-05 14:21 ` Michal Privoznik
2019-12-06 7:17 ` Markus Armbruster
2019-12-09 18:33 ` Cornelia Huck
2019-12-10 16:38 ` Philippe Mathieu-Daudé
2019-12-05 15:24 ` Laszlo Ersek
2019-12-06 7:15 ` Markus Armbruster
2019-12-06 9:02 ` Laszlo Ersek
2019-12-10 17:07 ` Cornelia Huck [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=20191210180739.273f2117.cohuck@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@redhat.com \
--cc=lersek@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.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).