Linux has support for free page reporting now (36e66c554b5c) for
virtualized environment. On Hyper-V when virtually backed VMs are
configured, Hyper-V will advertise cold memory discard capability,
when supported. This patch adds the support to hook into the free
page reporting infrastructure and leverage the Hyper-V cold memory
discard hint hypercall to report/free these pages back to the host.
Signed-off-by: Sunil Muthuswamy <redacted>
---
First patch mail bounced backed. Sending it again with the email
addresses fixed.
---
arch/x86/hyperv/hv_init.c | 24 ++++++++
arch/x86/kernel/cpu/mshyperv.c | 6 +-
drivers/hv/hv_balloon.c | 93 +++++++++++++++++++++++++++++++
include/asm-generic/hyperv-tlfs.h | 29 ++++++++++
include/asm-generic/mshyperv.h | 2 +
5 files changed, 152 insertions(+), 2 deletions(-)
@@ -1565,6 +1570,83 @@ static void balloon_onchannelcallback(void *context)}+#ifdef CONFIG_PAGE_REPORTING+staticinthv_free_page_report(structpage_reporting_dev_info*pr_dev_info,+structscatterlist*sgl,unsignedintnents)+{+unsignedlongflags;+structhv_memory_hint*hint;+inti;+u64status;+structscatterlist*sg;++WARN_ON(nents>HV_MAX_GPA_PAGE_RANGES);+local_irq_save(flags);+hint=*(structhv_memory_hint**)this_cpu_ptr(hyperv_pcpu_input_arg);+if(!hint){+local_irq_restore(flags);+return-ENOSPC;+}++hint->type=HV_EXT_MEMORY_HEAT_HINT_TYPE_COLD_DISCARD;+hint->reserved=0;+for(i=0,sg=sgl;sg;sg=sg_next(sg),i++){+intorder;+unionhv_gpa_page_range*range;++order=get_order(sg->length);+range=&hint->ranges[i];+range->address_space=0;+range->page.largepage=1;+range->page.additional_pages=(1ull<<(order-9))-1;+range->base_large_pfn=page_to_pfn(sg_page(sg))>>9;+}++status=hv_do_rep_hypercall(HV_EXT_CALL_MEMORY_HEAT_HINT,nents,0,+hint,NULL);+local_irq_restore(flags);+status&=HV_HYPERCALL_RESULT_MASK;+if(status!=HV_STATUS_SUCCESS){+pr_err("Cold memory discard hypercall failed with status %llx\n",+status);+return-1;+}++return0;+}++staticintenable_page_reporting(void)+{+intret;++if(!(hv_query_ext_cap()&+HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT)){+pr_info("Cold memory discard hint not supported by Hyper-V\n");+return0;+}++BUILD_BUG_ON(PAGE_REPORTING_CAPACITY>HV_MAX_GPA_PAGE_RANGES);+dm_device.pr_dev_info.report=hv_free_page_report;+ret=page_reporting_register(&dm_device.pr_dev_info);+if(ret<0){+dm_device.pr_dev_info.report=NULL;+pr_err("Failed to enable cold memory discard: %d\n",ret);+}else{+pr_info("Cold memory discard hint enabled\n");+}++returnret;+}++staticvoiddisable_page_reporting(void)+{+if(dm_device.pr_dev_info.report){+page_reporting_unregister(&dm_device.pr_dev_info);+dm_device.pr_dev_info.report=NULL;+}+}+#endif //CONFIG_PAGE_REPORTING+staticintballoon_connect_vsp(structhv_device*dev){structdm_version_requestversion_req;
@@ -1710,6 +1792,11 @@ static int balloon_probe(struct hv_device *dev,if(ret!=0)returnret;+#ifdef CONFIG_PAGE_REPORTING+if(enable_page_reporting()<0)+gotoprobe_error;+#endif+dm_device.state=DM_INITIALIZED;dm_device.thread=
Linux has support for free page reporting now (36e66c554b5c) for
virtualized environment. On Hyper-V when virtually backed VMs are
configured, Hyper-V will advertise cold memory discard capability,
when supported. This patch adds the support to hook into the free
page reporting infrastructure and leverage the Hyper-V cold memory
discard hint hypercall to report/free these pages back to the host.
Signed-off-by: Sunil Muthuswamy <redacted>
---
First patch mail bounced backed. Sending it again with the email
addresses fixed.
---
arch/x86/hyperv/hv_init.c | 24 ++++++++
arch/x86/kernel/cpu/mshyperv.c | 6 +-
drivers/hv/hv_balloon.c | 93 +++++++++++++++++++++++++++++++
include/asm-generic/hyperv-tlfs.h | 29 ++++++++++
include/asm-generic/mshyperv.h | 2 +
5 files changed, 152 insertions(+), 2 deletions(-)
As the only usage of this function looks like
if (!(hv_query_ext_cap() & HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT))
I would've change the interface to
bool hv_query_ext_cap(u64 cap)
so the usage would look like
if (!(hv_query_ext_cap(HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT))
...
quoted hunk
+ u64 *cap;
+ unsigned long flags;
+ u64 ext_cap = 0;
+
+ /*
+ * Querying extended capabilities is an extended hypercall. Check if the
+ * partition supports extended hypercall, first.
+ */
+ if (!(ms_hyperv.b_features & HV_ENABLE_EXTENDED_HYPERCALLS))
+ return 0;
+
+ local_irq_save(flags);
+ cap = *(u64 **)this_cpu_ptr(hyperv_pcpu_input_arg);
+ if (hv_do_hypercall(HV_EXT_CALL_QUERY_CAPABILITIES, NULL, cap) ==
+ HV_STATUS_SUCCESS)
+ ext_cap = *cap;
+
+ local_irq_restore(flags);
+ return ext_cap;
+}
+EXPORT_SYMBOL_GPL(hv_query_ext_cap);
HYPERV_CPUID_FEATURES(0x40000003) EAX and EBX correspond to Partition
Privilege Flags (TLFS), I'd suggest to take the opportunity and rename
this to something like 'privilege flags low=0x%x high=0x%x'.
Also, I don't quite like 'ms_hyperv.b_features' as I'll always have to
look at what it's being assigned to understand what it holds. I'd even
suggest to rename ms_hyperv.features to ms_hyperv.priv_low and
ms_hyperv.b_features tp ms_hyperv.priv_high. Or maybe even better, pack
them to the same 'u64 ms_hyperv.privileges'.
@@ -490,4 +504,19 @@ struct hv_set_vp_registers_input { } element[]; } __packed;+/*+ * The whole argument should fit in a page to be able to pass to the hypervisor+ * in one hypercall.+ */+#define HV_MAX_GPA_PAGE_RANGES ((PAGE_SIZE - sizeof(u64)) / \+ sizeof(union hv_gpa_page_range))+
The name HV_MAX_GPA_PAGE_RANGES sounds too generic and I think this is
specific to the HvExtCallMemoryHeatHint hypercall as other hypercalls
may have a different header length.
Why '[1]' and not '[]'? If it was '[]' you could've used 'sizeof(struct
hv_memory_hint)' in HV_MAX_GPA_PAGE_RANGES macro definition instead of
'sizeof(u64)'.
From: Wei Liu <wei.liu@kernel.org> Date: 2020-05-20 09:02:06
On Tue, May 19, 2020 at 06:37:57PM +0000, Sunil Muthuswamy wrote:
quoted hunk
Linux has support for free page reporting now (36e66c554b5c) for
virtualized environment. On Hyper-V when virtually backed VMs are
configured, Hyper-V will advertise cold memory discard capability,
when supported. This patch adds the support to hook into the free
page reporting infrastructure and leverage the Hyper-V cold memory
discard hint hypercall to report/free these pages back to the host.
Signed-off-by: Sunil Muthuswamy <redacted>
---
First patch mail bounced backed. Sending it again with the email
addresses fixed.
---
arch/x86/hyperv/hv_init.c | 24 ++++++++
arch/x86/kernel/cpu/mshyperv.c | 6 +-
drivers/hv/hv_balloon.c | 93 +++++++++++++++++++++++++++++++
include/asm-generic/hyperv-tlfs.h | 29 ++++++++++
include/asm-generic/mshyperv.h | 2 +
5 files changed, 152 insertions(+), 2 deletions(-)
+ if (hv_do_hypercall(HV_EXT_CALL_QUERY_CAPABILITIES, NULL, cap) ==
+ HV_STATUS_SUCCESS)
You're using the input page as the output parameter. Ideally we should
introduce hyperv_pcpu_output_arg page, but that would waste one page per
cpu just for this one call.
So for now I think this setup is fine, but I would like to add the
following comment.
/*
* Repurpose the input_arg page to accept output from Hyper-V for
* now because this is the only call that needs output from the
* hypervisor. It should be fixed properly by introducing an
* output_arg page once we have more places that require output.
*/
HYPERV_CPUID_FEATURES(0x40000003) EAX and EBX correspond to Partition
Privilege Flags (TLFS), I'd suggest to take the opportunity and rename
this to something like 'privilege flags low=0x%x high=0x%x'.
Also, I don't quite like 'ms_hyperv.b_features' as I'll always have to
look at what it's being assigned to understand what it holds. I'd even
suggest to rename ms_hyperv.features to ms_hyperv.priv_low and
ms_hyperv.b_features tp ms_hyperv.priv_high. Or maybe even better, pack
them to the same 'u64 ms_hyperv.privileges'.
+ if (hv_do_hypercall(HV_EXT_CALL_QUERY_CAPABILITIES, NULL, cap) ==
+ HV_STATUS_SUCCESS)
You're using the input page as the output parameter. Ideally we should
introduce hyperv_pcpu_output_arg page, but that would waste one page per
cpu just for this one call.
So for now I think this setup is fine, but I would like to add the
following comment.
/*
* Repurpose the input_arg page to accept output from Hyper-V for
* now because this is the only call that needs output from the
* hypervisor. It should be fixed properly by introducing an
* output_arg page once we have more places that require output.
*/
Sounds good. Will add it in v2.
quoted
+#ifdef CONFIG_PAGE_REPORTING
+static int hv_free_page_report(struct page_reporting_dev_info *pr_dev_info,
+ struct scatterlist *sgl, unsigned int nents)
+{
+ unsigned long flags;
+ struct hv_memory_hint *hint;
+ int i;
+ u64 status;
+ struct scatterlist *sg;
+
+ WARN_ON(nents > HV_MAX_GPA_PAGE_RANGES);
Should we return -ENOSPC here?
This is more of an assert because PAGE_REPORTING_CAPACITY is set to 32 and has
already been checked that it is < HV_MAX_GPA_PAGE_RANGES in enable_page_reporting.
quoted
+ hint->type = HV_EXT_MEMORY_HEAT_HINT_TYPE_COLD_DISCARD;
+ hint->reserved = 0;
+ for (i = 0, sg = sgl; sg; sg = sg_next(sg), i++) {
+ int order;
+ union hv_gpa_page_range *range;
+
Unfortunately I can't find the semantics of this hypercall in TLFS 6, so
I have a few questions here.
This structure is not specific to this hypercall.
quoted
+ order = get_order(sg->length);
+ range = &hint->ranges[i];
+ range->address_space = 0;
I guess this means all address spaces?
'address_space' is being used here just as a zero initializer for the union. I think the use
of 'address_space' in the definition of hv_gpa_page_range is not appropriate. This struct is
defined in the TLFS 6.0 with the same name, if you want to look it up.
quoted
+ range->page.largepage = 1;
What effect does this have? What if the page is a 4k page?
Page reporting infrastructure doesn't report 4k pages today, but only huge pages (see
PAGE_REPORTING_MIN_ORDER in page_reporting.h). Additionally, the Hyper-V hypervisor
only supports reporting of 2M pages and above. The current code assumes that the minimum
order will be 9 i.e 2M pages and above.
If we feel that this could change in the future, or an implementation detail that should be
protected against, I can add some checks in hv_balloon.c. But, in that case, the ballon driver
should be able to query the page reporting min order somehow, which it is currently, since it is
private.
Alexander, do you have any suggestions or feedback here?
As the only usage of this function looks like
if (!(hv_query_ext_cap() & HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT))
I would've change the interface to
bool hv_query_ext_cap(u64 cap)
so the usage would look like
if (!(hv_query_ext_cap(HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT))
HYPERV_CPUID_FEATURES(0x40000003) EAX and EBX correspond to Partition
Privilege Flags (TLFS), I'd suggest to take the opportunity and rename
this to something like 'privilege flags low=0x%x high=0x%x'.
Also, I don't quite like 'ms_hyperv.b_features' as I'll always have to
look at what it's being assigned to understand what it holds. I'd even
suggest to rename ms_hyperv.features to ms_hyperv.priv_low and
ms_hyperv.b_features tp ms_hyperv.priv_high. Or maybe even better, pack
them to the same 'u64 ms_hyperv.privileges'.
Good idea. I will make the change to rename this to 'priv_high' in v2. I like the idea of
combining 'features' & 'priv_high' to a u64, but that would be a cleanup change and a
separate patch.
Why is largepage always '1'?
I have responded to a similar question by Wei. Page reporting only supports huge pages
and, so does the Hyper-V hypervisor. Let's follow this there.
What is '9'? Could you please define it through PAGE_*/HPAGE_* macro?
Yes, I will define a macro. Essentially, it is to get a count of 2M pages.
Nit: you could've just used
if (status & HV_HYPERCALL_RESULT_MASK != HV_STATUS_SUCCESS) {
Sure, coming in v2.
...
quoted
+ pr_err("Cold memory discard hypercall failed with status %llx\n",
+ status);
+ return -1;
-EFAULT or something like it maybe?
Coming in v2.
quoted
+#ifdef CONFIG_PAGE_REPORTING
+ if (enable_page_reporting() < 0)
+ goto probe_error;
Why? The hyperv-balloon driver itself may still be functional and you
already set dm_device.pr_dev_info.report to NULL.
An error here would reflect an internal error and should not happen and
it was to make it easy to catch such errors, which are otherwise difficult
with just a print. But, the code should follow the general spirit. I will change
this in v2.
The name HV_MAX_GPA_PAGE_RANGES sounds too generic and I think this is
specific to the HvExtCallMemoryHeatHint hypercall as other hypercalls
may have a different header length.
Why '[1]' and not '[]'? If it was '[]' you could've used 'sizeof(struct
hv_memory_hint)' in HV_MAX_GPA_PAGE_RANGES macro definition instead of
'sizeof(u64)'.
From: Alexander Duyck <hidden> Date: 2020-05-22 20:12:11
On Fri, May 22, 2020 at 9:42 AM Sunil Muthuswamy [off-list ref] wrote:
[...]
quoted
quoted
+ order = get_order(sg->length);
+ range = &hint->ranges[i];
+ range->address_space = 0;
I guess this means all address spaces?
'address_space' is being used here just as a zero initializer for the union. I think the use
of 'address_space' in the definition of hv_gpa_page_range is not appropriate. This struct is
defined in the TLFS 6.0 with the same name, if you want to look it up.
quoted
quoted
+ range->page.largepage = 1;
What effect does this have? What if the page is a 4k page?
Page reporting infrastructure doesn't report 4k pages today, but only huge pages (see
PAGE_REPORTING_MIN_ORDER in page_reporting.h). Additionally, the Hyper-V hypervisor
only supports reporting of 2M pages and above. The current code assumes that the minimum
order will be 9 i.e 2M pages and above.
If we feel that this could change in the future, or an implementation detail that should be
protected against, I can add some checks in hv_balloon.c. But, in that case, the ballon driver
should be able to query the page reporting min order somehow, which it is currently, since it is
private.
Alexander, do you have any suggestions or feedback here?
For now we are keeping the limit to order 9 for a couple reasons. The
first being that we don't want to trigger the breaking apart of
transparent huge pages on the host, and the second being for
performance as it is better to report larger pages rather than smaller
ones.
If we were to enable bringing the value down lower we would likely
make it a part of the page reporting dev info structure and would have
to be set at initialization time. That way the device itself could
configure the minimum value. I don't see the value itself being
lowered without adding an option like that since it would likely cause
issues for several different reasons going forward though. If nothing
else you could do a BUILD_BUG_ON that would assert if
PAGE_REPORTING_MIN_ORDER was anything other than the same size as the
"large_page" size referenced above.
What is 9 here? Is there a macro name *ORDER that you can use?
It is to determine the count of 2M pages. I will define a macro.
Is this the only spot where you are using order? Instead of converting
the length to an order why not just divide it by the 2M page size? I
would think that would be faster than having to do something like
having to call get_order on the length? Also instead of using "9" it
might make more sense if you have a define somewhere that says what
"large_page" size actually is. Then you could just divide by that
which should be translated into a shift which is fast and cheap.
From: Michael Kelley <hidden> Date: 2020-05-23 00:40:30
From: Sunil Muthuswamy <redacted> Sent: Friday, May 22, 2020 9:40 AM
quoted
quoted
+ if (hv_do_hypercall(HV_EXT_CALL_QUERY_CAPABILITIES, NULL, cap) ==
+ HV_STATUS_SUCCESS)
You're using the input page as the output parameter. Ideally we should
introduce hyperv_pcpu_output_arg page, but that would waste one page per
cpu just for this one call.
So for now I think this setup is fine, but I would like to add the
following comment.
/*
* Repurpose the input_arg page to accept output from Hyper-V for
* now because this is the only call that needs output from the
* hypervisor. It should be fixed properly by introducing an
* output_arg page once we have more places that require output.
*/
Sounds good. Will add it in v2.
Note that the only real requirement for the output parameter to hypercalls
is that it not cross a page boundary. Since '*cap' is only 64-bits, you can
declare it as a static variable or even as a local on the stack. It will
naturally be aligned (or can add __aligned(8) to be explicit??), so it won't
cross a page boundary. Then you can skip using the per-cpu input arg
altogether, along with the associated local_irq_save()/restore().
Michael
Hi Sunil,
first thank you very much for your work here. I am using this patch in
the latest mainline releases with WSL 2 and it is helping me a lot. Let
me know if you're still interested in continuing to work on this patch.
It would be great to have it included in the mainline. If you need any
help let me know too. I'm including my test tag. Thanks!
Em 5/19/2020 3:37 PM, Sunil Muthuswamy escreveu:
quoted hunk
Linux has support for free page reporting now (36e66c554b5c) for
virtualized environment. On Hyper-V when virtually backed VMs are
configured, Hyper-V will advertise cold memory discard capability,
when supported. This patch adds the support to hook into the free
page reporting infrastructure and leverage the Hyper-V cold memory
discard hint hypercall to report/free these pages back to the host.
Signed-off-by: Sunil Muthuswamy <redacted>
Reported-by: kbuild test robot <redacted>
---
First patch mail bounced backed. Sending it again with the email
addresses fixed.
---
arch/x86/hyperv/hv_init.c | 24 ++++++++
arch/x86/kernel/cpu/mshyperv.c | 6 +-
drivers/hv/hv_balloon.c | 93 +++++++++++++++++++++++++++++++
include/asm-generic/hyperv-tlfs.h | 29 ++++++++++
include/asm-generic/mshyperv.h | 2 +
5 files changed, 152 insertions(+), 2 deletions(-)
@@ -1565,6 +1570,83 @@ static void balloon_onchannelcallback(void *context)}+#ifdef CONFIG_PAGE_REPORTING+staticinthv_free_page_report(structpage_reporting_dev_info*pr_dev_info,+structscatterlist*sgl,unsignedintnents)+{+unsignedlongflags;+structhv_memory_hint*hint;+inti;+u64status;+structscatterlist*sg;++WARN_ON(nents>HV_MAX_GPA_PAGE_RANGES);+local_irq_save(flags);+hint=*(structhv_memory_hint**)this_cpu_ptr(hyperv_pcpu_input_arg);+if(!hint){+local_irq_restore(flags);+return-ENOSPC;+}++hint->type=HV_EXT_MEMORY_HEAT_HINT_TYPE_COLD_DISCARD;+hint->reserved=0;+for(i=0,sg=sgl;sg;sg=sg_next(sg),i++){+intorder;+unionhv_gpa_page_range*range;++order=get_order(sg->length);+range=&hint->ranges[i];+range->address_space=0;+range->page.largepage=1;+range->page.additional_pages=(1ull<<(order-9))-1;+range->base_large_pfn=page_to_pfn(sg_page(sg))>>9;+}++status=hv_do_rep_hypercall(HV_EXT_CALL_MEMORY_HEAT_HINT,nents,0,+hint,NULL);+local_irq_restore(flags);+status&=HV_HYPERCALL_RESULT_MASK;+if(status!=HV_STATUS_SUCCESS){+pr_err("Cold memory discard hypercall failed with status %llx\n",+status);+return-1;+}++return0;+}++staticintenable_page_reporting(void)+{+intret;++if(!(hv_query_ext_cap()&+HV_EXT_CAPABILITY_MEMORY_COLD_DISCARD_HINT)){+pr_info("Cold memory discard hint not supported by Hyper-V\n");+return0;+}++BUILD_BUG_ON(PAGE_REPORTING_CAPACITY>HV_MAX_GPA_PAGE_RANGES);+dm_device.pr_dev_info.report=hv_free_page_report;+ret=page_reporting_register(&dm_device.pr_dev_info);+if(ret<0){+dm_device.pr_dev_info.report=NULL;+pr_err("Failed to enable cold memory discard: %d\n",ret);+}else{+pr_info("Cold memory discard hint enabled\n");+}++returnret;+}++staticvoiddisable_page_reporting(void)+{+if(dm_device.pr_dev_info.report){+page_reporting_unregister(&dm_device.pr_dev_info);+dm_device.pr_dev_info.report=NULL;+}+}+#endif //CONFIG_PAGE_REPORTING+staticintballoon_connect_vsp(structhv_device*dev){structdm_version_requestversion_req;
@@ -1710,6 +1792,11 @@ static int balloon_probe(struct hv_device *dev,if(ret!=0)returnret;+#ifdef CONFIG_PAGE_REPORTING+if(enable_page_reporting()<0)+gotoprobe_error;+#endif+dm_device.state=DM_INITIALIZED;dm_device.thread=