Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1505496 > unrolled thread
| Started by | Liang Li <liang.z.li@intel.com> |
|---|---|
| First post | 2016-10-21 08:40 +0200 |
| Last post | 2016-10-25 03:30 +0200 |
| Articles | 3 — 3 participants |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
[RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn Liang Li <liang.z.li@intel.com> - 2016-10-21 08:40 +0200
Re: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn Dave Hansen <dave.hansen@intel.com> - 2016-10-24 19:00 +0200
RE: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn "Li, Liang Z" <liang.z.li@intel.com> - 2016-10-25 03:30 +0200
| From | Liang Li <liang.z.li@intel.com> |
|---|---|
| Date | 2016-10-21 08:40 +0200 |
| Subject | [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn |
| Message-ID | <suBEJ-1Rz-15@gated-at.bofh.it> |
Expose the function to get the max pfn, so it can be used in the
virtio-balloon device driver. Simply include the 'linux/bootmem.h'
is not enough, if the device driver is built to a module, directly
refer the max_pfn lead to build failed.
Signed-off-by: Liang Li <liang.z.li@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Mel Gorman <mgorman@techsingularity.net>
Cc: Michael S. Tsirkin <mst@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Amit Shah <amit.shah@redhat.com>
---
include/linux/mm.h | 1 +
mm/page_alloc.c | 10 ++++++++++
2 files changed, 11 insertions(+)
diff --git a/include/linux/mm.h b/include/linux/mm.h
index ffbd729..2a89da0e 100644
--- a/include/linux/mm.h
+++ b/include/linux/mm.h
@@ -1776,6 +1776,7 @@ static inline spinlock_t *pmd_lock(struct mm_struct *mm, pmd_t *pmd)
extern void free_area_init_node(int nid, unsigned long * zones_size,
unsigned long zone_start_pfn, unsigned long *zholes_size);
extern void free_initmem(void);
+extern unsigned long get_max_pfn(void);
/*
* Free reserved pages within range [PAGE_ALIGN(start), end & PAGE_MASK)
diff --git a/mm/page_alloc.c b/mm/page_alloc.c
index 2b3bf67..e5f63a9 100644
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -4426,6 +4426,16 @@ void show_free_areas(unsigned int filter)
show_swap_cache_info();
}
+/*
+ * The max_pfn can change because of memory hot plug, so it's only good
+ * as a hint. e.g. for sizing data structures.
+ */
+unsigned long get_max_pfn(void)
+{
+ return max_pfn;
+}
+EXPORT_SYMBOL(get_max_pfn);
+
static void zoneref_set_zone(struct zone *zone, struct zoneref *zoneref)
{
zoneref->zone = zone;
--
1.8.3.1
[toc] | [next] | [standalone]
| From | Dave Hansen <dave.hansen@intel.com> |
|---|---|
| Date | 2016-10-24 19:00 +0200 |
| Subject | Re: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn |
| Message-ID | <svQLp-1O1-47@gated-at.bofh.it> |
| In reply to | #1505496 |
On 10/20/2016 11:24 PM, Liang Li wrote: > Expose the function to get the max pfn, so it can be used in the > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > is not enough, if the device driver is built to a module, directly > refer the max_pfn lead to build failed. I'm not sure the rest of the set is worth reviewing. I think a lot of it will change pretty fundamentally once you have those improved data structures in place.
[toc] | [prev] | [next] | [standalone]
| From | "Li, Liang Z" <liang.z.li@intel.com> |
|---|---|
| Date | 2016-10-25 03:30 +0200 |
| Subject | RE: [RESEND PATCH v3 kernel 3/7] mm: add a function to get the max pfn |
| Message-ID | <svYIV-76i-1@gated-at.bofh.it> |
| In reply to | #1507459 |
> On 10/20/2016 11:24 PM, Liang Li wrote: > > Expose the function to get the max pfn, so it can be used in the > > virtio-balloon device driver. Simply include the 'linux/bootmem.h' > > is not enough, if the device driver is built to a module, directly > > refer the max_pfn lead to build failed. > > I'm not sure the rest of the set is worth reviewing. I think a lot of it will > change pretty fundamentally once you have those improved data structures > in place. That's true. I will send out the v4 as soon as possible. Liang
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web