* question about iotable_init( ) function
[not found] <35FD53F367049845BC99AC72306C23D19441BF586F@CNBJMBX05.corpusers.net>
@ 2013-07-01 9:27 ` Will Deacon
2013-07-01 9:30 ` Wang, Yalin
0 siblings, 1 reply; 2+ messages in thread
From: Will Deacon @ 2013-07-01 9:27 UTC (permalink / raw)
To: linux-arm-kernel
On Mon, Jul 01, 2013 at 08:31:38AM +0100, Wang, Yalin wrote:
> Hi Will,
>
> I have a question about iotable_init() function (arch/arm/mm/mmu.c)
> I found in this function it only allocate a vm_struct and insert it into vmlist ,
> But it didn?t allocate a vmap_area to insert it into vmap_area_root tree (mm/vmalloc.c).
>
> So this means that the virtual address reserverd by iotable_init is not declared
> In vmap_area_root , this is not safe , maybe some driver will use this virtual address as vmalloc again,
> I think it ?s not safe in this condition , should also add a vmap_area node into vmap_area_root to
> Hold this virtual address not used by others .
The vmap_area structures are allocated and inserted later on by vmalloc_init
(iotable init is for static mappings early during boot).
Will
^ permalink raw reply [flat|nested] 2+ messages in thread
* question about iotable_init( ) function
2013-07-01 9:27 ` question about iotable_init( ) function Will Deacon
@ 2013-07-01 9:30 ` Wang, Yalin
0 siblings, 0 replies; 2+ messages in thread
From: Wang, Yalin @ 2013-07-01 9:30 UTC (permalink / raw)
To: linux-arm-kernel
Hi Will,
Oh, I see,
Thanks for your clarification very much !
-----Original Message-----
From: Will Deacon [mailto:will.deacon at arm.com]
Sent: Monday, July 01, 2013 5:27 PM
To: Wang, Yalin
Cc: 'Russell King - ARM Linux'; 'linux-arm-kernel at lists.infradead.org'; 'linux-arch at vger.kernel.org'
Subject: Re: question about iotable_init( ) function
On Mon, Jul 01, 2013 at 08:31:38AM +0100, Wang, Yalin wrote:
> Hi Will,
>
> I have a question about iotable_init() function (arch/arm/mm/mmu.c) I
> found in this function it only allocate a vm_struct and insert it
> into vmlist , But it didn?t allocate a vmap_area to insert it into vmap_area_root tree (mm/vmalloc.c).
>
> So this means that the virtual address reserverd by iotable_init is
> not declared In vmap_area_root , this is not safe , maybe some driver will use this virtual address as vmalloc again,
> I think it ?s not safe in this condition , should also add a vmap_area node into vmap_area_root to
> Hold this virtual address not used by others .
The vmap_area structures are allocated and inserted later on by vmalloc_init (iotable init is for static mappings early during boot).
Will
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-07-01 9:30 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <35FD53F367049845BC99AC72306C23D19441BF586F@CNBJMBX05.corpusers.net>
2013-07-01 9:27 ` question about iotable_init( ) function Will Deacon
2013-07-01 9:30 ` Wang, Yalin
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox