From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752815AbcJCOC7 (ORCPT ); Mon, 3 Oct 2016 10:02:59 -0400 Received: from mx1.redhat.com ([209.132.183.28]:47818 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751469AbcJCOCv (ORCPT ); Mon, 3 Oct 2016 10:02:51 -0400 From: Vitaly Kuznetsov To: xen-devel@lists.xenproject.org Cc: linux-kernel@vger.kernel.org, Boris Ostrovsky , David Vrabel , Juergen Gross Subject: [PATCH RFC] xen: make it possible to disable XEN_TMEM Date: Mon, 3 Oct 2016 16:02:48 +0200 Message-Id: <1475503368-22878-1-git-send-email-vkuznets@redhat.com> X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.29]); Mon, 03 Oct 2016 14:02:51 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 --- - 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