| commit | 3baa43fdc9b64646b468b92936c4842c51b9e2ed | |
| author | Eric W. Biederman <ebiederm@xmission.com> | |
| Wed, 7 Mar 2007 19:23:54 +0000 (7 14:23 -0500) | ||
| committer | Greg Kroah-Hartman <gregkh@suse.de> | |
| Fri, 9 Mar 2007 18:50:33 +0000 (9 10:50 -0800) | ||
| tree | 0a004d203f41f46cc7a1ace9c2eb1dbd81bdfde0 | treesnapshot (tar.gz zip) |
| parent | 7670279989a552a7a8afd275368d55a4f3b5054b | commitdiff |
x86-64: survive having no irq mapping for a vector
Occasionally the kernel has bugs that result in no irq being found for a
given cpu vector. If we acknowledge the irq the system has a good chance
of continuing even though we dropped an irq message. If we continue to
simply print a message and not acknowledge the irq the system is likely to
become non-responsive shortly there after.
AK: Fixed compilation for UP kernels
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Cc: "Luigi Genoni" <luigi.genoni@pirelli.com>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
Occasionally the kernel has bugs that result in no irq being found for a
given cpu vector. If we acknowledge the irq the system has a good chance
of continuing even though we dropped an irq message. If we continue to
simply print a message and not acknowledge the irq the system is likely to
become non-responsive shortly there after.
AK: Fixed compilation for UP kernels
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Andi Kleen <ak@suse.de>
Cc: "Luigi Genoni" <luigi.genoni@pirelli.com>
Cc: Andi Kleen <ak@suse.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Chris Wright <chrisw@sous-sol.org>
| arch/x86_64/kernel/irq.c | diffblobblamehistory |