Re: OTMP & MPRemoteCalls
Re: OTMP & MPRemoteCalls
- Subject: Re: OTMP & MPRemoteCalls
- From: Quinn <email@hidden>
- Date: Fri, 5 Dec 2003 11:05:27 +0000
At 17:04 -0500 4/12/03, Steve Kalkwarf wrote:
I took a whirl through my project's source, and discovered that OTMP.c
passes kMPAnyContext to its MPRemoteCall()s.
Is this actually a problem?
No, and yes.
No, in that Mac OS X ignores the actual value of the context
parameter to MPRemoteCall and always operates as if
kMPOwningProcessRemoteContext had been supplied.
Yes, in that you shouldn't be running that branch of the OTMP code on
Mac OS X. OTMP has two parallel sets of routines, those with the
OTMP prefix and those with the OTMPX prefix. The OTMP routines are
*strictly* for traditional Mac OS. The OTMPX routines are the
routines you should be using on Mac OS X. The OTMPX routines will
dispatch to either OTMP, if you're running on traditional Mac OS, or
real OT, if you're running on Mac OS X.
Executing the OTMP routines is bad because the synchronisation model
that they use only works if interrupts run to completion (which isn't
true on Mac OS X).
S+E
--
Quinn "The Eskimo!" <
http://www.apple.com/developer/>
Apple Developer Technical Support * Networking, Communications, Hardware
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.