From: Alex Williamson <alex.williamson@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Andreas Hartmann <andihartmann@01019freenet.de>,
	bhelgaas@google.com, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: Re: [PATCH] PCI: Add Ralink RT2800 broken INTx masking quirk
Date: Thu, 07 Jun 2012 11:43:24 -0600	[thread overview]
Message-ID: <1339091004.26976.26.camel@ul30vt> (raw)
In-Reply-To: <4FD0E27B.6060502@web.de>
On Thu, 2012-06-07 at 19:18 +0200, Jan Kiszka wrote:
> On 2012-06-07 19:05, Alex Williamson wrote:
> > On Thu, 2012-06-07 at 08:18 +0200, Andreas Hartmann wrote:
> >> 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".
> > 
> > Yeah, that's probably a good idea.  For debugging and letting users have
> > a workaround rather than any kind of regular use.  I'll add a nointxmask
> > to vfio-pci with a description indicating that if it fixes a device to
> > report it for quirking.  Thanks,
> 
> Isn't this controllable on a per-device base from userspace (or is this
> what you mean)? That would nicely align to qemu-kvm's pci-assign
> share_intx property (and may allow to map pci-assign's user-visible
> interface to a vfio backend one day).
No, there's currently no per-device control of this from userspace with
VFIO.  It wouldn't be hard to make use of flags bits in the ioctls to
support it, but I don't just want to move the blacklist from the kernel
out to the user.  Thanks,
Alex
next prev parent reply	other threads:[~2012-06-07 17:43 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
2012-06-07 17:05   ` Alex Williamson
2012-06-07 17:18     ` Jan Kiszka
2012-06-07 17:43       ` Alex Williamson [this message]
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=1339091004.26976.26.camel@ul30vt \
    --to=alex.williamson@redhat.com \
    --cc=andihartmann@01019freenet.de \
    --cc=bhelgaas@google.com \
    --cc=jan.kiszka@web.de \
    --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).