Project Home
Project Home
Documents
Documents
Wiki
Wiki
Discussion Forums
Discussions
Project Information
Project Info
Forum Topic - pidin info reporting two processors on a single-core Atom processor: (6 Items)
   
pidin info reporting two processors on a single-core Atom processor  
We are running QNX 6.5.0 base release (not SR1) on an Intel Atom N455 processor.  Our image is using proctno-smp-instr. 
 We are using the smp version because our software can run on a dual core VortexDX3 processor.

Pidin info reports the following on the Atom processor:

# pidin info
CPU:X86 Release:6.5.0  FreeMem:775Mb/1013Mb BootTime:Jan 01 00:00:05 UTC 2002
Processes: 29, Threads: 163
Processor1: 66222 Intel 686 F6M12S10 1668MHz FPU
Processor2: 66222 Intel 686 F6M12S10 1670MHz FPU

Tracelogger shows CPU #2 periodically switching between idle and ready, but never running.

1. Is this a known issue?
2. Are there any bad consequences running this way?
Re: pidin info reporting two processors on a single-core Atom processor  
Do you have hyper threading enabled in your bios?

Jerry Sui | Software Developer | jsui@qnx.com

O:613-595-3758   C:613-240-9239 | www.qnx.com <http://www.qnx.com/>; | QNX
Software Systems
Cisco Support Team email: cisco_support@qnx.com
 








On 2016-05-25, 11:09 AM, "Robert Murrell" <community-noreply@qnx.com>
wrote:

>We are running QNX 6.5.0 base release (not SR1) on an Intel Atom N455
>processor.  Our image is using proctno-smp-instr.  We are using the smp
>version because our software can run on a dual core VortexDX3 processor.
>
>Pidin info reports the following on the Atom processor:
>
># pidin info
>CPU:X86 Release:6.5.0  FreeMem:775Mb/1013Mb BootTime:Jan 01 00:00:05 UTC
>2002
>Processes: 29, Threads: 163
>Processor1: 66222 Intel 686 F6M12S10 1668MHz FPU
>Processor2: 66222 Intel 686 F6M12S10 1670MHz FPU
>
>Tracelogger shows CPU #2 periodically switching between idle and ready,
>but never running.
>
>1. Is this a known issue?
>2. Are there any bad consequences running this way?
>
>
>
>
>_______________________________________________
>
>OSTech
>http://community.qnx.com/sf/go/post116334
>To cancel your subscription to this discussion, please e-mail
>ostech-core_os-unsubscribe@community.qnx.com

Re: pidin info reporting two processors on a single-core Atom processor  
The unit is in a "Do not touch" test right now, but the board user guide says its on by default.  So almost certainly so
.
Re: pidin info reporting two processors on a single-core Atom processor  
You should turn off it then.


Jerry Sui | Software Developer | jsui@qnx.com

O:613-595-3758   C:613-240-9239 | www.qnx.com <http://www.qnx.com/>; | QNX
Software Systems
Cisco Support Team email: cisco_support@qnx.com
 








On 2016-05-26, 12:59 PM, "Robert Murrell" <community-noreply@qnx.com>
wrote:

>The unit is in a "Do not touch" test right now, but the board user guide
>says its on by default.  So almost certainly so.
>
>
>
>
>_______________________________________________
>
>OSTech
>http://community.qnx.com/sf/go/post116344
>To cancel your subscription to this discussion, please e-mail
>ostech-core_os-unsubscribe@community.qnx.com

Re: pidin info reporting two processors on a single-core Atom processor  
Is hyperthreading a problem with QNX 6.5.0?
Re: pidin info reporting two processors on a single-core Atom processor  
It is not a problem with QNX 6.5.0, but qnx is not optimized for
hyperthreading. If the 2 threads are in different processes, there will be
a lot of context switch on the same physical CPU, which is not efficient.
Please see the following link for more information about hyper threading.

https://en.wikipedia.org/wiki/Hyper-threading


Thanks.

Jerry Sui | Software Developer | jsui@qnx.com

O:613-595-3758   C:613-240-9239 | www.qnx.com <http://www.qnx.com/>; | QNX
Software Systems
Cisco Support Team email: cisco_support@qnx.com
 








On 2016-05-27, 8:50 AM, "Robert Murrell" <community-noreply@qnx.com> wrote:

>Is hyperthreading a problem with QNX 6.5.0?
>
>
>
>_______________________________________________
>
>OSTech
>http://community.qnx.com/sf/go/post116348
>To cancel your subscription to this discussion, please e-mail
>ostech-core_os-unsubscribe@community.qnx.com