calculated when running.
VMALLOC_START depends on the "vmalloc=XXX" parameter which is passed by
bootloader(u-boot). so if you specify a large vmalloc size in bootloader, for
example
"vmalloc=512M", the VMALLOC_START will be reduced accordingly.
the rough formula is as below:
1. def
On Tue, Jun 26, 2012 at 12:41 AM, Dave Hylands wrote:
> Hi Subbu,
>
> On Mon, Jun 25, 2012 at 7:45 PM, Subramaniam Appadodharana
> wrote:
> ...snip...
> >> However, if you call vmalloc and lets suppose that vmalloc just
> >> happens to return 0xE000. The physical address of the first page
>
Hi Subbu,
On Mon, Jun 25, 2012 at 7:45 PM, Subramaniam Appadodharana
wrote:
...snip...
>> However, if you call vmalloc and lets suppose that vmalloc just
>> happens to return 0xE000. The physical address of the first page
>> might be 0xD2345000.
>>
>> What's important is that the physical pag
Hi,
On Mon, Jun 25, 2012 at 9:01 PM, 卜弋天 wrote:
>
>> Suppose your machine has 1 GB of RAM with a physical addresses of
>> 0x4000 thru 0x7FFF
>>
>> Let's suppose that PHYS_OFFSET = 0xC000
>> Let's suppose that VMALLOC_START is set to 0xE000 and VMALLOC_END
>> is at 0xEFFF (256
> Suppose your machine has 1 GB of RAM with a physical addresses of
> 0x4000 thru 0x7FFF
>
> Let's suppose that PHYS_OFFSET = 0xC000
> Let's suppose that VMALLOC_START is set to 0xE000 and VMALLOC_END
> is at 0xEFFF (256 Mb)
>
is this PAGE_OFFSET or PHYS_OFFSET?
> So what w
Hi Dave,
Thank you for taking your time to provide this example. This is indeed very
insightful.
On Mon, Jun 25, 2012 at 7:41 PM, Dave Hylands wrote:
> Hi Subbu,
>
> ...snip,,,
> >> __pa only works on kernel direct addresses.
> >>
> >> __pa doesn't work on the addresses from vmalloc
> >>
> >> U
Hi Subbu,
...snip,,,
>> __pa only works on kernel direct addresses.
>>
>> __pa doesn't work on the addresses from vmalloc
>>
>> Using __pa on VMALLOC_START or VMALLOC_END doesn't really make sense.
>> If there were any physical memory there, it would be highmem.
>>
> Okay, but my intention was to
;>
> >> Hi :)
> >>
> >> On Sun, Jun 24, 2012 at 1:32 AM, Subramaniam Appadodharana
> >> wrote:
> >> > Hi All,
> >> > I am trying to understand how vmalloc memory is reserved in kernel. In
> >> > 3.4+
> >> >
,
>> > I am trying to understand how vmalloc memory is reserved in kernel. In
>> > 3.4+
>> > latest kernel, the default vmalloc size is 240MB.
>>
>> vmalloc reserved address range, you meant?
>>
>> >Is this a carveout from
>> > the 1G
On Mon, Jun 25, 2012 at 1:00 PM, Mulyadi Santosa
wrote:
> Hi :)
>
> On Sun, Jun 24, 2012 at 1:32 AM, Subramaniam Appadodharana
> wrote:
> > Hi All,
> > I am trying to understand how vmalloc memory is reserved in kernel. In
> 3.4+
> > latest kernel,
Hi :)
On Sun, Jun 24, 2012 at 1:32 AM, Subramaniam Appadodharana
wrote:
> Hi All,
> I am trying to understand how vmalloc memory is reserved in kernel. In 3.4+
> latest kernel, the default vmalloc size is 240MB.
vmalloc reserved address range, you meant?
>Is this a carveout fro
Hi All,
I am trying to understand how vmalloc memory is reserved in kernel. In 3.4+
latest kernel, the default vmalloc size is 240MB. Is this a carveout from
the 1GiB memory that kernel has?
In other words can I do a __pa(VMALLOC_START) or __pa(VMALLOC_END)
or __pa(highmemory) irrespective of the
12 matches
Mail list logo
