From: Igor Mammedov <imammedo@redhat.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: Andrew Jones <drjones@redhat.com>,
xen-devel@lists.xensource.com, jeremy@goop.org,
virtualization@lists.linux-foundation.org
Subject: Re: [PATCH 4/4] xen kconfig: describe xen tmem in the config menu
Date: Tue, 24 Jan 2012 09:30:15 +0100 [thread overview]
Message-ID: <4F1E6C17.7060609@redhat.com> (raw)
In-Reply-To: <20120123183454.GA12542@phenom.dumpdata.com>
On 01/23/2012 07:34 PM, Konrad Rzeszutek Wilk wrote:
> On Fri, Jan 06, 2012 at 10:43:11AM +0100, Andrew Jones wrote:
>> Add a description to the config menu for xen tmem.
>
> I am not sure what this patch gets us. If this is to minimize the
> size of the module - so say it gets loaded, but tmem-enabled is
> not set nor cleancache and we just have it consuming memory - we can do it
> via returning -ENODEV on the module load.
But why compile in something that one may never use? At least with this patch
I'll have a choice to turn it off if I don't need it.
For example when I build hardened kernel, I'd like to turn of all unnecessary
features for a particular config (i.e. reduce attack surface as much as possible).
--
Thanks,
Igor
next prev parent reply other threads:[~2012-01-24 8:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-06 9:43 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06 9:43 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones
2012-01-06 9:43 ` [PATCH 2/4] xen kconfig: relax INPUT_XEN_KBDDEV_FRONTEND deps Andrew Jones
2012-01-06 15:46 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-06 15:58 ` Andrew Jones
2012-01-09 7:59 ` Dmitry Torokhov
2012-01-09 10:43 ` [Xen-devel] " Andrew Jones
2012-01-09 17:51 ` [PATCH 2/4 v2] " Andrew Jones
2012-01-11 16:11 ` [Xen-devel] " Konrad Rzeszutek Wilk
2012-01-11 16:29 ` Andrew Jones
2012-03-15 17:23 ` Konrad Rzeszutek Wilk
2012-03-16 6:24 ` Dmitry Torokhov
2012-03-16 14:48 ` Konrad Rzeszutek Wilk
2012-01-23 18:35 ` [PATCH 2/4] " Konrad Rzeszutek Wilk
2012-01-06 9:43 ` [PATCH 3/4] xen kconfig: add dom0 support help text Andrew Jones
2012-01-09 18:07 ` [PATCH 3/4 v2] " Andrew Jones
2012-01-11 15:45 ` [Xen-devel] " Andrew Jones
2012-01-23 18:42 ` [PATCH 3/4] " Konrad Rzeszutek Wilk
2012-01-06 9:43 ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
2012-01-23 18:34 ` Konrad Rzeszutek Wilk
2012-01-24 8:30 ` Igor Mammedov [this message]
2012-01-24 17:38 ` [Xen-devel] " Konrad Rzeszutek Wilk
-- strict thread matches above, loose matches on Subject: below --
2012-01-11 16:19 [Xen-devel] [PATCH] xen: remove CONFIG_XEN_DOM0 compile option Konrad Rzeszutek Wilk
2012-01-11 16:36 ` [PATCH 1/4] xen kconfig: keep XEN_XENBUS_FRONTEND builtin Andrew Jones
2012-01-11 16:36 ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
2012-01-11 17:35 ` Konrad Rzeszutek Wilk
2012-01-12 10:54 ` Andrew Jones
2012-01-06 8:57 [PATCH 0/4] xen kconfig tweaks Andrew Jones
2012-01-06 8:57 ` [PATCH 4/4] xen kconfig: describe xen tmem in the config menu Andrew Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F1E6C17.7060609@redhat.com \
--to=imammedo@redhat.com \
--cc=drjones@redhat.com \
--cc=jeremy@goop.org \
--cc=konrad.wilk@oracle.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).