Received: from eggs.gnu.org ([208.118.235.92]:49322) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULpFL-00010z-RF for qemu-devel@nongnu.org; Sat, 30 Mar 2013 02:26:38 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ULpFK-00064d-QZ for qemu-devel@nongnu.org; Sat, 30 Mar 2013 02:26:35 -0400 Received: from speedy.comstyle.com ([206.51.28.2]:23070 helo=mail.comstyle.com) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ULpFK-000639-KP for qemu-devel@nongnu.org; Sat, 30 Mar 2013 02:26:34 -0400 Received: from rox.home.comstyle.com (unknown [IPv6:2001:470:b01e:3:303a:106b:ecf3:e375]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: brad) by mail.comstyle.com (Postfix) with ESMTPSA id 676A03DEB3 for ; Sat, 30 Mar 2013 02:25:28 -0400 (EDT) Date: Sat, 30 Mar 2013 02:25:25 -0400 From: Brad Smith Message-ID: <20130330062517.GG31912@rox.home.comstyle.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] [PATCH] Use clock_gettime() on OpenBSD List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org init_get_clock() already indicates to get_clock() to utilize clock_gettime() with a monotonic clock but OpenBSD was missing from the list of OS's to use a monotonic clock on. What I don't understand is why is init_get_clock() not called anywhere? diff --git a/include/qemu/timer.h b/include/qemu/timer.h index 1766b2d..8b86fa5 100644 --- a/include/qemu/timer.h +++ b/include/qemu/timer.h @@ -118,7 +118,8 @@ extern int use_rt_clock; static inline int64_t get_clock(void) { #if defined(__linux__) || (defined(__FreeBSD__) && __FreeBSD_version >= 500000) \ - || defined(__DragonFly__) || defined(__FreeBSD_kernel__) + || defined(__DragonFly__) || defined(__FreeBSD_kernel__) \ + || defined(__OpenBSD__) if (use_rt_clock) { struct timespec ts; clock_gettime(CLOCK_MONOTONIC, &ts); -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.