From: "Michael S. Tsirkin" <mst@redhat.com>
To: Isaku Yamahata <yamahata@valinux.co.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v3 3/3] piix_pci: optimize set irq path
Date: Mon, 21 Mar 2011 14:31:11 +0200 [thread overview]
Message-ID: <20110321123111.GA29012@redhat.com> (raw)
In-Reply-To: <20110321121032.GA9998@valinux.co.jp>
On Mon, Mar 21, 2011 at 09:10:32PM +0900, Isaku Yamahata wrote:
> On Mon, Mar 21, 2011 at 01:37:07PM +0200, Michael S. Tsirkin wrote:
> > > +static int piix3_post_load(void *opaque, int version_id)
> > > +{
> > > + PIIX3State *piix3 = opaque;
> > > + piix3_update_irq_levels(piix3);
> >
> > Couldn't figure out why would we not want to
> > propagate the interrupts here.
> > Could you explain please?
> > What happens if we do propagate them?
> > Nothing bad, right?
>
> I wanted to be just conservative.
> If you are brave enough to change the behavior, I'm fine with propagating
> interrupts.
>
> If we propagate the interrupts, guest OS may see interrupts
> unnecessarily/spuriously injected after load.
> Probably such interrupts doesn't harm OSes, so there is nothing
> bad in theory as you said.
> On the other hand, I hesitated to change the existing behavior because
> it would be very difficult to debug it and to test many OSes.
I expect it won't change the behaviour because the interrupts
are level: at the moment e.g. pci devices already reassert
interrupts on load.
But I agree it better be a separate patch, and needs a lot of testing.
> --
> yamahata
next prev parent reply other threads:[~2011-03-21 12:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 13:24 [Qemu-devel] [PATCH v3 0/3] piix_pci: optimize irq data path Isaku Yamahata
2011-03-19 13:24 ` [Qemu-devel] [PATCH v3 1/3] pci: add accessor function to get irq levels Isaku Yamahata
2011-03-19 13:24 ` [Qemu-devel] [PATCH v3 2/3] piix_pci: eliminate PIIX3State::pci_irq_levels Isaku Yamahata
2011-03-19 13:24 ` [Qemu-devel] [PATCH v3 3/3] piix_pci: optimize set irq path Isaku Yamahata
2011-03-21 11:37 ` [Qemu-devel] " Michael S. Tsirkin
2011-03-21 12:10 ` Isaku Yamahata
2011-03-21 12:31 ` Michael S. Tsirkin [this message]
2011-03-21 12:56 ` Isaku Yamahata
2011-03-21 13:01 ` Michael S. Tsirkin
2011-03-21 12:26 ` Isaku Yamahata
2011-03-21 14:10 ` Michael S. Tsirkin
2011-03-22 0:50 ` Isaku Yamahata
2011-03-22 13:40 ` Michael S. Tsirkin
2011-03-22 14:07 ` Isaku Yamahata
2011-03-22 16:24 ` Michael S. Tsirkin
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=20110321123111.GA29012@redhat.com \
--to=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=yamahata@valinux.co.jp \
/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.