From: Andriy Gapon <avg@icyb.net.ua>
To: Beth Kon <eak@us.ibm.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: hpet emulation problems
Date: Tue, 21 Jul 2009 21:26:47 +0300 [thread overview]
Message-ID: <4A660867.7060404@icyb.net.ua> (raw)
In-Reply-To: <4A660611.6040801@us.ibm.com>
on 21/07/2009 21:16 Beth Kon said the following:
> Thanks for catching these bugs! I'll submit corrections shortly.
>
> As far as supporting level-triggered interrupts, all the guests I tested
> used edge-triggered interrupts, so this is what I implemented as a first
> pass. I don't think there is any reason not to implement
> level-triggered, though I am not planning to work on that at this point.
Beth,
thank you very much!
I think that level-triggered interrupt support could be useful (in the future),
for supporting HPET drivers that use non-legacy-replacement mode or extra
timers, when the respective interrupts have to be shared with PCI interrupts for
one reason or another.
--
Andriy Gapon
next prev parent reply other threads:[~2009-07-21 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 12:29 [Qemu-devel] hpet emulation problems Andriy Gapon
2009-07-21 12:53 ` [Qemu-devel] " Andriy Gapon
2009-07-21 18:16 ` Beth Kon
2009-07-21 18:26 ` Andriy Gapon [this message]
2009-07-23 10:10 ` Andriy Gapon
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=4A660867.7060404@icyb.net.ua \
--to=avg@icyb.net.ua \
--cc=eak@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.