This is *totally* not how to do interrupts with Mach. You should be
creating a thread for each interrupt source, and keeping a worklist of
interrupt handlers registered against that source.
Unfortunately, I can't help you with Mach-related things, since I work
for Apple and that'd put me in a conflict-of-interest situation. 8(
> > None of these are newbus items. Interrupt dispatch is not managed by
> > newbus (due to the costs involved). Instead, interrupts are attached
> > with bus_setup_intr, which forwards the interrupt handler and argument
> > to platform-specific code. The resource mananger is involved (since
> > interrupts are a managed resource), and interrupts must be allocated
> > using bus_alloc_resource before being set up.
> >
>
> Could you possibly go over how this works on the i386. Is there a global
> structure that keeps track of all allocated IRQs and interrupt handling
> routines? What I really need, is to find out, where this structure is
> built, so that at this point, I can instead build the structure that xmach
> needs. Or, alternatively, I can wait until that structure is done, and
> then make the xmach structure from that...
>
> Thanks again,
>
> JAn
>
--
... every activity meets with opposition, everyone who acts has his
rivals and unfortunately opponents also. But not because people want
to be opponents, rather because the tasks and relationships force
people to take different points of view. [Dr. Fritz Todt]
V I C T O R Y N O T V E N G E A N C E
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
