linux-kernel - Re: [PATCH 2/2] xen: remove bm_rld_set of xen_processor

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: <51ADBDC402000078000DAF36@nat28.tlf.novell.com>
Date:	Tue, 04 Jun 2013 09:13:24 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"liguang" <lig.fnst@...fujitsu.com>,
	"Stefano Stabellini" <stefano.stabellini@...citrix.com>,
	"Len Brown" <lenb@...nel.org>,
	"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Jeremy Fitzhardinge" <jeremy@...p.org>,
	"Liu Jinsong" <jinsong.liu@...el.com>,
	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
	<virtualization@...ts.linux-foundation.org>,
	<xen-devel@...ts.xensource.com>, <linux-acpi@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/2] xen: remove bm_rld_set of xen_processor_flags

>>> On 04.06.13 at 10:05, liguang <lig.fnst@...fujitsu.com> wrote:
> bm_rld_set seems obsolete now
> 
> Signed-off-by: liguang <lig.fnst@...fujitsu.com>
> ---
>  include/xen/interface/platform.h |    1 -
>  1 files changed, 0 insertions(+), 1 deletions(-)
> 
> diff --git a/include/xen/interface/platform.h 
> b/include/xen/interface/platform.h
> index c57d5f6..7ffff33 100644
> --- a/include/xen/interface/platform.h
> +++ b/include/xen/interface/platform.h
> @@ -240,7 +240,6 @@ struct xen_processor_flags {
>  	uint32_t bm_check:1;
>  	uint32_t has_cst:1;
>  	uint32_t power_setup_done:1;
> -	uint32_t bm_rld_set:1;
>  };
>  
>  struct xen_processor_power {

Any such patch would need to be submitted against the master copy
of the header (in the Xen repo), and by recognizing that you'd also
notice that this is part of a public ABI, and hence can't be removed,
but at best can be documented as obsolete. Of course you'd first
need to check whether the hypervisor makes any use of that bit
when passed down from Dom0.

Jan

--
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/