From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Takayoshi Kochi <t-kochi@bq.jp.nec.com>, kaneshige.kenji@jp.fujitsu.com
Cc: davidm@hpl.hp.com, linux-ia64@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: RE: [PATCH] fix PCI interrupt setting for ia64
Date: Thu, 11 Mar 2004 05:29:59 +0000 [thread overview]
Message-ID: <MDEEKOKJPMPMKGHIFAMAIEMADGAA.kaneshige.kenji@jp.fujitsu.com> (raw)
In-Reply-To: <20040311.103447.10929472.t-kochi@bq.jp.nec.com>
In-Reply-To: <MDEEKOKJPMPMKGHIFAMAKECGDGAA.kaneshige.kenji@jp.fujitsu.com>
Hi,
Sorry, I misunderstood your concern.
I think you are right. Probe_irq_on() still have another problems even if my
patch
is applied. For example, if buggy PCI device generates interrupts during its
device
driver calls probe_irq_on(), these interrupts might be considered as
spurious and
IRQ probing will fail. I think this is another problem than I pointed out.
In addition to this, if probe_irq_on() is used for PCI interrupts (level
triggered),
interrupts are generated repeatedly because there are no handlers which
clears
these interrupt request. But I think this is not a problem, because these
interrupts
will be masked by probe_irq_on() or probe_irq_off() soon. If this is a
problem, I think
probe_irq_on() should never be used for PCI (level triggered) interrupt
probing.
Regards,
Kenji Kaneshige
> -----Original Message-----
> From: linux-ia64-owner@vger.kernel.org
> [mailto:linux-ia64-owner@vger.kernel.org]On Behalf Of Takayoshi Kochi
> Sent: Thursday, March 11, 2004 10:35 AM
> To: kaneshige.kenji@jp.fujitsu.com
> Cc: davidm@hpl.hp.com; linux-ia64@vger.kernel.org;
> linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] fix PCI interrupt setting for ia64
>
>
> Hi,
>
> From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
> Subject: RE: [PATCH] fix PCI interrupt setting for ia64
> Date: Thu, 11 Mar 2004 09:34:06 +0900
>
> > Hi,
> >
> > I'm sorry that the report falls behind. I wanted to check out by using
> > real device driver which uses a probe_irq_on(), but I don't
> have appropriate
> > environment now.
> >
> > Though I didn't check out on a real machine yet, I believe my
> patch doesn't
> > have any influence on probe_irq_on() because current
> probe_irq_on() calls
> > startup callback to unmask the RTEs as you said before.
>
> My concern was that if there's a buggy PCI device that raises
> interrupts all the time until it's initialized by some device driver,
> probe_irq_on() would not work as expected regardless of whether
> your patch is applied or not. I thought masking the interrupt line
> doesn't work around this case.
>
> ---
> Takayoshi Kochi <t-kochi@bq.jp.nec.com>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-03-11 5:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 2:49 [PATCH] fix PCI interrupt setting for ia64 Kenji Kaneshige
2004-03-08 6:30 ` Grant Grundler
2004-03-08 21:37 ` David Mosberger
2004-03-08 7:34 ` Liu, Benjamin
2004-03-08 7:44 ` Liu, Benjamin
2004-03-08 9:25 ` Takayoshi Kochi
2004-03-08 19:12 ` Bjorn Helgaas
2004-03-08 19:13 ` Bjorn Helgaas
2004-03-08 21:44 ` David Mosberger
2004-03-08 21:54 ` Russell King
2004-03-08 22:05 ` Bjorn Helgaas
2004-03-08 22:10 ` David Mosberger
2004-03-08 22:41 ` Bjorn Helgaas
2004-03-08 22:50 ` David Mosberger
2004-03-08 8:31 ` Kenji Kaneshige
2004-03-08 9:14 ` Liu, Benjamin
2004-03-08 10:42 ` Kenji Kaneshige
2004-03-08 10:46 ` Kenji Kaneshige
2004-03-10 20:09 ` David Mosberger
2004-03-11 0:34 ` Kenji Kaneshige
2004-03-11 1:34 ` Takayoshi Kochi
2004-03-11 7:22 ` David Mosberger
2004-03-11 5:29 ` Kenji Kaneshige [this message]
2004-03-11 7:33 ` David Mosberger
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=MDEEKOKJPMPMKGHIFAMAIEMADGAA.kaneshige.kenji@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=davidm@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=t-kochi@bq.jp.nec.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