lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Thu, 16 Jun 2011 11:44:30 +0200
From:	Vincent Guittot <vincent.guittot@...aro.org>
To:	Samuel Thibault <samuel.thibault@...-lyon.org>,
	Vincent Guittot <vincent.guittot@...aro.org>,
	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linaro-dev@...ts.linaro.org
Subject: Re: [RFC] Add Arm cpu topology definition

On 16 June 2011 10:55, Samuel Thibault <samuel.thibault@...-lyon.org> wrote:
> Hello,
>
> Vincent Guittot, le Thu 16 Jun 2011 10:49:13 +0200, a écrit :
>> The affinity between Arm processors is defined in the MPIDR register.
>> We can identify which processors are in the same cluster,
>> and which ones have performance interdependency. The cpu topology
>>  of an Arm platform can be set thanks to this register and this topology
>> is then used by sched_mc and sched_smt.
>
> Cool!  Could you check that the hwloc tool gets also gets this
> information from userland through /sys, and/or send me the output of the
> hwloc-gather-topology tool from hwloc so we can add an testcase for
> this?
>

The output of hwloc-gather-topology is :

Machine (phys=0 local=280840KB total=280840KB)
  Socket #0 (phys=3)
    Core #0 (phys=0)
      PU #0 (phys=0)
    Core #1 (phys=1)
      PU #1 (phys=1)
depth 0:        1 Machine (type #1)
 depth 1:       1 Socket (type #3)
  depth 2:      2 Cores (type #5)
   depth 3:     2 PUs (type #6)
Topology not from this system

let me know if it's what you want

> Samuel
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ