All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Wang, Yalin" <Yalin.Wang@sonymobile.com>
To: "'sboyd@codeaurora.org'" <sboyd@codeaurora.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	Arnd Bergmann <arnd@arndb.de>,
	David Brown <davidb@codeaurora.org>,
	Bryan Huntsman <bryanh@codeaurora.org>
Subject: FW: Arch/arm/msm/memory.c:reserve_memory_for_mempools( )
Date: Fri, 28 Jun 2013 14:14:54 +0800	[thread overview]
Message-ID: <35FD53F367049845BC99AC72306C23D19441BF586A@CNBJMBX05.corpusers.net> (raw)


Hi Sboy,

I don't know who should I send this mail to .
If you are not the right person, please forward To the right responsible person , Thank you !

I have a question about msm kernel code :

File: Arch/arm/msm/memory.c

reserve_memory_for_mempools()
it call memblock_remove() directly,
I think it's not safe sometimes ,
Should use arm_memblock_steal() function or some other similar Function to make sure the removed memory is not reserved by memblock driver, In case the removed memory is reserved by some other driver.


Thanks 


Yalin.Wang
Software Engineer
OS Kernel&Graphics
 
Sony Mobile Communications
Tel: +86 10 5966 9819
Phone: 18610323092
Address: No.16 Guangshun South Street, Chaoyang, Beijing, P.R.C.

sonymobile.com
  

WARNING: multiple messages have this Message-ID (diff)
From: Yalin.Wang@sonymobile.com (Wang, Yalin)
To: linux-arm-kernel@lists.infradead.org
Subject: FW: Arch/arm/msm/memory.c:reserve_memory_for_mempools( )
Date: Fri, 28 Jun 2013 14:14:54 +0800	[thread overview]
Message-ID: <35FD53F367049845BC99AC72306C23D19441BF586A@CNBJMBX05.corpusers.net> (raw)


Hi Sboy,

I don't know who should I send this mail to .
If you are not the right person, please forward To the right responsible person , Thank you !

I have a question about msm kernel code :

File: Arch/arm/msm/memory.c

reserve_memory_for_mempools()
it call memblock_remove() directly,
I think it's not safe sometimes ,
Should use arm_memblock_steal() function or some other similar Function to make sure the removed memory is not reserved by memblock driver, In case the removed memory is reserved by some other driver.


Thanks 


Yalin.Wang
Software Engineer
OS Kernel&Graphics
?
Sony Mobile Communications
Tel: +86 10 5966 9819
Phone: 18610323092
Address: No.16 Guangshun South Street, Chaoyang, Beijing, P.R.C.

sonymobile.com
??

             reply	other threads:[~2013-06-28  6:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-28  6:14 Wang, Yalin [this message]
2013-06-28  6:14 ` FW: Arch/arm/msm/memory.c:reserve_memory_for_mempools( ) Wang, Yalin
2013-06-28  6:14 ` Wang, Yalin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=35FD53F367049845BC99AC72306C23D19441BF586A@CNBJMBX05.corpusers.net \
    --to=yalin.wang@sonymobile.com \
    --cc=arnd@arndb.de \
    --cc=bryanh@codeaurora.org \
    --cc=davidb@codeaurora.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@codeaurora.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.