Jump to content

KernSerialize16BitDD: Difference between revisions

From EDM2
Created page with "==Synopsis== VOID APIENTRY KernSerialize16BitDD(VOID); ==Description== This will acquire a special kernel spinlock. ==Parameters== None. ==Comments== I think, according to ..."
 
Ak120 (talk | contribs)
mNo edit summary
 
(5 intermediate revisions by 2 users not shown)
Line 1: Line 1:
This will acquire a special kernel spinlock.
==Synopsis==
==Synopsis==
VOID APIENTRY KernSerialize16BitDD(VOID);
VOID APIENTRY KernSerialize16BitDD(VOID);
 
==Description==
This will acquire a special kernel spinlock.


==Parameters==
==Parameters==
Line 9: Line 8:


==Comments==
==Comments==
I think, according to the name, this has to be called before accessing a 16 bit driver. I wonder though, since you supposedly also have to adjust the stack pointer (KernThunkStackTo16), why both functions haven't been joined in a single call.  
It can be possible, according to the name, this has to be called before accessing a 16 bit driver. I wonder though, since you supposedly also have to adjust the stack pointer (KernThunkStackTo16), why both functions haven't been joined in a single call.


[[Category:The OS/2 API Project]]
[[Category:KEE]]

Latest revision as of 12:28, 19 July 2020

This will acquire a special kernel spinlock.

Synopsis

VOID APIENTRY KernSerialize16BitDD(VOID);

Parameters

None.

Comments

It can be possible, according to the name, this has to be called before accessing a 16 bit driver. I wonder though, since you supposedly also have to adjust the stack pointer (KernThunkStackTo16), why both functions haven't been joined in a single call.