From: Avi Kivity <avi@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Matthew Ogilvie <mmogilvi_qemu@miniinfo.net>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v5 5/6] i8259: fix so that dropping IRQ level always clears the interrupt request
Date: Tue, 11 Sep 2012 15:58:35 +0300 [thread overview]
Message-ID: <504F357B.8070201@redhat.com> (raw)
In-Reply-To: <504EFEF1.2080107@web.de>
On 09/11/2012 12:05 PM, Jan Kiszka wrote:
> I think this is convincing, maybe worth documenting in the related
> changelogs of QEMU and KVM. Avi, doubts remaining?
>
Nope, I think I've understood it finally.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-09-11 12:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 1:27 [Qemu-devel] [PATCH v5 0/6] Running Microport UNIX (ca 1987) Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 1/6] fix some debug printf format strings Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 2/6] vl: fix -hdachs/-hda argument order parsing issues Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 3/6] qemu-options.hx: mention retrace= VGA option Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 4/6] vga: add some optional CGA compatibility hacks Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 5/6] i8259: fix so that dropping IRQ level always clears the interrupt request Matthew Ogilvie
2012-09-10 8:56 ` Avi Kivity
2012-09-10 9:09 ` Jan Kiszka
2012-09-10 9:18 ` Avi Kivity
2012-09-10 9:33 ` Jan Kiszka
2012-09-10 13:09 ` Maciej W. Rozycki
2012-09-11 12:57 ` Avi Kivity
2012-09-11 4:32 ` Matthew Ogilvie
2012-09-11 9:05 ` Jan Kiszka
2012-09-11 12:58 ` Avi Kivity [this message]
2012-11-19 15:28 ` BALATON Zoltan
2012-11-20 5:05 ` Matthew Ogilvie
2012-09-10 1:27 ` [Qemu-devel] [PATCH v5 6/6] i8259: refactor pic_set_irq level logic Matthew Ogilvie
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=504F357B.8070201@redhat.com \
--to=avi@redhat.com \
--cc=jan.kiszka@web.de \
--cc=macro@linux-mips.org \
--cc=mmogilvi_qemu@miniinfo.net \
--cc=pbonzini@redhat.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).