From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.34) id 1BRGkY-0001Vu-NQ for qemu-devel@nongnu.org; Fri, 21 May 2004 16:36:14 -0400 Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.34) id 1BRGk2-0001NS-43 for qemu-devel@nongnu.org; Fri, 21 May 2004 16:36:13 -0400 Received: from [195.122.192.2] (helo=janik.cz) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BRGk1-0001My-HU for qemu-devel@nongnu.org; Fri, 21 May 2004 16:35:41 -0400 From: Pavel@Janik.cz (=?iso-8859-2?q?Pavel_Jan=EDk?=) Date: Fri, 21 May 2004 22:35:35 +0200 Message-ID: <87vfip5xig.fsf@Janik.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] Debugging IRQ latency Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org Hi, hw/i8259.c contains (when DEBUG_ is turned on): (double)(cpu_get_ticks() - irq_time[irq]) * 1000000.0 / ticks_= per_sec); but cpu_get_ticks is defined as static in vl.c: static inline int64_t cpu_get_ticks(void) Thus you can't debug IRQ latency. --=20 Pavel Jan=EDk Proving me wrong is always a good sport ;) -- Linus Torvalds in linux-kernel