This is correct, and you should take an interrupt every 10ms in any
Interesting values to print are the master mask, master pending,
pending_sel, and the words in the pend and mask arrays that contain
the bits for the event channel that you are interested in.
(Remember that the event channel will have a different index to the
> OK, some more data.
> in a timer interrupt (first and only) I see this:
> xentimerread: hz 0 cpu_hz 598736060 shadow_system_time 333ac5398180
> settin timer to 0x333bfecedc00
> So the time is 333ac5398180, I set the timer to 0x333bfecedc00 via
> HYPERVISOR_set_timer_op. I'm assuming that once the system time gets to
> 0x333bfecedc00 then I'll get an interrupt.
> Now we wait ... in this loop, I'm print time and the values of the mask,
> the pending, and the pending_sel values in shared info:
> ipending: @0x333bfe262600 islo 0x0, pending 0x0, pending_sel 0x0
> ipending: @0x333bfebebc80 islo 0x0, pending 0x0, pending_sel 0x0
> ipending: @0x333bff575300 islo 0x0, pending 0x0, pending_sel 0x0
> ipending: @0x333bffefe980 islo 0x0, pending 0x0, pending_sel 0x0
> ipending: @0x333c00888000 islo 0x0, pending 0x0, pending_sel 0x0
> note that there is no changing in pending as we cross the time for an
> interrupt to have happened. I would expect to see pending to get set to
> some non-zero value once the system time had passed 0x333bfecedc00.
> My reading of HYPERVISOR_set_timer_op is that you set an absolute value,
> and when the time is > than that value, you get called with an interrupt;
> is that wrong?
> LANL CCS-1 email flavor:
> ***** Correspondence 
> ***** DUSA LACSI-HW [ ]
> ***** DUSA LACSI-OS [x ]
> ***** DUSA LACSI-CS [ ]
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
Xen-devel mailing list