All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@csr.com>
To: "Moore, Eric" <Eric.Moore@lsi.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	"Prakash, Sathya" <Sathya.Prakash@lsi.com>
Subject: Re: [PATCH 2/2] fusion:  Implement generic interrupt misroute handling
Date: Mon, 04 Aug 2008 14:55:25 +0100	[thread overview]
Message-ID: <48970A4D.2090309@csr.com> (raw)
In-Reply-To: <660360F4F2570145BD872F298951B17A3ADCEDB9@cosmail03.lsi.com>

Moore, Eric wrote:
> Thanks, I will try this out.   However I thought I saw lost
> interrupts occurring randomly, meaning it was not necessarily the
> first config page access.  I'm back in the office on 8/11, I will
> test it out then and provide feedback.

Is this using MSI on a device without per-vector mask bits?  If so, then
this patch may help.

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=ce6fce4295ba727b36fdc73040e444bd1aae64cd

David
-- 
David Vrabel, Senior Software Engineer, Drivers
CSR, Churchill House, Cambridge Business Park,  Tel: +44 (0)1223 692562
Cowley Road, Cambridge, CB4 0WZ                 http://www.csr.com/

  parent reply	other threads:[~2008-08-04 13:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-03 18:05 [PATCH 2/2] fusion: Implement generic interrupt misroute handling James Bottomley
2008-08-03 22:59 ` Moore, Eric
2008-08-03 22:59   ` Moore, Eric
2008-08-03 23:07   ` James Bottomley
2008-08-04 13:55   ` David Vrabel [this message]
2008-08-05 16:36     ` James Bottomley
2008-08-05 17:38       ` Jesse Barnes
2008-08-05 20:45         ` James Bottomley

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=48970A4D.2090309@csr.com \
    --to=david.vrabel@csr.com \
    --cc=Eric.Moore@lsi.com \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=Sathya.Prakash@lsi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.