From: neidhard.kim@lge.com (Kim, Jong-Sung)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] [RESEND] arm: limit memblock base address for early_pte_alloc
Date: Thu, 28 Jun 2012 15:54:49 +0900 [thread overview]
Message-ID: <010e01cd54fa$e9c93fd0$bd5bbf70$@lge.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1206280223250.31003@xanadu.home>
> From: Nicolas Pitre [mailto:nicolas.pitre at linaro.org]
> Sent: Thursday, June 28, 2012 3:26 PM
>
> On Thu, 28 Jun 2012, Kim, Jong-Sung wrote:
>
> > Thank you for your comment, Dave! It was not that sophisticated
> > choice, but I thought that normal embedded system trying to reduce the
> > BOM would have a big-enough first memblock memory region. However
> > you're right. There can be exceptional systems. Then, how do you think
> about following manner:
> [...]
>
> This still has some possibilities for failure.
>
Can you kindly describe the possible failure path?
> Please have a look at the two patches I've posted to fix this in a better
> way.
>
I'm setting up for your elegant patches. ;-)
WARNING: multiple messages have this Message-ID (diff)
From: "Kim, Jong-Sung" <neidhard.kim@lge.com>
To: 'Nicolas Pitre' <nicolas.pitre@linaro.org>
Cc: 'Dave Martin' <dave.martin@linaro.org>,
'Minchan Kim' <minchan@kernel.org>,
'Russell King' <linux@arm.linux.org.uk>,
'Catalin Marinas' <catalin.marinas@arm.com>,
'Chanho Min' <chanho.min@lge.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
linux-arm-kernel@lists.infradead.org
Subject: RE: [PATCH] [RESEND] arm: limit memblock base address for early_pte_alloc
Date: Thu, 28 Jun 2012 15:54:49 +0900 [thread overview]
Message-ID: <010e01cd54fa$e9c93fd0$bd5bbf70$@lge.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1206280223250.31003@xanadu.home>
> From: Nicolas Pitre [mailto:nicolas.pitre@linaro.org]
> Sent: Thursday, June 28, 2012 3:26 PM
>
> On Thu, 28 Jun 2012, Kim, Jong-Sung wrote:
>
> > Thank you for your comment, Dave! It was not that sophisticated
> > choice, but I thought that normal embedded system trying to reduce the
> > BOM would have a big-enough first memblock memory region. However
> > you're right. There can be exceptional systems. Then, how do you think
> about following manner:
> [...]
>
> This still has some possibilities for failure.
>
Can you kindly describe the possible failure path?
> Please have a look at the two patches I've posted to fix this in a better
> way.
>
I'm setting up for your elegant patches. ;-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: "Kim, Jong-Sung" <neidhard.kim@lge.com>
To: "'Nicolas Pitre'" <nicolas.pitre@linaro.org>
Cc: "'Dave Martin'" <dave.martin@linaro.org>,
"'Minchan Kim'" <minchan@kernel.org>,
"'Russell King'" <linux@arm.linux.org.uk>,
"'Catalin Marinas'" <catalin.marinas@arm.com>,
"'Chanho Min'" <chanho.min@lge.com>,
<linux-kernel@vger.kernel.org>, <linux-mm@kvack.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH] [RESEND] arm: limit memblock base address for early_pte_alloc
Date: Thu, 28 Jun 2012 15:54:49 +0900 [thread overview]
Message-ID: <010e01cd54fa$e9c93fd0$bd5bbf70$@lge.com> (raw)
In-Reply-To: <alpine.LFD.2.02.1206280223250.31003@xanadu.home>
> From: Nicolas Pitre [mailto:nicolas.pitre@linaro.org]
> Sent: Thursday, June 28, 2012 3:26 PM
>
> On Thu, 28 Jun 2012, Kim, Jong-Sung wrote:
>
> > Thank you for your comment, Dave! It was not that sophisticated
> > choice, but I thought that normal embedded system trying to reduce the
> > BOM would have a big-enough first memblock memory region. However
> > you're right. There can be exceptional systems. Then, how do you think
> about following manner:
> [...]
>
> This still has some possibilities for failure.
>
Can you kindly describe the possible failure path?
> Please have a look at the two patches I've posted to fix this in a better
> way.
>
I'm setting up for your elegant patches. ;-)
next prev parent reply other threads:[~2012-06-28 6:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 7:11 [PATCH] [RESEND] arm: limit memblock base address for early_pte_alloc Minchan Kim
2012-06-05 7:11 ` Minchan Kim
2012-06-05 7:11 ` Minchan Kim
2012-06-08 13:58 ` Kim, Jong-Sung
2012-06-08 13:58 ` Kim, Jong-Sung
2012-06-08 13:58 ` Kim, Jong-Sung
2012-06-27 16:02 ` Dave Martin
2012-06-27 16:02 ` Dave Martin
2012-06-27 16:02 ` Dave Martin
2012-06-28 5:43 ` Kim, Jong-Sung
2012-06-28 5:43 ` Kim, Jong-Sung
2012-06-28 5:43 ` Kim, Jong-Sung
2012-06-28 6:25 ` Nicolas Pitre
2012-06-28 6:25 ` Nicolas Pitre
2012-06-28 6:25 ` Nicolas Pitre
2012-06-28 6:54 ` Kim, Jong-Sung [this message]
2012-06-28 6:54 ` Kim, Jong-Sung
2012-06-28 6:54 ` Kim, Jong-Sung
2012-06-27 19:18 ` Russell King - ARM Linux
2012-06-27 19:18 ` Russell King - ARM Linux
2012-06-27 19:18 ` Russell King - ARM Linux
2012-06-28 6:08 ` Kim, Jong-Sung
2012-06-28 6:08 ` Kim, Jong-Sung
2012-06-28 6:08 ` Kim, Jong-Sung
2012-06-19 8:38 ` Minchan Kim
2012-06-19 8:38 ` Minchan Kim
2012-06-19 8:38 ` Minchan Kim
2012-06-27 16:12 ` Dave Martin
2012-06-27 16:12 ` Dave Martin
2012-06-27 16:12 ` Dave Martin
2012-06-28 4:33 ` Nicolas Pitre
2012-06-28 4:33 ` Nicolas Pitre
2012-06-28 4:33 ` Nicolas Pitre
2012-06-28 4:46 ` Minchan Kim
2012-06-28 9:08 ` Russell King - ARM Linux
2012-06-28 9:08 ` Russell King - ARM Linux
2012-06-28 9:08 ` Russell King - ARM Linux
2012-06-28 17:50 ` Nicolas Pitre
2012-06-28 17:50 ` Nicolas Pitre
2012-06-28 17:50 ` Nicolas Pitre
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='010e01cd54fa$e9c93fd0$bd5bbf70$@lge.com' \
--to=neidhard.kim@lge.com \
--cc=linux-arm-kernel@lists.infradead.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.