linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <matthew@wil.cx>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: Jesse Barnes <jbarnes@virtuousgeek.org>,
	David Vrabel <david.vrabel@csr.com>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PCI: MSI interrupts masked using prohibited method
Date: Fri, 25 Jul 2008 09:51:46 -0600	[thread overview]
Message-ID: <20080725155146.GB17093@parisc-linux.org> (raw)
In-Reply-To: <20080725155329.79821436@brian.englab.brq.redhat.com>

On Fri, Jul 25, 2008 at 03:53:29PM +0200, Michal Schmidt wrote:
> Maybe we should just not use MSI for devices without maskbits.

That seems excessive.  I wouldn't object to forbidding CPU affinity
changes for devices:

 - Without maskbits
 - With the intx quirk

I'd want to look into it in a bit more detail .... perhaps we could
allow irq affinity if we don't have to change the address, only the
data.

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

  reply	other threads:[~2008-07-25 15:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 10:46 PCI: MSI interrupts masked using prohibited method David Vrabel
2008-06-25 21:20 ` Jesse Barnes
2008-06-27 12:17   ` David Vrabel
2008-06-27 17:07     ` Jesse Barnes
2008-07-16 19:43       ` Jesse Barnes
2008-07-16 19:58         ` Matthew Wilcox
2008-07-16 20:35           ` David Miller
2008-07-17 12:16           ` Krzysztof Halasa
2008-07-17 12:43             ` Matthew Wilcox
2008-07-17 13:14           ` David Vrabel
2008-07-17 15:39             ` Matthew Wilcox
2008-07-17 15:58               ` Thomas Gleixner
2008-07-17 16:11                 ` Matthew Wilcox
2008-07-17 17:04                   ` Thomas Gleixner
2008-07-17 16:56                 ` Matthew Wilcox
     [not found]                   ` <487F7DFA.10101@csr.com>
2008-07-17 19:48                     ` Matthew Wilcox
2008-07-18 10:33                       ` David Vrabel
2008-07-22 13:56                         ` Michal Schmidt
2008-07-22 17:52                           ` Jesse Barnes
2008-07-23 13:02                             ` Michal Schmidt
2008-07-25 13:29                             ` Michal Schmidt
2008-07-25 13:42                               ` Matthew Wilcox
2008-07-25 13:53                                 ` Michal Schmidt
2008-07-25 15:51                                   ` Matthew Wilcox [this message]
2008-07-28  9:54                                     ` Michal Schmidt
2008-07-25 16:37                                   ` David Vrabel
2008-07-25 16:56                                     ` Matthew Wilcox
2008-07-25 19:12                                       ` Jesse Barnes
2008-07-28  9:59                                       ` Michal Schmidt
2008-07-28 22:04                                         ` Jesse Barnes

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=20080725155146.GB17093@parisc-linux.org \
    --to=matthew@wil.cx \
    --cc=david.vrabel@csr.com \
    --cc=jbarnes@virtuousgeek.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mschmidt@redhat.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;
as well as URLs for NNTP newsgroup(s).