[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type
From: |
Stefan Hajnoczi |
Subject: |
Re: [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type |
Date: |
Wed, 30 May 2018 17:35:52 +0100 |
User-agent: |
Mutt/1.9.5 (2018-04-13) |
On Tue, May 29, 2018 at 01:57:53PM +0800, Peter Xu wrote:
> Instead, use a dynamic function to detect which clock we'll use. The
> problem is that the old code will let monitor initialization depends on
> qtest_enabled(). After this change, we don't have such a dependency any
> more.
There is a hidden dependency:
monitor_get_clock() returns the wrong value before main() has
processed command-line arguments.
Where is the guarantee that monitor_get_clock() is never called too
early?
At the least, monitor_get_clock() should call abort(3) if invoked too
early. Even better would be an interface that cannot be used
incorrectly.
signature.asc
Description: PGP signature
- [Qemu-devel] [PATCH v9 0/7] monitor: let Monitor be thread safe, Peter Xu, 2018/05/29
- [Qemu-devel] [PATCH v9 1/7] monitor: rename out_lock to mon_lock, Peter Xu, 2018/05/29
- [Qemu-devel] [PATCH v9 2/7] monitor: protect mon->fds with mon_lock, Peter Xu, 2018/05/29
- [Qemu-devel] [PATCH v9 3/7] monitor: more comments on lock-free elements, Peter Xu, 2018/05/29
- [Qemu-devel] [PATCH v9 4/7] monitor: fix comment for monitor_lock, Peter Xu, 2018/05/29
- [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type, Peter Xu, 2018/05/29
- Re: [Qemu-devel] [PATCH v9 5/7] monitor: remove event_clock_type,
Stefan Hajnoczi <=
[Qemu-devel] [PATCH v9 6/7] monitor: move init global earlier, Peter Xu, 2018/05/29
[Qemu-devel] [PATCH v9 7/7] monitor: add lock to protect mon_fdsets, Peter Xu, 2018/05/29