From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, Alex Graf <agraf@suse.de>,
kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [RFC PATCH] vfio: add fixup for broken PCI devices
Date: Fri, 25 May 2012 22:36:40 +1000 [thread overview]
Message-ID: <1337949400.16119.25.camel@pasglop> (raw)
In-Reply-To: <1337948650.4714.88.camel@ul30vt>
On Fri, 2012-05-25 at 06:24 -0600, Alex Williamson wrote:
> > > To eliminate such effect, some quirk should be called. The
> proposed
> > > pci_fixup_final does its job well for mentioned NEC PCI USB but
> not
> > > sure if it is 100% correct.
> >
> > I think we should create a new quirk category... call it
> pci_fixup_reset
> > or something like that, which is responsible for blasting the thing
> into
> > submission when ownership changes.
> >
> > We'll need these for more than just USB I suspect.
>
> We already have pci_dev_specific_reset() called from pci_dev_reset().
> Does this device support any of the standard reset mechanisms? It
> would
> be nice to know what within the final fixups keeps this device
> working.
> Thanks,
Well, HW is HW ... it's going to be broken one way or another. Reset is
no exception, and we already have a way to deal with that sort of
breakage via the quirks. They are already divided in several categories
(early, normal, final, ...), I suggest we just add one for reset. No
point re-inventing a callback mechanism when we already have one.
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, Alex Graf <agraf@suse.de>,
kvm@vger.kernel.org, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH] vfio: add fixup for broken PCI devices
Date: Fri, 25 May 2012 22:36:40 +1000 [thread overview]
Message-ID: <1337949400.16119.25.camel@pasglop> (raw)
In-Reply-To: <1337948650.4714.88.camel@ul30vt>
On Fri, 2012-05-25 at 06:24 -0600, Alex Williamson wrote:
> > > To eliminate such effect, some quirk should be called. The
> proposed
> > > pci_fixup_final does its job well for mentioned NEC PCI USB but
> not
> > > sure if it is 100% correct.
> >
> > I think we should create a new quirk category... call it
> pci_fixup_reset
> > or something like that, which is responsible for blasting the thing
> into
> > submission when ownership changes.
> >
> > We'll need these for more than just USB I suspect.
>
> We already have pci_dev_specific_reset() called from pci_dev_reset().
> Does this device support any of the standard reset mechanisms? It
> would
> be nice to know what within the final fixups keeps this device
> working.
> Thanks,
Well, HW is HW ... it's going to be broken one way or another. Reset is
no exception, and we already have a way to deal with that sort of
breakage via the quirks. They are already divided in several categories
(early, normal, final, ...), I suggest we just add one for reset. No
point re-inventing a callback mechanism when we already have one.
Cheers,
Ben.
next prev parent reply other threads:[~2012-05-25 12:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:35 [RFC PATCH] vfio: add fixup for broken PCI devices Alexey Kardashevskiy
2012-05-25 7:35 ` [Qemu-devel] " Alexey Kardashevskiy
2012-05-25 8:28 ` Benjamin Herrenschmidt
2012-05-25 8:28 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-05-25 12:24 ` Alex Williamson
2012-05-25 12:24 ` [Qemu-devel] " Alex Williamson
2012-05-25 12:36 ` Benjamin Herrenschmidt [this message]
2012-05-25 12:36 ` Benjamin Herrenschmidt
2012-05-28 12:44 ` Michael S. Tsirkin
2012-05-28 12:44 ` Michael S. Tsirkin
2012-05-28 12:48 ` Jan Kiszka
2012-05-28 12:48 ` Jan Kiszka
2012-05-28 13:15 ` Michael S. Tsirkin
2012-05-28 13:15 ` Michael S. Tsirkin
2012-06-06 23:17 ` Alex Williamson
2012-06-06 23:17 ` [Qemu-devel] " Alex Williamson
2012-06-07 2:52 ` Benjamin Herrenschmidt
2012-06-07 2:52 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-06-07 3:56 ` Alex Williamson
2012-06-07 3:56 ` Alex Williamson
2012-06-07 4:37 ` Benjamin Herrenschmidt
2012-06-07 4:37 ` [Qemu-devel] " Benjamin Herrenschmidt
2012-06-22 8:16 ` Alexey Kardashevskiy
2012-06-22 8:16 ` [Qemu-devel] " Alexey Kardashevskiy
2012-08-17 14:28 ` Alexey Kardashevskiy
2012-08-17 14:28 ` [Qemu-devel] " Alexey Kardashevskiy
2012-08-21 2:31 ` Alex Williamson
2012-08-21 2:31 ` [Qemu-devel] " Alex Williamson
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=1337949400.16119.25.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=agraf@suse.de \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--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.