Changes between Initial Version and Version 1 of Ticket #32, comment 2


Ignore:
Timestamp:
Jan 11, 2016, 12:16:38 AM (9 years ago)
Author:
Valery V. Sedletski

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #32, comment 2

    initial v1  
    3131}}}
    3232
    33 are possible. So, we should use it as CpuId with care, and it may happen that generic implementation may fail because of this (it seems that some places assume that the CpuId starts with 0 and uses consecutive numbers. For example, Number of CPU's )
     33are possible. So, we should use it as CpuId with care, and it may happen that generic implementation may fail because of this (it seems that some places assume that the CpuId starts with 0 and uses consecutive numbers.)
    3434
    35 Also, pure generic implementation seems to be valid for single core only, because RTMpGetMaxCpuId returns RTMpCpuId, i.e., max. CpuId is the current one, which is valid for single CPU only. And we see that
     35Also, pure generic implementation seems to be valid for single core only, because RTMpGetMaxCpuId returns RTMpCpuId, i.e., max. CpuId is the current one, which is valid for single CPU only. The same with RTMpIsCpuOnline, RTMpIsCpuPossible. And we see that
    3636
    3737{{{
    … …  
    3939}}}
    4040
    41 is used in RuntimeR0Drv for OS/2 only. Others use a 'real' implementation.
     41is used in RuntimeR0Drv for OS/2 only. Other OS'es use a 'real' implementation.