[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1475503368-22878-1-git-send-email-vkuznets@redhat.com>
Date: Mon, 3 Oct 2016 16:02:48 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: xen-devel@...ts.xenproject.org
Cc: linux-kernel@...r.kernel.org,
Boris Ostrovsky <boris.ostrovsky@...cle.com>,
David Vrabel <david.vrabel@...rix.com>,
Juergen Gross <jgross@...e.com>
Subject: [PATCH RFC] xen: make it possible to disable XEN_TMEM
XEN_TMEM config option has no prompt and it is enabled as module by
default if CLEANCACHE or FRONTSWAP options are set with no way to disable
it. The only in-tree user of the tmem interface is xen-selfballoon which
can itself be disabled so it makes sense to make it possible to disable
XEN_TMEM too. In theory, both these options could be unified under the
XEN_SELFBALLOONING but other (out-of-tree) users of the tmem interface
may exist and someone may want to keep them supported without enabling
XEN_SELFBALLOONING.
Signed-off-by: Vitaly Kuznetsov <vkuznets@...hat.com>
---
- I don't know much about tmem and its users thus RFC.
---
drivers/xen/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/xen/Kconfig b/drivers/xen/Kconfig
index f15bb3b7..0ea1df8 100644
--- a/drivers/xen/Kconfig
+++ b/drivers/xen/Kconfig
@@ -166,7 +166,7 @@ config SWIOTLB_XEN
select SWIOTLB
config XEN_TMEM
- tristate
+ tristate "Transcendent Memory support for Xen"
depends on !ARM && !ARM64
default m if (CLEANCACHE || FRONTSWAP)
help
--
2.7.4
Powered by blists - more mailing lists