not be
allocated. Kernel log also print out warning message as below.
"Truncating RAM at 8000-afff to -af7f (vmalloc region overlap)."
Although it could be solved by state "vmalloc=size" in cmdline but i think
it would be better to change default value to 232 from 240
not be
allocated. Kernel log also print out warning message as below.
"Truncating RAM at 8000-afff to -af7f (vmalloc region overlap)."
Although it could be solved by state "vmalloc=size" in cmdline but i think
it would be better to change default value to 232 from 240
> On Thu, Sep 03, 2015 at 11:24:47AM +0900, Yongtaek Lee wrote:
> > default value of vmalloc_min was set 0xf000 for ARM by commit
> > 0536bdf3. But actually vmalloc_min is 0xef80 not 0xf000.
> >
> > VMALLOC_END - (240 << 20) - VMALLOC_OFFSET)
> &g
> So, if we go and apply your logic to a 1GB system we should resize the
> vmalloc area to 0 bytes in order to avoid RAM truncation without
> CONFIG_HIGHMEM?
As you already know, CONFIG_HIGHMEM option is necessary if RAM is
more than 1GB. So no need to resize vmalloc area to 0.
> Sorry, but the
> Wrong, there is no such "rule".
> If we apply that rule, then if you have 1GB of RAM, it will fill from
> 0xc000 to 0x inclusive. There will be _zero_ bytes of
> vmalloc space. There will be _zero_ bytes of IO mappings. There won't
> even be a vectors page, so the kernel _will_ cr
evice fail
4. kfree
So that address checking is needed to call correct free function.
Signed-off-by: Yongtaek Lee
Reviewed-by: Daniel Stone
Reviewed-by: David Herrmann
Acked-by: David Rientjes
---
drivers/input/evdev.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git
evice fail
4. kfree
So that address checking is needed to call correct free function.
Signed-off-by: Yongtaek Lee
Reviewed-by: Daniel Stone
---
drivers/input/evdev.c |5 -
1 files changed, 4 insertions(+), 1 deletions(-)
diff --git a/drivers/input/evdev.c b/drivers/input/evdev.c
ind
7 matches
Mail list logo
