harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey Varlamov (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HARMONY-2154) port_CPUs_number returns incorrect information on EM64T in wow mode
Date Tue, 28 Nov 2006 11:46:22 GMT
    [ http://issues.apache.org/jira/browse/HARMONY-2154?page=comments#action_12453890 ] 
Alexey Varlamov commented on HARMONY-2154:

Diving into MSDN, I found quite similar example which "determines the number of active processor
I played a bit with the suggested port_Cores_number() function on a Xeon box with Windows
2003 SP1 32 bit installed; results appeared somewhat foggy: reported CPU number is 2 but number
of cores is 1, processors either in Hyperthreading or SMT or share a physical package. MSDN
promises there will be more distinctive APIs in Vista.
Anyway, I think we need more clear definition for the port_Cores_number api and better justification
or use case.

> port_CPUs_number returns incorrect information on EM64T in wow mode
> -------------------------------------------------------------------
>                 Key: HARMONY-2154
>                 URL: http://issues.apache.org/jira/browse/HARMONY-2154
>             Project: Harmony
>          Issue Type: Bug
>          Components: DRLVM
>         Environment: msvc, Windows XP
>            Reporter: Rana Dasgupta
>         Assigned To: Alexey Varlamov
>         Attachments: platformapi.patch, platformapi2.patch
> port_CPUs_number uses GetSystemInfo which returns incorrect platform information in emulation
mode. This fix looks for GetNativeSystemInfo in the kernel and uses it if available; if not
uses GetSystemInfo. On native 64 bit mode GetNative SystemInfo delegates to GetSystemInfo.
This, and the way WOW redirection works, enables the correct api to be used in all 32 and
64 bit situations.
> The patch also adds an api port_Cores_number for core counting on 32 and 64 bit platforms.
This is a placeholder implementataion to be extended if we decide to access NUMA or related
information through this api.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message