Bug 1283835 - when call local_irq_disable(); to block local cpu from all hard irq, it goes wrong!
when call local_irq_disable(); to block local cpu from all hard irq, it goes ...
Status: CLOSED NOTABUG
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: realtime-kernel (Show other bugs)
3.1
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Red Hat Real Time Maintenance
MRG Quality Engineering
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-11-19 23:25 EST by lingfei
Modified: 2015-11-20 10:04 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-11-20 10:04:34 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
546755767: needinfo+


Attachments (Terms of Use)

  None (edit)
Description lingfei 2015-11-19 23:25:43 EST
Description of problem:
when shielding a specific CPU from handling with IRQs in  real time program

Version-Release number of selected component (if applicable):
Redhat-6.7 3.10.0-229.rt56.161.el6rt.x86_64

How reproducible:
Write a time time program 

Steps to Reproduce:
1.#include<linux/irqflags.h>
2.Call some thread functions in main();.
3.Set the thread affinition on a specific cpu.  
3.Call local_irq_disable(); to shield local cpu from dealing with hard irq in  
a thread function.
4.Compile it.
Actual results:
**/3.10.0-229.rt56.161.el6rt.x86_64/include/asm-generic/irqflags.h:46: undefined reference to `arch_local_irq_restore(unsigned long)'

Expected results:
with no error;

Additional info:
I just the arch_local_irq_restore(unsigned long); declared but definited in the file ,where it goes?
Comment 1 Clark Williams 2015-11-20 10:04:34 EST
The irqflags header file is for kernel use only; it is not for use by an application program. 

Application programs cannot disable interrupts.

Note You need to log in before you can comment on or make changes to this bug.