From: David Mosberger <davidm@napali.hpl.hp.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Takayoshi Kochi <t-kochi@bq.jp.nec.com>,
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 07:33:26 +0000 [thread overview]
Message-ID: <16464.5702.108960.33261@napali.hpl.hp.com> (raw)
In-Reply-To: <MDEEKOKJPMPMKGHIFAMAIEMADGAA.kaneshige.kenji@jp.fujitsu.com>
Kenji,
Your patch failed to apply apparently because all tabs got replaced by
blanks. I fixed it by hand for now, but in the future, I'd appreciate
it if you could either fix your mailer config so it doesn't muck with
whitespace (or don't paste & cut patches if that's how the patch got
mangled). As a last resort, send patches as a MIME attachment.
>>>>> On Thu, 11 Mar 2004 14:29:59 +0900, Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> said:
Kenji> I think you are right. Probe_irq_on() still have another
Kenji> problems even if my patch is applied. For example, if buggy
Kenji> PCI device generates interrupts during its device driver
Kenji> calls probe_irq_on(), these interrupts might be considered as
Kenji> spurious and IRQ probing will fail. I think this is another
Kenji> problem than I pointed out.
That should be OK. The probe_irq_on() interface never was guaranteed
to work under all circumstances.
Kenji> In addition to this, if probe_irq_on() is used for PCI
Kenji> interrupts (level triggered), interrupts are generated
Kenji> repeatedly because there are no handlers which clears these
Kenji> interrupt request. But I think this is not a problem, because
Kenji> these interrupts will be masked by probe_irq_on() or
Kenji> probe_irq_off() soon. If this is a problem, I think
Kenji> probe_irq_on() should never be used for PCI (level triggered)
Kenji> interrupt probing.
That's a good point but I doubt it's going to cause trouble because of
the history behind this interface (it's mostly needed for ISA
devices). If it did, it wouldn't be hard to fix, but I'm not sure
it's worth bothering. Perhaps it would be a good idea to get rid of
the interface altogether in the 2.7 timeframe (for ia64 and other
ISA-free platforms at least; I don't think it can be gotten rid of for
x86).
--david
prev parent reply other threads:[~2004-03-11 7:33 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
2004-03-11 7:33 ` David Mosberger [this message]
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=16464.5702.108960.33261@napali.hpl.hp.com \
--to=davidm@napali.hpl.hp.com \
--cc=davidm@hpl.hp.com \
--cc=kaneshige.kenji@jp.fujitsu.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