linux-kernel - Re: [Xen-devel] [PATCH] xen: remove unused Kconfig parameter

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: <51DC406202000078000E39B2@nat28.tlf.novell.com>
Date:	Tue, 09 Jul 2013 15:54:58 +0100
From:	"Jan Beulich" <JBeulich@...e.com>
To:	"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>
Cc:	"Borislav Petkov" <bp@...en8.de>, "Matt Wilson" <msw@...zon.com>,
	"Michael Opdenacker" <michael.opdenacker@...e-electrons.com>,
	<jeremy@...p.org>, <x86@...nel.org>, <tglx@...utronix.de>,
	<virtualization@...ts.linux-foundation.org>,
	<xen-devel@...ts.xensource.com>, <mingo@...hat.com>,
	"Paul Bolle" <pebolle@...cali.nl>, <linux-kernel@...r.kernel.org>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] xen: remove unused Kconfig parameter

>>> On 09.07.13 at 16:48, Konrad Rzeszutek Wilk <konrad.wilk@...cle.com> wrote:
> Dom0 has been both - but there is nothing wrong with seperating these
> two labels. And therein I was thinking that the 'hardware backend domain'
> should be the introduced. I am not good with names so the best option
> seems CONFIG_XEN_PRIVILIGED, but that sounds to be like 'controlling 
> domain'.
> 
> Any good ideas for names? CONFIG_XEN_HARDWARE_DOMAIN ? 
> CONFIG_XEN_PRIVILIGED_DOMAIN?

Following the naming in the hypervisor, CONFIG_XEN_HARDWARE_DOMAIN
and CONFIG_XEN_CONTROL_DOMAIN would seem reasonable to me.

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/