qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gleb Natapov <gleb@redhat.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org, Avi Kivity <avi@redhat.com>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] Register uhci_reset() callback.
Date: Tue, 16 Jun 2009 20:09:31 +0300	[thread overview]
Message-ID: <20090616170931.GE782@redhat.com> (raw)
In-Reply-To: <f43fc5580906160954q38e0754dmd063ff90c9124bd8@mail.gmail.com>

On Tue, Jun 16, 2009 at 07:54:25PM +0300, Blue Swirl wrote:
> On 6/16/09, Gleb Natapov <gleb@redhat.com> wrote:
> > On Tue, Jun 16, 2009 at 06:14:51PM +0300, Blue Swirl wrote:
> >  > > Because interrupt line is stuck a guest can't get to the point where it
> >  > >  loads a driver to the second device. For outside observer the guest
> >  > >  just hangs.
> >  >
> >  > I see. The problem is in piix_pci interrupt handling, pci_irq_levels[]
> >  > should be set to zero on reset.
> >
> > The patch that does that was rejected earlier :)
> >  http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg00342.html
> >  http://lists.gnu.org/archive/html/qemu-devel/2009-06/msg00344.html
> 
> I think patch 2/3 is bogus, but 3/3 should be the correct way. Nobody
> commented on that.
> 
What is bogus about 2/3? But the comment were not about specific patch,
more about the general approach. And conclusion was that each device should
lower its line. This is how real HW works BTW. IMHO both things should
be done, pci bus should reset its internal state and each device should
lower its own line (bus implementation may be changed in the future to
more be like real HW).

--
			Gleb.

  reply	other threads:[~2009-06-16 17:11 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-11  8:48 [Qemu-devel] Register uhci_reset() callback Gleb Natapov
2009-06-11 13:41 ` Paul Brook
2009-06-11 13:46   ` Gleb Natapov
2009-06-11 13:53     ` Paul Brook
2009-06-11 14:00       ` Gleb Natapov
2009-06-11 16:38         ` Jamie Lokier
2009-06-11 16:40           ` Gleb Natapov
2009-06-15 16:20             ` Avi Kivity
2009-06-16 15:00               ` Jamie Lokier
2009-06-16 15:18                 ` Avi Kivity
2009-06-16 15:43                   ` Jamie Lokier
2009-06-15 16:21     ` Avi Kivity
2009-06-15 17:02       ` Gleb Natapov
2009-06-15 17:17         ` Avi Kivity
2009-06-15 17:21           ` Gleb Natapov
2009-06-15 17:56         ` Paul Brook
2009-06-15 18:16           ` Gleb Natapov
2009-06-15 18:57             ` Blue Swirl
2009-06-15 19:30               ` Gleb Natapov
2009-06-15 19:50                 ` Blue Swirl
2009-06-15 20:05                   ` Gleb Natapov
2009-06-16 15:14                     ` Blue Swirl
2009-06-16 15:20                       ` Gleb Natapov
2009-06-16 16:54                         ` Blue Swirl
2009-06-16 17:09                           ` Gleb Natapov [this message]
2009-06-16 17:19                             ` Blue Swirl
2009-06-16 18:39                               ` Gleb Natapov
2009-06-18  9:20                               ` Avi Kivity
2009-06-16 16:54                         ` Paul Brook
2009-06-16 17:12                           ` Blue Swirl
2009-06-16 18:00                             ` Paul Brook
2009-06-16 18:10                               ` Blue Swirl
2009-06-16 18:52                                 ` Jamie Lokier
2009-06-16 19:05                                   ` Jamie Lokier
2009-06-16 19:10                                     ` Blue Swirl
2009-06-16 19:23                                       ` Gleb Natapov
2009-06-16 19:16                                   ` Paul Brook
2009-06-16 17:47                           ` Gleb Natapov
2009-06-16 17:04                 ` Paul Brook

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=20090616170931.GE782@redhat.com \
    --to=gleb@redhat.com \
    --cc=avi@redhat.com \
    --cc=blauwirbel@gmail.com \
    --cc=paul@codesourcery.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).