qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>, Markus Armbruster <armbru@redhat.com>
Cc: "Laszlo Ersek" <lersek@redhat.com>,
	"Daniel P . Berrangé" <berrange@redhat.com>,
	"Michael Roth" <mdroth@linux.vnet.ibm.com>,
	qemu-devel@nongnu.org
Subject: Re: [PATCH v3] qga: fence guest-set-time if hwclock not available
Date: Tue, 10 Dec 2019 17:38:06 +0100	[thread overview]
Message-ID: <ef45f3a1-7683-3b14-1096-ec083b29ea5d@redhat.com> (raw)
In-Reply-To: <20191209193305.7108b3e9.cohuck@redhat.com>

On 12/9/19 7:33 PM, Cornelia Huck wrote:
> On Fri, 06 Dec 2019 08:17:27 +0100
> Markus Armbruster <armbru@redhat.com> wrote:
> 
>> Cornelia Huck <cohuck@redhat.com> writes:
>>
>>> On Thu, 5 Dec 2019 14:05:19 +0100
>>> Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
>>>   
>>>> Hi Cornelia,
>>>>
>>>> On 12/5/19 12:53 PM, Cornelia Huck 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.
>>>>
>>>> s390 or trivial trees seems appropriate.
>>>>    
>>>>>
>>>>> ---
>>>>>    qga/commands-posix.c | 13 ++++++++++++-
>>>>>    1 file changed, 12 insertions(+), 1 deletion(-)
>>>>>
>>>>> diff --git a/qga/commands-posix.c b/qga/commands-posix.c
>>>>> index 1c1a165daed8..0be301a4ea77 100644
>>>>> --- a/qga/commands-posix.c
>>>>> +++ b/qga/commands-posix.c
>>>>> @@ -156,6 +156,17 @@ void qmp_guest_set_time(bool has_time, int64_t time_ns, Error **errp)
>>>>>        pid_t pid;
>>>>>        Error *local_err = NULL;
>>>>>        struct timeval tv;
>>>>> +    static const char hwclock_path[] = "/sbin/hwclock";
>>>>> +    static int hwclock_available = -1;
>>>>> +
>>>>> +    if (hwclock_available < 0) {
>>>>> +        hwclock_available = (access(hwclock_path, X_OK) == 0);
>>>>> +    }
>>>>> +
>>>>> +    if (!hwclock_available) {
>>>>> +        error_setg(errp, QERR_UNSUPPORTED);
>>>>
>>>> In include/qapi/qmp/qerror.h we have:
>>>>
>>>> /*
>>>>    * These macros will go away, please don't use in new code, and do not
>>>>    * add new ones!
>>>>    */
>>>
>>> Sigh, it is really hard to keep track here :( I just copied from other
>>> callers in this file...
>>
>> I'm not faulting you for that.
>>
>> I think this new use is acceptable.  For details, see my other reply in
>> this thread.
> 
> Ok, thanks for your explanation there.
> 
> I guess I'll queue this on s390-next... Philippe, any objections to
> adding your R-b to the unmodified patch?

Certainly, sorry for the delay/noise on this trivial patch, I learned 
the subtle differences between comments in code and reality :)

Reviewed-by: Philippe Mathieu-Daudé <philmd@redhat.com>



  reply	other threads:[~2019-12-10 16:39 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é [this message]
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

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=ef45f3a1-7683-3b14-1096-ec083b29ea5d@redhat.com \
    --to=philmd@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=cohuck@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).