mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Michal Schmidt <mschmidt@redhat.com>
Cc: David Vrabel <david.vrabel@csr.com>,
	Matthew Wilcox <matthew@wil.cx>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: PCI: MSI interrupts masked using prohibited method
Date: Tue, 22 Jul 2008 10:52:26 -0700	[thread overview]
Message-ID: <200807221052.26879.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080722155629.1160635e@brian.englab.brq.redhat.com>

On Tuesday, July 22, 2008 6:56 am Michal Schmidt wrote:
> On Fri, 18 Jul 2008 11:33:10 +0100
>
> David Vrabel <david.vrabel@csr.com> wrote:
> > Matthew Wilcox wrote:
> > > I think David's original patch (just declining to mask the
> > > interrupt) is the best approach to take.  Perhaps architectures
> > > with saner interrupt hardware would like to try the approach I've
> > > mentioned here.
> > >
> > > I don't like the comment in http://lkml.org/lkml/2008/6/27/199 as
> > > it's not prohibited ... just a bad idea.  How about this patch?
> >
> > The PCI specification is quite clear that it's prohibited.  The
> > problem also is more severe than simply having spurious interrupts --
> > with some devices if a line interrupt is generated (regardless of
> > whether it ends up on the bus) then no more interrupts are generated.
> >
> > I also think that the change requires a comment in the code.  It odd
> > to have a mask function that doesn't really mask so a comment is
> > necessary to explain why this is.
> >
> > Please apply this instead.
> >
> > David
>
> This breaks the setting of SMP affinity for MSI interrupts :-(
> With the patch, writes to /proc/irq/<n>/smp_affinity are ignored for an
> MSI interrupt.

It should only break it for devices that don't provide a mask bit.  But given 
that we can't really mask generically on those devices, maybe that's ok given 
that it fixes the other problems mentioned in this thread...

Jesse

  reply	other threads:[~2008-07-22 17:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 10:46 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 [this message]
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
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=200807221052.26879.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=david.vrabel@csr.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=matthew@wil.cx \
    --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

Powered by JetHome