181
Programming / Re: New OS/4 kernel :: SVN4227
« on: January 07, 2016, 11:09:38 am »Beyond just that very selfish reason above, here is a more precise one: if the /ST=0 parameter in the ACPI.PSD drive does in fact get ignored, and the authors have set some arbitrary value for the size of the stack, then I would consider this to be a defect. So if the OS4 team patches the binary to actually correct this behaviour then I'm actually questioning why the "core" OS2 maintainer team refuses to fix the code itself?
The case is a bit more complicated. OS/2 kernel offers to PSD very small stack (2672 bytes). It is ok for os2apic.psd and it looks like not enouph for ACPI.PSD. That is why ACPI.PSD does some actions to increase PSD stack offered by the kernel. It is not an easy thing since PSD stack is organized on per processor base. At the same time ACPI.PSD recognizes /ST key to set desirable PSD stack size on user demand. ACPI.PSD does not allow the user to set stack size = 0 (as it is really senseless), but if one finds a way (the patch helps) to set "ST=0", ACPI.PSD will not go through the procedure of increasing PSD stack offered by the kernel.
OS/4 starting from svn ver 4250 has unified PSD/interrupt stack with 12k size thus ACPI.PSD has no need to increase it. At the same time, "not easy" ASPI.PSD procedure for increasing PSD stack, simply spoils internal data structure of OS/4 kernel. That is way ACPI.PSD has to be patched and /ST=0 has to be used in order to work with OS/4.
)
I really missed that.