RFR: 8243961: ForceNUMA and only one available NUMA node fails assertion on Windows

[Thomas Schatzl]

And again...

On 30.04.20 12:27, Thomas Schatzl wrote:
> Hi again,
> 
> On 30.04.20 12:24, Thomas Schatzl wrote:
>> Hi,
>>
>> On 29.04.20 14:28, Kim Barrett wrote:
>>> Please review this Windows-specific change to the initialization of
>>> UseNUMAInterleaving.
> [...]
>> Some collectors (Z, Shenandoah) will set UseNUMA, but this evaluation 
>> is before os::init_2 so above idea would do the right thing as neither 
>> have any special UseNUMA path. I.e. both actually seem to want 
>> UseNUMAInterleaving. Shenandoah explicitly says so, so actually 
>> changing them to enable UseNUMAInterleaving instead of UseNUMA would 
>> be good too imo.
>>
>> On non-Windows there will be no difference to now.
>>
> 
>    this would probably also fix the bug described in 
> https://mail.openjdk.java.net/pipermail/shenandoah-dev/2019-August/010991.html 
> for Shenandoah which Z also suffers from.
> 

  Z uses its own memory reservation code, so it is not affected.

Thanks,
   Thomas