From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] Register usb-uhci reset function.
Date: Tue, 16 Jun 2009 19:41:05 +0100 [thread overview]
Message-ID: <200906161941.06191.paul@codesourcery.com> (raw)
In-Reply-To: <20090616173723.GF782@redhat.com>
>> If allow devices to be reset independently then they should probably set
>> theit IRQ output on reset.
>
>It is not "if" it is "when". We have to allow device to be reset
> independently for hot-unplug.
I'm not entirely convinced about reset-on-hotunplug. What about a device that
pulls its IRQ line high on reset?
> > The only relevant circumstances are if the devices raises an IRQ, and is
> > then reset by software while the system is running. It's got nothing to
> > do with piix3, PCI bus interrupt sharing or system reset. If you are
> > seeing problems after a system reset then your bug lies elsewhere.
>
> So you apparently never heard about hardware reset? You never saw buggy
> guests that does not reset HW before reboot?
Clearing device state on full system reset makes sense because the whole point
is that we're returning the system to its power-on state.
Lowering the IRQ when a single device is reset also makes sense.
However having the device explicit set its IRQ line during a full system reset
is a different matter. This is probably harmless most of the time, and may
paper over other bugs (e.g. the PCI bus not being reset properly). However I
do not believe it is the correct justification for these changes.
Paul
next prev parent reply other threads:[~2009-06-16 18:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 12:47 [Qemu-devel] [PATCH] Register usb-uhci reset function Gleb Natapov
2009-06-16 17:14 ` Paul Brook
2009-06-16 17:37 ` Gleb Natapov
2009-06-16 18:41 ` Paul Brook [this message]
2009-06-16 19:11 ` Gleb Natapov
2009-06-16 19:38 ` Paul Brook
2009-06-16 22:57 ` Zachary Amsden
2009-06-17 8:12 ` Gleb Natapov
2009-06-16 18:02 ` Blue Swirl
2009-06-16 19:19 ` Anthony Liguori
2009-06-16 19:26 ` Gleb Natapov
2009-06-17 9:07 ` Filip Navara
2009-06-17 9:43 ` Gleb Natapov
2009-06-17 10:17 ` Filip Navara
2009-06-17 11:06 ` Gleb Natapov
2009-06-17 11:25 ` Dor Laor
2009-06-17 11:39 ` Gleb Natapov
2009-06-17 11:50 ` Filip Navara
2009-06-17 11:36 ` Filip Navara
2009-06-17 12:12 ` Gleb Natapov
2009-06-17 13:03 ` Filip Navara
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=200906161941.06191.paul@codesourcery.com \
--to=paul@codesourcery.com \
--cc=gleb@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).