[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b9df5fa11001072234o2e5fb8bfv7b57a562d9a6e4d1@mail.gmail.com>
Date: Fri, 8 Jan 2010 12:34:15 +0600
From: Rakib Mullick <rakib.mullick@...il.com>
To: Randy Dunlap <randy.dunlap@...cle.com>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org,
akpm@...ux-foundation.org
Subject: Re: + hugetlb-fix-section-mismatch-warning-in-hugetlbc.patch added to
-mm tree
On 1/8/10, Randy Dunlap <randy.dunlap@...cle.com> wrote:
Hi,
>
> Hi,
>
> If so, then hugetlb_register_node() could be called at any time
> (like after system init), and it would then call
> hugetlb_sysfs_add_hstate(), which would be bad.
>
But - hugetlb_register_node is only called from hugetlb_register_all_nodes.
The call sequence is :
hugetlb_init ---------------> was __init
\-> hugetlb_register_all_nodes ----> we make it __init
\-> hugetlb_register_node
---> we make it __init
\->
hugetlb_sysfs_add_hstate -> this was __init
Above all happens in __init context. So - hugetlb_register_node is
called only at
system init. But I don't think __init is used for hotplug support, for
proper hotplug
support we might use __meminit.
And register_hugetlbfs_with_node is called from hugetlb_un/register_node.
But hugetlb_unregister_node doesn't use callback function. It's not referencing
hugetlb_sysfs_add_hstate(). So - it's safe. Unless I'm not missing
anything, too.
thanks,
> Thanks.
> ---
>
> ~Randy
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists