public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rajesh Shah <rajesh.shah@intel.com>
To: "Michael S. Tsirkin" <mst@mellanox.co.il>
Cc: Greg KH <gregkh@suse.de>, Roland Dreier <rolandd@cisco.com>,
	Brice Goglin <brice@myri.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: AMD 8131 MSI quirk called too late, bus_flags not inherited ?
Date: Wed, 24 May 2006 10:05:05 -0700	[thread overview]
Message-ID: <20060524100505.A400@unix-os.sc.intel.com> (raw)
In-Reply-To: <20060524165958.GE21266@mellanox.co.il>; from mst@mellanox.co.il on Wed, May 24, 2006 at 07:59:58PM +0300

On Wed, May 24, 2006 at 07:59:58PM +0300, Michael S. Tsirkin wrote:
> 
> Offtopic, something I wanted to bring up with respect to MSI,
> but never had the time to debug:
> 
> If I do
> 
> pci_enable_msix, pci_disable_msix
> 
> then later
> 
> pci_enable_msi
> 
> on the same device fails with the following message:
> PCI: 0000:08:00.0: Can't enable MSI.  Device already has MSI-X vectors assigned
> 
> This is not something new - has been happening since forever.
> Looks like not all MSI-X vectors get properly unassigned by pci_disable_msix.
> 
Yes, this has been reported by others too. I've been looking at
MSI code recently to fix an unrelated problem, and noticed that
the code has policies about vector reservation that prevent
what you're trying to do. I'm planning to clean up the MSI
code shortly (patches out hopefully by next week), and will
remove such policies since many people are trying to do this.

thanks,
Rajesh

  reply	other threads:[~2006-05-24 17:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-15 21:11 AMD 8131 MSI quirk called too late, bus_flags not inherited ? Brice Goglin
2006-05-18 15:54 ` Greg KH
2006-05-21 10:16   ` Michael S. Tsirkin
2006-05-21 10:58     ` Brice Goglin
2006-05-21 12:17       ` Michael S. Tsirkin
2006-05-21 12:31         ` Brice Goglin
2006-05-21 13:10           ` Michael S. Tsirkin
2006-05-21 13:24             ` Brice Goglin
2006-05-23  4:19               ` Greg KH
2006-05-23  7:05                 ` Brice Goglin
2006-05-24 16:59                 ` Michael S. Tsirkin
2006-05-24 17:05                   ` Rajesh Shah [this message]
2006-05-21 13:29           ` Michael S. Tsirkin
     [not found] <fa.WOQy7TVxeMkzxI+BbQP2Wqi34A0@ifi.uio.no>
     [not found] ` <fa.7RUPmW8q906KfAmuRItEvwbAUvg@ifi.uio.no>
2006-05-21 19:19   ` Dave Olson
     [not found] <fa.qrx8XYAhsFvMnCfipnnEkuNPFSA@ifi.uio.no>
     [not found] ` <fa.hVNDQ4A/sPeiQKqlsb6JDQFEpLE@ifi.uio.no>
2006-05-23  7:32   ` Dave Olson

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=20060524100505.A400@unix-os.sc.intel.com \
    --to=rajesh.shah@intel.com \
    --cc=brice@myri.com \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=rolandd@cisco.com \
    /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