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]
Message-ID: <20061113130926.GD7085@osiris.boeblingen.de.ibm.com>
Date:	Mon, 13 Nov 2006 14:09:26 +0100
From:	Heiko Carstens <heiko.carstens@...ibm.com>
To:	Srinivasa Ds <srinivasa@...ibm.com>
Cc:	anton@....ibm.com, paulus@...ba.org, linux-kernel@...r.kernel.org
Subject: Re: [RFC] [PATCH] cpu_hotplug on IBM JS20 system

> Since we are not supported by hardware for cpu hotplug. I have developed
> the patch which will disable cpu hotplug on IBM bladecentre JS20. Please
> let me know your comments on this please.

> +extern  int cpu_hotplug_disabled;
> +extern  struct mutex cpu_add_remove_lock;
[...]
> +	if(rtas_stop_self_args.token == RTAS_UNKNOWN_SERVICE) {
> +		mutex_lock(&cpu_add_remove_lock);
> +		cpu_hotplug_disabled = 1;
> +		mutex_unlock(&cpu_add_remove_lock);
> +	}
> +
>  #endif /* CONFIG_HOTPLUG_CPU */
>  #ifdef CONFIG_RTAS_ERROR_LOGGING
>  	rtas_last_error_token = rtas_token("rtas-last-error");

You should add a function to kernel/cpu.c which you can call in order to
disable cpu hotplug instead of exporting its private data structures.
-
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