Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
openanolis
cloud-kernel
提交
249f6d9e
cloud-kernel
项目概览
openanolis
/
cloud-kernel
1 年多 前同步成功
通知
160
Star
36
Fork
7
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
10
列表
看板
标记
里程碑
合并请求
2
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
cloud-kernel
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
10
Issue
10
列表
看板
标记
里程碑
合并请求
2
合并请求
2
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
提交
249f6d9e
编写于
10月 16, 2008
作者:
T
Thomas Gleixner
提交者:
Ingo Molnar
10月 16, 2008
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
x86: move ack_bad_irq() to irq.c
Share more duplicated code. Signed-off-by:
N
Thomas Gleixner
<
tglx@linutronix.de
>
上级
6b39ba77
变更
3
隐藏空白更改
内联
并排
Showing
3 changed file
with
23 addition
and
43 deletion
+23
-43
arch/x86/kernel/irq.c
arch/x86/kernel/irq.c
+23
-0
arch/x86/kernel/irq_32.c
arch/x86/kernel/irq_32.c
+0
-23
arch/x86/kernel/irq_64.c
arch/x86/kernel/irq_64.c
+0
-20
未找到文件。
arch/x86/kernel/irq.c
浏览文件 @
249f6d9e
...
...
@@ -12,6 +12,29 @@
atomic_t
irq_err_count
;
/*
* 'what should we do if we get a hw irq event on an illegal vector'.
* each architecture has to answer this themselves.
*/
void
ack_bad_irq
(
unsigned
int
irq
)
{
printk
(
KERN_ERR
"unexpected IRQ trap at vector %02x
\n
"
,
irq
);
#ifdef CONFIG_X86_LOCAL_APIC
/*
* Currently unexpected vectors happen only on SMP and APIC.
* We _must_ ack these because every local APIC has only N
* irq slots per priority level, and a 'hanging, unacked' IRQ
* holds up an irq slot - in excessive cases (when multiple
* unexpected vectors occur) that might lock up the APIC
* completely.
* But only ack when the APIC is enabled -AK
*/
if
(
cpu_has_apic
)
ack_APIC_irq
();
#endif
}
#ifdef CONFIG_X86_32
# define irq_stats(x) (&per_cpu(irq_stat,x))
#else
...
...
arch/x86/kernel/irq_32.c
浏览文件 @
249f6d9e
...
...
@@ -25,29 +25,6 @@ EXPORT_PER_CPU_SYMBOL(irq_stat);
DEFINE_PER_CPU
(
struct
pt_regs
*
,
irq_regs
);
EXPORT_PER_CPU_SYMBOL
(
irq_regs
);
/*
* 'what should we do if we get a hw irq event on an illegal vector'.
* each architecture has to answer this themselves.
*/
void
ack_bad_irq
(
unsigned
int
irq
)
{
printk
(
KERN_ERR
"unexpected IRQ trap at vector %02x
\n
"
,
irq
);
#ifdef CONFIG_X86_LOCAL_APIC
/*
* Currently unexpected vectors happen only on SMP and APIC.
* We _must_ ack these because every local APIC has only N
* irq slots per priority level, and a 'hanging, unacked' IRQ
* holds up an irq slot - in excessive cases (when multiple
* unexpected vectors occur) that might lock up the APIC
* completely.
* But only ack when the APIC is enabled -AK
*/
if
(
cpu_has_apic
)
ack_APIC_irq
();
#endif
}
#ifdef CONFIG_DEBUG_STACKOVERFLOW
/* Debugging check for stack overflow: is there less than 1KB free? */
static
int
check_stack_overflow
(
void
)
...
...
arch/x86/kernel/irq_64.c
浏览文件 @
249f6d9e
...
...
@@ -18,26 +18,6 @@
#include <asm/idle.h>
#include <asm/smp.h>
/*
* 'what should we do if we get a hw irq event on an illegal vector'.
* each architecture has to answer this themselves.
*/
void
ack_bad_irq
(
unsigned
int
irq
)
{
printk
(
KERN_WARNING
"unexpected IRQ trap at vector %02x
\n
"
,
irq
);
/*
* Currently unexpected vectors happen only on SMP and APIC.
* We _must_ ack these because every local APIC has only N
* irq slots per priority level, and a 'hanging, unacked' IRQ
* holds up an irq slot - in excessive cases (when multiple
* unexpected vectors occur) that might lock up the APIC
* completely.
* But don't ack when the APIC is disabled. -AK
*/
if
(
!
disable_apic
)
ack_APIC_irq
();
}
#ifdef CONFIG_DEBUG_STACKOVERFLOW
/*
* Probabilistic stack overflow check:
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录