Re: [PATCH v7 0/15] MR7516: Server-side thread priorities implementation (Part 3)

[Marc-Aurel Zent (＠mzent)]

On Tue Mar 18 15:03:51 2025 +0000, Rémi Bernon wrote:
> I haven't found neither the PROCESS_PRIOCLASS nor the
> PROCESS_PRIORITY_CLASS constants in the SDK headers, where are you
> seeing them?
> I was originally looking into that since the reported process base priority was not matching what windows reported and they were set to these values, so I thought they were wrong (which turned out to be not true for a different reason...).

In any case, [System Informer](https://systeminformer.sourceforge.io), which is luckily open-source and MIT licensed, displays them like so:

```
static CONST PH_KEY_VALUE_PAIR ProcessPriorityClassTypePairs[] =
{
    SIP(SREF(L"Unknown"), PROCESS_PRIORITY_CLASS_UNKNOWN),
    SIP(SREF(L"Idle"), PROCESS_PRIORITY_CLASS_IDLE),
    SIP(SREF(L"Normal"), PROCESS_PRIORITY_CLASS_NORMAL),
    SIP(SREF(L"High"), PROCESS_PRIORITY_CLASS_HIGH),
    SIP(SREF(L"Real time"), PROCESS_PRIORITY_CLASS_REALTIME),
    SIP(SREF(L"Below normal"), PROCESS_PRIORITY_CLASS_BELOW_NORMAL),
    SIP(SREF(L"Above normal"), PROCESS_PRIORITY_CLASS_ABOVE_NORMAL),
};
```

A quick GitHub code search shows that these are used like so in a wide range of projects, whereas the current Wine naming of `PROCESS_PROCLASS_*` is basically only used by Wine.

This also adds the unknown case and starts from `0`, which are both nice-to-haves, and leads me to believe that this is also the original private API naming scheme. If this is still not worth it to do, I can also just drop the commit as well.

-- 
https://gitlab.winehq.org/wine/wine/-/merge_requests/7516#note_98393