* [PATCH RFC] xen: make it possible to disable XEN_TMEM
@ 2016-10-03 14:02 Vitaly Kuznetsov
2016-10-03 14:19 ` [Xen-devel] " Konrad Rzeszutek Wilk
0 siblings, 1 reply; 3+ messages in thread
From: Vitaly Kuznetsov @ 2016-10-03 14:02 UTC (permalink / raw)
To: xen-devel; +Cc: linux-kernel, Boris Ostrovsky, David Vrabel, Juergen Gross
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@redhat.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
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [Xen-devel] [PATCH RFC] xen: make it possible to disable XEN_TMEM
2016-10-03 14:02 [PATCH RFC] xen: make it possible to disable XEN_TMEM Vitaly Kuznetsov
@ 2016-10-03 14:19 ` Konrad Rzeszutek Wilk
2016-10-03 15:18 ` Vitaly Kuznetsov
0 siblings, 1 reply; 3+ messages in thread
From: Konrad Rzeszutek Wilk @ 2016-10-03 14:19 UTC (permalink / raw)
To: Vitaly Kuznetsov
Cc: xen-devel, Juergen Gross, Boris Ostrovsky, linux-kernel, David Vrabel
On Mon, Oct 03, 2016 at 04:02:48PM +0200, Vitaly Kuznetsov wrote:
> 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
And if CONFIG_XEN=y .
> can itself be disabled so it makes sense to make it possible to disable
During boot-time with arguments.
> 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.
I think going the route of XEN_SELFBALLOONING may be better.
>
> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.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
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [Xen-devel] [PATCH RFC] xen: make it possible to disable XEN_TMEM
2016-10-03 14:19 ` [Xen-devel] " Konrad Rzeszutek Wilk
@ 2016-10-03 15:18 ` Vitaly Kuznetsov
0 siblings, 0 replies; 3+ messages in thread
From: Vitaly Kuznetsov @ 2016-10-03 15:18 UTC (permalink / raw)
To: Konrad Rzeszutek Wilk
Cc: xen-devel, Juergen Gross, Boris Ostrovsky, linux-kernel, David Vrabel
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> writes:
> On Mon, Oct 03, 2016 at 04:02:48PM +0200, Vitaly Kuznetsov wrote:
>> 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
>
> And if CONFIG_XEN=y .
>
Yes, of course)
>> can itself be disabled so it makes sense to make it possible to disable
>
> During boot-time with arguments.
I see, I rather meant we need a way to disable building the module, not
just loading it.
>> 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.
>
> I think going the route of XEN_SELFBALLOONING may be better.
Ok, if you say so)
>>
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.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
>>
>>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xen.org
>> https://lists.xen.org/xen-devel
--
Vitaly
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-10-03 15:18 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-10-03 14:02 [PATCH RFC] xen: make it possible to disable XEN_TMEM Vitaly Kuznetsov
2016-10-03 14:19 ` [Xen-devel] " Konrad Rzeszutek Wilk
2016-10-03 15:18 ` Vitaly Kuznetsov
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).