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  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, 24 Jul 2014 09:12:13 -0000
To:	"Viresh Kumar" <>
Cc:	"Saravana Kannan" <>,
	"Rafael J. Wysocki" <>,
	"Todd Poynor" <>,
	"" <>,
	"Linux Kernel Mailing List" <>,
	"" <>,
Subject: Re: [PATCH] cpufreq: Don't destroy/realloc policy/sysfs on

Viresh Kumar wrote:
> On 24 July 2014 08:32, Saravana Kannan <> wrote:
>> Ok, I think I've figured this out. But one question. Is it possible to
>> physically remove one CPU in a bunch of "related cpus" without also
>> unplugging the rest? Put another way, can you unplug one core from a
>> cluster?
> Are we talking about doing this here:
> echo 0 > /sys/devices/system/cpu/cpuX/online      ??
> If yes, then what's the confusion all about? Yes we do it all the time.

No. That's why I said physically remove.

The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
hosted by The Linux Foundation

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists