From: Andreas Hartmann <andihartmann@01019freenet.de>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: bjorn.helgaas@hp.com, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
jan.kiszka@siemens.com, andihartmann@01019freenet.de
Subject: Re: [PATCH] PCI: Add Ralink RT2800 broken INTx masking quirk
Date: Thu, 07 Jun 2012 08:18:15 +0200 [thread overview]
Message-ID: <4FD047A7.6050602@01019freenet.de> (raw)
In-Reply-To: <20120606212241.6627.98371.stgit@bling.home>
Hello Alex,
what about a module parameter to achieve this behaviour manually by
the user without recompiling? I fear, there are much more candidates
out there needing this "feature".
Kind regards and thank you,
Andreas
Alex Williamson wrote:
> Passes pci_intx_mask_supported but continues to send interrupts as
> discovered through VFIO-based device assignment.
>
> http://www.spinics.net/lists/kvm/msg73738.html
>
> Signed-off-by: Alex Williamson <alex.williamson@redhat.com> ---
>
> Depends on Jan's base patch for this quirk:
> http://www.spinics.net/lists/linux-pci/msg15516.html
>
> drivers/pci/quirks.c | 2 ++ 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/pci/quirks.c b/drivers/pci/quirks.c index
> cbb4358..178f494 100644 --- a/drivers/pci/quirks.c +++
> b/drivers/pci/quirks.c @@ -2940,6 +2940,8 @@ static void __devinit
> quirk_broken_intx_masking(struct pci_dev *dev) }
> DECLARE_PCI_FIXUP_FINAL(PCI_VENDOR_ID_CHELSIO, 0x0010,
> quirk_broken_intx_masking); +DECLARE_PCI_FIXUP_FINAL(0x1814,
> 0x0601, /* Ralink RT2800 802.11n PCI */ +
> quirk_broken_intx_masking);
>
> static void pci_do_fixups(struct pci_dev *dev, struct pci_fixup
> *f, struct pci_fixup *end)
>
next prev parent reply other threads:[~2012-06-07 6:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 21:23 [PATCH] PCI: Add Ralink RT2800 broken INTx masking quirk Alex Williamson
2012-06-06 21:47 ` Alex Williamson
2012-06-07 6:13 ` Andreas Hartmann
2012-06-07 6:18 ` Andreas Hartmann [this message]
2012-06-07 17:05 ` Alex Williamson
2012-06-07 17:18 ` Jan Kiszka
2012-06-07 17:43 ` Alex Williamson
2012-06-07 21:01 ` Andreas Hartmann
2012-06-07 21:25 ` Alex Williamson
2012-06-07 21:42 ` Andreas Hartmann
2012-06-07 22:09 ` Alex Williamson
2012-06-08 1:56 ` Andreas Hartmann
2012-06-08 10:56 ` Andreas Hartmann
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=4FD047A7.6050602@01019freenet.de \
--to=andihartmann@01019freenet.de \
--cc=alex.williamson@redhat.com \
--cc=bjorn.helgaas@hp.com \
--cc=jan.kiszka@siemens.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.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).