From: Gleb Natapov <gleb@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] Register uhci_reset() callback.
Date: Tue, 16 Jun 2009 22:23:39 +0300 [thread overview]
Message-ID: <20090616192339.GJ782@redhat.com> (raw)
In-Reply-To: <f43fc5580906161210n285f2bdfnda5cf4c781798d0c@mail.gmail.com>
On Tue, Jun 16, 2009 at 10:10:59PM +0300, Blue Swirl wrote:
> > That's why real hardware has a nice long reset pulse, during which
> > every input change is ignored until the reset pulse is removed.
>
> qemu_irq does not have state. It's different from real HW IRQ, so QEMU
> devices don't need to do anything. I also had this confused earlier.
>
Yes, qemu_irq does not have state, but nonetheless the sate exists. It is
maintained inside piix3 (this is just implementation detail that may
or may not go away). But who, if not device itself, should know better
what IRQ level should be in any given time? You can literally call
qemu_irq() after each line of device emulation code and it will be OK,
slow may be, but correct. The more you call qemu_irq() the more closely
you emulate real HW level interrupt.
--
Gleb.
next prev parent reply other threads:[~2009-06-16 19:25 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 8:48 [Qemu-devel] Register uhci_reset() callback Gleb Natapov
2009-06-11 13:41 ` Paul Brook
2009-06-11 13:46 ` Gleb Natapov
2009-06-11 13:53 ` Paul Brook
2009-06-11 14:00 ` Gleb Natapov
2009-06-11 16:38 ` Jamie Lokier
2009-06-11 16:40 ` Gleb Natapov
2009-06-15 16:20 ` Avi Kivity
2009-06-16 15:00 ` Jamie Lokier
2009-06-16 15:18 ` Avi Kivity
2009-06-16 15:43 ` Jamie Lokier
2009-06-15 16:21 ` Avi Kivity
2009-06-15 17:02 ` Gleb Natapov
2009-06-15 17:17 ` Avi Kivity
2009-06-15 17:21 ` Gleb Natapov
2009-06-15 17:56 ` Paul Brook
2009-06-15 18:16 ` Gleb Natapov
2009-06-15 18:57 ` Blue Swirl
2009-06-15 19:30 ` Gleb Natapov
2009-06-15 19:50 ` Blue Swirl
2009-06-15 20:05 ` Gleb Natapov
2009-06-16 15:14 ` Blue Swirl
2009-06-16 15:20 ` Gleb Natapov
2009-06-16 16:54 ` Blue Swirl
2009-06-16 17:09 ` Gleb Natapov
2009-06-16 17:19 ` Blue Swirl
2009-06-16 18:39 ` Gleb Natapov
2009-06-18 9:20 ` Avi Kivity
2009-06-16 16:54 ` Paul Brook
2009-06-16 17:12 ` Blue Swirl
2009-06-16 18:00 ` Paul Brook
2009-06-16 18:10 ` Blue Swirl
2009-06-16 18:52 ` Jamie Lokier
2009-06-16 19:05 ` Jamie Lokier
2009-06-16 19:10 ` Blue Swirl
2009-06-16 19:23 ` Gleb Natapov [this message]
2009-06-16 19:16 ` Paul Brook
2009-06-16 17:47 ` Gleb Natapov
2009-06-16 17:04 ` 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=20090616192339.GJ782@redhat.com \
--to=gleb@redhat.com \
--cc=avi@redhat.com \
--cc=blauwirbel@gmail.com \
--cc=paul@codesourcery.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).