how to determine which interrupts enable and which desable?


 
Thread Tools Search this Thread
Operating Systems Linux how to determine which interrupts enable and which desable?
# 1  
Old 09-23-2008
how to determine which interrupts enable and which desable?

hi all.

How can i determine which interrupts are enabled in my machine (x86). I mean
how can i access information about this through my pic/apic, or
how can i see, which interrupt enable? Maybe i can do it through /proc, or /sys?
I writing driver and i think, that i incorrect initialize it, but i wanna be sure,
that interrupt can reach cpu and not stuck in my interrupt controller.

I know that there are /proc/interrupts that don't show intr if now int_handler is installed
and /proc/stat, but i need information from my apic controller, interrupt mask...

In dos, as i know, i can access to 0x21 (or 0x20, i'm not familiar with it) and put
there my interrupt mask and then i can be sure, that my interrupt will be reached
to the cpu...

I have x86, linux 2.6.18.

English is not my native language, so sorry for any gramma
and other errors.
Thanks for advice.

Last edited by kolya; 09-23-2008 at 06:08 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

CPU - Interrupts distribution

Hi Gurus, I have a situation runing my ETL tools on the below server. The throughput while processing data is coming very low. When i tried to analyse the CPU stats i got colleceted the mpstat. Server Physical Host Name *********com IP**.***.** OS Type Linux OS Classlinux red hat... (3 Replies)
Discussion started by: r_t_1601
3 Replies

2. Linux

Convert ssRawInterrupts into Interrupts Per Sec

am doing performance monitoring to our server through snmp. i need to convert the interrupts raw value (ssRawInterrupts) in UCD-SNMP-MIB to per sec (Interrupts/Sec). What is the exact formula to find the above one. Guide me please. Thanks in advance. (1 Reply)
Discussion started by: maruthu
1 Replies

3. Programming

Getting notified in user-space on interrupts

Hi, I'm working on an AMD opteron running Linux 2.6.28.6 I want to preload a module specific register (MSR) with a value to have it overflow after a number of a specific event counts. As I understand, when the counter in the register overflows, an interrupt will be generated and handled by the... (2 Replies)
Discussion started by: mylinuxforums
2 Replies

4. Programming

SIGCHLD interrupts its own handler

Hi. I have a program whose job it is to manage 15 child processes. Sometimes these children die (sometimes deliberately other times with a SEGV). This causes a SIGCHLD to be sent to my program which uses waitpid() in the signal handler to gather information and, in most cases, restart the child.... (3 Replies)
Discussion started by: jrichemont
3 Replies

5. UNIX for Dummies Questions & Answers

about concept of Interrupts.

Hi all, I am new here ,i want to know about interrupts in detail.What r Interrupts .how they r handeled. Thanx in adavnce. (1 Reply)
Discussion started by: vishwasrao
1 Replies

6. UNIX for Dummies Questions & Answers

Traps and Interrupts

Well, I don't know where exactly to ask this doubt so I'm asking in the newbie section. I was reading about traps and interrupts when I thought of traps as something that cease the control of the OS from the user and interrupts that cease the control yet provide support for multitasking. Am I right... (3 Replies)
Discussion started by: Legend986
3 Replies

7. UNIX for Advanced & Expert Users

Interrupts problems

Hi, My machine is a Unixware 7.1.3 is a files server, and I had never problem with that machine, but since two days, the machine presents slows problems, i think that the problem is te device interrupts, I had checked all and I dont found it any problem. Any idea? Thanks, (sorry my... (2 Replies)
Discussion started by: By_Jam
2 Replies

8. UNIX for Dummies Questions & Answers

catching interrupts

hey i have been facing a problem,can you tell me if we can catch ctrl d in unix i have tried and sucessfully catched and disabled ctrl-c and ctrl -z but am not sure if we can do the same for CTRL-D, so got any clue mail on he forum or ...i mean c programming in Unix thats what i am working on (1 Reply)
Discussion started by: toughguy2handle
1 Replies

9. Filesystems, Disks and Memory

Does unix use interrupts?

I'm a freshman here and I have a simple question. Does unix use interrupts which is like Dos? Are they the same? Thx.:cool: (6 Replies)
Discussion started by: Frank_M
6 Replies
Login or Register to Ask a Question
ddi_intr_enable(9F)													       ddi_intr_enable(9F)

NAME
ddi_intr_enable, ddi_intr_block_enable, ddi_intr_disable, ddi_intr_block_disable - enable or disable a given interrupt or range of inter- rupts SYNOPSIS
#include <sys/types.h> #include <sys/conf.h> #include <sys/ddi.h> #include <sys/sunddi.h> int ddi_intr_enable(ddi_intr_handle_t h); int ddi_intr_block_enable(ddi_intr_handle_t *h_array, int count); int ddi_intr_disable(ddi_intr_handle_t h); int ddi_intr_block_disable(ddi_intr_handle_t *h_array, int count); INTERFACE LEVEL
Solaris DDI specific (Solaris DDI). ddi_intr_enable() h DDI interrupt handle ddi_intr_block_enable() h_array Pointer to an array of DDI interrupt handles count Number of interrupts ddi_intr_disable() h DDI interrupt handle ddi_intr_block_disable() h_array Pointer to an array of DDI interrupt handles count Number of interrupts The ddi_intr_enable() function enables the interrupt given by the interrupt handle h. The ddi_intr_block_enable() function enables a range of interrupts given by the count and h_array arguments, where count must be at least 1 and h_array is pointer to a count-sized array of interrupt handles. The ddi_intr_block_enable() function can be used only if the device or host bridge supports the block enable/disable feature. The ddi_intr_get_cap() function returns the RO flag DDI_INTR_FLAG_BLOCK if the device or host bridge supports the interrupt block enable/dis- able feature for the given interrupt type. The ddi_intr_block_enable() function is useful for enabling MSI interrupts when the optional per-vector masking capability is not supported. The ddi_intr_enable() or ddi_intr_block_enable() functions must be called after the required interrupt resources are allocated with ddi_intr_alloc(), the interrupt handlers are added through ddi_intr_add_handler(), and the required locks are initialized by mutex(9F) or rwlock(9F). Once enabled by either of the enable calls, the interrupt can be taken and passed to the driver's interrupt service routine. Enabling an interrupt implies clearing any system or device mask bits associated with the interrupt. The ddi_intr_disable() function disables the interrupt given by the interrupt handle h. The ddi_intr_block_disable() function disables a range of interrupts given by the count and h_array arguments, where count must be at least 1 and h_array is pointer to a count-sized array of interrupt handles. The ddi_intr_block_disable() function can be used only if the device or host bridge supports the block enable/disable feature. The ddi_intr_get_cap() function returns the RO flag DDI_INTR_FLAG_BLOCK if the device or host bridge supports the interrupt block enable/dis- able feature for the given interrupt type. The ddi_intr_block_disable() function is useful for disabling MSI interrupts when the optional per-vector masking capability is not supported. The ddi_intr_disable() or ddi_intr_block_disable() functions must be called before removing the interrupt handler and freeing the corre- sponding interrupt with ddi_intr_remove_handler() and ddi_intr_free(), respectively. The ddi_intr_block_disable() function should be called if the ddi_intr_block_enable() function was used to enable the interrupts. The ddi_intr_enable(), ddi_intr_block_enable(), ddi_intr_disable(), and ddi_intr_block_disable() functions return: DDI_SUCCESS On success. DDI_EINVAL On encountering invalid input parameters. DDI_FAILURE On any implementation specific failure. CONTEXT
The ddi_intr_enable(), ddi_intr_block_enable(), ddi_intr_disable(), and ddi_intr_block_disable() functions can be called from kernel non- interrupt context. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ attributes(5), ddi_intr_add_handler(9F), ddi_intr_alloc(9F), ddi_intr_dup_handler(9F), ddi_intr_free(9F), ddi_intr_get_cap(9F), ddi_intr_remove_handler(9F), mutex(9F), rwlock(9F) Consumers of these interfaces should verify that the return value is not equal to DDI_SUCCESS. Incomplete checking for failure codes could result in inconsistent behavior among platforms. If a device driver that uses MSI and MSI-X interrupts resets the device, the device might reset its configuration space modifications. Such a reset could cause a device driver to lose any MSI and MSI-X interrupt usage settings that have been applied. 22 Apr 2005 ddi_intr_enable(9F)