qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: qemu-devel@nongnu.org
Cc: Gleb Natapov <gleb@qumranet.com>
Subject: [Qemu-devel] Re: [PATCH 1/3] Change qemu_set_irq() to return status information.
Date: Sun, 29 Jun 2008 22:58:46 +0200	[thread overview]
Message-ID: <4867F786.7070002@web.de> (raw)
In-Reply-To: <200806292134.08436.paul@codesourcery.com>

[-- Attachment #1: Type: text/plain, Size: 973 bytes --]

Paul Brook wrote:
>> The model takes into account that not all interrupt controller are
>> capable to detect missed interrupt (it is possible that there is no
>> interrupt controller at all). In this case irq function should
>> return one and everything will fall back to how it works now.
> 
> On a related note the correct way to fix this is "-icount auto".
> You should make sure that your hacks are not enabled when we have a realistic 
> virtual timebase.

Virtual timebases don't help if the guest has to interact with the real
life - ie. clocks you cannot tweak. In the end, you will have to bring
them in sync again, so this approach basically points in the right
direction.

However, I started to wonder if this model is already enough to handle
the case where QEMU itself looses ticks. At least the PIT should
currently not be able to deal with such issues, so you also won't see
coalesce counters increase. Or am I missing something?

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]

  parent reply	other threads:[~2008-06-29 20:58 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29 14:02 [Qemu-devel] [PATCH 0/3] Fix guest time drift under heavy load Gleb Natapov
2008-06-29 14:02 ` [Qemu-devel] [PATCH 1/3] Change qemu_set_irq() to return status information Gleb Natapov
2008-06-29 14:14   ` Avi Kivity
2008-06-29 14:18     ` Gleb Natapov
2008-06-29 14:53       ` Paul Brook
2008-06-29 15:37         ` Gleb Natapov
2008-06-29 14:38   ` Paul Brook
2008-06-29 15:40     ` Gleb Natapov
2008-06-29 18:11       ` Paul Brook
2008-06-29 19:44         ` Gleb Natapov
2008-06-29 20:34           ` Paul Brook
2008-06-29 20:49             ` Gleb Natapov
2008-06-30 13:26               ` Gleb Natapov
2008-06-30 14:00                 ` Paul Brook
2008-06-30 14:28                   ` Gleb Natapov
2008-06-30 14:35                     ` Paul Brook
2008-06-29 20:58             ` Jan Kiszka [this message]
2008-06-29 21:16               ` [Qemu-devel] " Paul Brook
2008-06-29 21:42                 ` Dor Laor
2008-06-29 21:47                 ` Jan Kiszka
2008-06-29 21:54                   ` Paul Brook
2008-06-30 13:18               ` Gleb Natapov
2008-06-29 14:02 ` [Qemu-devel] [PATCH 2/3] Fix time drift problem under high load when PIT is in use Gleb Natapov
2008-06-29 14:40   ` [Qemu-devel] " Jan Kiszka
2008-06-29 15:52     ` Gleb Natapov
2008-06-29 14:02 ` [Qemu-devel] [PATCH 3/3] Fix time drift problem under high load when RTC " Gleb Natapov
2008-06-29 14:37 ` [Qemu-devel] Re: [PATCH 0/3] Fix guest time drift under heavy load Jan Kiszka

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=4867F786.7070002@web.de \
    --to=jan.kiszka@web.de \
    --cc=gleb@qumranet.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).