From: Anthony Liguori <anthony@codemonkey.ws>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Matthew Ogilvie <mmogilvi_qemu@miniinfo.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 6/6] i8259: add -no-spurious-interrupt-hack option
Date: Mon, 27 Aug 2012 10:50:25 -0500 [thread overview]
Message-ID: <876284mj0e.fsf@codemonkey.ws> (raw)
In-Reply-To: <503B82C6.5080007@redhat.com>
Paolo Bonzini <pbonzini@redhat.com> writes:
> Il 27/08/2012 15:55, Anthony Liguori ha scritto:
>>> > This patch provides a way to optionally suppress spurious interrupts,
>>> > as a workaround for systems described below:
>>> >
>>> > Some old operating systems do not handle spurious interrupts well,
>>> > and qemu tends to generate them significantly more often than
>>> > real hardware.
>> This is the wrong approach. You add a LostTickPolicy property to the
>> i8259 device.
>
> Isn't the i8254 the one that would need a LostTickPolicy?
You're right, I too quickly read this patch and misunderstood what it's
doing.
Regards,
Anthony Liguori
>
> But this seems like a bug that is either in the i8259 emulation, or in
> the firmware. Your own suggestion of setting IRQ2 to level-triggered in
> SeaBIOS is definitely a good one.
>
> Paolo
next prev parent reply other threads:[~2012-08-27 15:50 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-23 6:24 [Qemu-devel] [PATCH v2 0/6] Running Microport UNIX (ca 1987) Matthew Ogilvie
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 1/6] fix some debug printf format strings Matthew Ogilvie
2012-08-23 11:50 ` Andreas Färber
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 2/6] target-i386/translate.c: mov to/from crN/drN: ignore mod bits Matthew Ogilvie
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 3/6] vl: fix -hdachs/-hda argument order parsing issues Matthew Ogilvie
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 4/6] qemu-options.hx: mention retrace= VGA option Matthew Ogilvie
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 5/6] vga: add some optional CGA compatibility hacks Matthew Ogilvie
2012-08-23 6:24 ` [Qemu-devel] [PATCH v2 6/6] i8259: add -no-spurious-interrupt-hack option Matthew Ogilvie
2012-08-24 5:40 ` Jan Kiszka
2012-08-24 8:05 ` Matthew Ogilvie
2012-08-24 8:16 ` Jan Kiszka
2012-08-27 13:55 ` Anthony Liguori
2012-08-27 14:23 ` Paolo Bonzini
2012-08-27 15:50 ` Anthony Liguori [this message]
2012-08-24 3:58 ` [Qemu-devel] [PATCH v2 0/6] Running Microport UNIX (ca 1987) malc
2012-08-24 5:44 ` Jan Kiszka
2012-08-24 7:19 ` Peter Maydell
2012-08-24 13:39 ` Paolo Bonzini
2012-08-24 13:46 ` Peter Maydell
2012-08-24 9:13 ` [Qemu-devel] [PATCH v3 0/3] Microport UNIX series (was: [PATCH v2 0/6] ...) Matthew Ogilvie
2012-08-24 9:13 ` [Qemu-devel] [PATCH 1/3] debug printf (cirrus_vga): fixup unintended format change Matthew Ogilvie
2012-08-24 9:13 ` [Qemu-devel] [PATCH 2/3] vga cga_hack=palette_blanking: narrower conditions for hack Matthew Ogilvie
2012-08-24 9:13 ` [Qemu-devel] [PATCH 3/3] doc: mention that -no-spurious-interrupt-hack doesn't work with KVM Matthew Ogilvie
2012-08-24 12:02 ` [Qemu-devel] [PATCH v2 0/6] Running Microport UNIX (ca 1987) malc
2012-08-24 12:10 ` Jan Kiszka
2012-08-24 12:18 ` malc
2012-08-27 13:50 ` Anthony Liguori
2012-08-27 14:09 ` malc
2012-08-27 14:17 ` Anthony Liguori
2012-08-27 14:38 ` malc
2012-08-27 15:11 ` Anthony Liguori
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=876284mj0e.fsf@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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 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.