Re: enabling x87 interrupts



Alexei A. Frounze <spamtrap@xxxxxxxxxx> wrote:
: Wendy E. McCaughrin wrote:
: > Is the 8259A (PIC) still used to enable interrupts? I unmasked bit #2
: > in the master PIC and bit #5 (a.k.a. #13) in the slave PIC it cascades
: > with, to enable FPU interrupts. I have unmasked all 6 exceptions in
: > the FPU's control-word and use STI. Yet, INT 75h is never accessed.

: Nowadays, there's no external FPU chip that would assert interrupts on the
: PIC. The CPU itself handles all the FP instructions. And my bet is that it's
: configured in such a way that you should get exceptions, not interrupts.

: Alex

Thank you,Alex. Actually, for backwards compatibility, Intel says that it
still asserts interrupts on the PIC. From my correspondence with them, they
say that the 6 exceptions should still trigger INT 75h.

.



Relevant Pages

  • Re: Vectored Interrupt Fetch
    ... out that most interrupts and exceptions were heavyweight, ... instead of going through vectored interrupts. ... of "efficient handling of infrequent events", ...
    (comp.arch)
  • Re: Shared Data Problem
    ... Interrupts can viewed as as asynchronous events, ... :while exceptions can be viewed as synchronous events. ... Is there an expressible upper-bound on the reception of a SIGFPE? ... Is there a way of expressing 'fully graduated' in C? ...
    (comp.lang.c)
  • Re: enabling x87 interrupts
    ... in the master PIC and bit #5 in the slave PIC it cascades ... with, to enable FPU interrupts. ... there's no external FPU chip that would assert interrupts on the PIC. ... And my bet is that it's configured in such a way that you should get exceptions, ...
    (comp.lang.asm.x86)
  • [RFC,v2] x86_64: save_args out of line
    ... After this patch, a typical handler looks like this: ... * initial frame state for interrupts (and exceptions without error code) ...
    (Linux-Kernel)
  • Re: Shared Data Problem
    ... Interrupts can viewed as as asynchronous events, ... >:while exceptions can be viewed as synchronous events. ... HW floating-point support, then I expect that the CPU ...
    (comp.lang.c)