summaryrefslogtreecommitdiff
path: root/kexec/firmware_memmap.c
diff options
context:
space:
mode:
authorWANG Chao <chaowang@redhat.com>2014-04-22 10:56:45 +0800
committerSimon Horman <horms@verge.net.au>2014-04-23 09:11:03 +0900
commit02dd785100a64adff80df942a0a1e9de59279b00 (patch)
tree673bf4c70ec0decb3f673b92985e55b1d7332937 /kexec/firmware_memmap.c
parentadf854f76a2cd50f4c8db0142ac8d61a4107ff34 (diff)
x86, cleanup: kexec memory range .end to be inclusive
Later kexec and kdump memory range will be mapped to E820entry. But currently kexec memory range .end field is exclusive while crash memory range is inclusive. Given the fact that the exported proc iomem and sysfs memmap are both inclusive, change kexec memory range .end to be inclusive. Later the unified memory range of both kexec and kdump can use the same E820 filling code. Signed-off-by: WANG Chao <chaowang@redhat.com> Acked-by: Dave Young <dyoung@redhat.com> Tested-by: Linn Crosetto <linn@hp.com> Signed-off-by: Simon Horman <horms@verge.net.au>
Diffstat (limited to 'kexec/firmware_memmap.c')
-rw-r--r--kexec/firmware_memmap.c1
1 files changed, 0 insertions, 1 deletions
diff --git a/kexec/firmware_memmap.c b/kexec/firmware_memmap.c
index 9598933..6be3c7c 100644
--- a/kexec/firmware_memmap.c
+++ b/kexec/firmware_memmap.c
@@ -145,7 +145,6 @@ static int parse_memmap_entry(const char *entry, struct memory_range *range)
range->end = parse_numeric_sysfs(filename);
if (range->end == ULLONG_MAX)
return -1;
- range->end++; /* inclusive vs. exclusive ranges */
/*
* entry/type