Re: Freeze due to performance_cx_lowest=LOW



on 29/05/2006 23:10 Nate Lawson said the following:

disable apic (hint.apic.0.disabled="1"). I isolated this a little while
ago to the change to enable LAPIC timer. However, there is currently no
easy way to disable the LAPIC timer with APIC enabled so you have to
disable APIC. jhb@ and I have been discussing how to do this better but
no easy answers apparently.

I am not sure what I am talking about, but is it potentially possible to
drive timer system by more than one clock, actively using the most
precise of them at any particular moment ? So that if LAPIC timer stops
i8254 can be used instead.


--
Andriy Gapon
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"



Relevant Pages

  • Re: Freeze due to performance_cx_lowest=LOW
    ... ago to the change to enable LAPIC timer. ... possible to drive hardclock with two interrupts (I haven't thought yet ... 8254 timer/IRQ0 and can be used without mixed mode. ...
    (freebsd-current)
  • Re: Freeze due to performance_cx_lowest=LOW
    ... Andriy Gapon wrote: ... ago to the change to enable LAPIC timer. ... there is currently no easy way to disable the LAPIC timer with APIC enabled so you have to disable APIC. ... jhb@ and I have been discussing how to do this better but no easy answers apparently. ...
    (freebsd-current)
  • Re: Freeze due to performance_cx_lowest=LOW
    ... ago to the change to enable LAPIC timer. ... That requires mixed mode delivery -- i8254 on legacy PIC irq and APIC ... jhb@ just killed this and isn't eager to add ...
    (freebsd-current)