Bug fix if no NUMA support in kernel

[lubinszARM]

After testing for edge devices with minimal kernel configuration(without numa),
I think we should report coreId = threadId/nodeId=0 if found error.

Signed-off-by: Bin Lu bin.lu@arm.com

[k8s-ci-robot]

Hi @lubinszARM. Thanks for your PR.

I'm waiting for a google or kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[dashpole]

/ok-to-test
What is the effect of reporting coreId = threadId/nodeId=0? Can you expand on that a little bit?

[lubinszARM]

/ok-to-test
What is the effect of reporting coreId = threadId/nodeId=0? Can you expand on that a little bit?

Just same with the topology of 'no numa'.

On a non-numa board, coreId = threadId = physical-cpu-id. And only contains node 0.

[dashpole]

lgtm