From: Paul Brook <paul@codesourcery.com>
To: Artyom Tarasenko <atar4qemu@googlemail.com>
Cc: Blue Swirl <blauwirbel@gmail.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] irq latency and tcg
Date: Mon, 7 Dec 2009 17:44:14 +0000 [thread overview]
Message-ID: <200912071744.15123.paul@codesourcery.com> (raw)
In-Reply-To: <fb8d4f70912070939xd8ef0eera7aa687bc6e004dd@mail.gmail.com>
> > Using -icount should give you precise interrupt delivery.
>
> That's what I thought, but as I reported a few days ago, I couldn't
> find a good value for icount when using OBP.
> I tried a few values but keep getting "qemu: fatal: Raised interrupt
> while not in I/O function".
That's almost certainly a bug in the sparc backend.
Paul
next prev parent reply other threads:[~2009-12-07 17:44 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 [this message]
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
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=200912071744.15123.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).