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:	Tue, 26 Aug 2014 19:08:53 +0200
From:	David Herrmann <dh.herrmann@...il.com>
To:	Sudeep Holla <sudeep.holla@....com>
Cc:	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Heiko Carstens <heiko.carstens@...ibm.com>,
	Lorenzo Pieralisi <Lorenzo.Pieralisi@....com>,
	Stephen Boyd <sboyd@...eaurora.org>, Kay Sievers <kay@...y.org>
Subject: Re: [PATCH] drivers: base: add cpu_device_create to support per-cpu devices

Hi

On Tue, Aug 26, 2014 at 6:54 PM, Sudeep Holla <sudeep.holla@....com> wrote:
>> Yes, it's not done on purpose as mentioned in the commit log.
>> E.g.: cacheinfo topology will be as below
>>
>> /sys/devices/system/cpu/cpuX/cache/index0/<attributes>
>> /sys/devices/system/cpu/cpuX/cache/index1/<attributes>
>> ..
>> /sys/devices/system/cpu/cpuX/cache/index<Y/<attributes>
>>
>
> Does the above topology looks fine to you ? Since the parent is set
> properly, not setting bus will not cause any issue to the topology.

Sure, looks fine.

Thanks
David
--
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