qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	Artyom Tarasenko <atar4qemu@googlemail.com>
Subject: [Qemu-devel] Re: irq latency and tcg
Date: Sat, 12 Dec 2009 23:29:48 +0000	[thread overview]
Message-ID: <200912122329.48660.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580912120046w2904fda7yfcf278d43f8815fd@mail.gmail.com>

> According to comment in exec-all.h:
> /* Deterministic execution requires that IO only be performed on the last
>    instruction of a TB so that interrupts take effect immediately.  */
> 
> Sparc generator must then violate this assumption. Is the assumption
> valid also when not using icount and should the check be enabled for
> all cases, not just icount?

Not really.  With -icount we're trying to achieve deterministic behavior[1]. 
When icount is disabled a few extra instructions interrupt latency is the 
least of your problems.

I guess with in-core peripherals you may be able to accurately predict 
interrupt response. However for the vast majority of cases I wouldn't be 
surprised if real hardware has a few cycles latency anyway.

Paul

[1] Even with -icount, qemu is still a long way from being cycle accurate. The 
goal is to give reproducible and consistent results. Actual realtime 
characteristics are still likely to be very different from real hardware.

Paul

      reply	other threads:[~2009-12-12 23:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 13:30 [Qemu-devel] irq latency and tcg Artyom Tarasenko
2009-12-07 15:06 ` Paul Brook
2009-12-07 17:39   ` Artyom Tarasenko
2009-12-07 17:44     ` Paul Brook
2009-12-07 18:08 ` [Qemu-devel] " Blue Swirl
2009-12-09 12:30   ` Artyom Tarasenko
2009-12-12  8:46     ` Blue Swirl
2009-12-12 23:29       ` Paul Brook [this message]

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=200912122329.48660.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=atar4qemu@googlemail.com \
    --cc=blauwirbel@gmail.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).