From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic
Date: Thu, 23 Oct 2014 23:50:42 +0000 [thread overview]
Message-ID: <3165257.hQsT1mEnTD@avalon> (raw)
In-Reply-To: <xa1tk33qlo93.fsf@mina86.com>
Hi Michal,
On Thursday 23 October 2014 18:55:20 Michal Nazarewicz wrote:
> On Thu, Oct 23 2014, Laurent Pinchart wrote:
> > The fixed parameter to cma_declare_contiguous() tells the function
> > whether the given base address must be honoured or should be considered
> > as a hint only. The API considers a zero base address as meaning any
> > base address, which must never be considered as a fixed value.
> >
> > Part of the implementation correctly checks both fixed and base != 0,
> > but two locations check the fixed value only. Set fixed to false when
> > base is 0 to fix that and simplify the code.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Michal Nazarewicz <mina86@mina86.com>
>
> And like before, this should also probably also go to stable.
v3.17 and older don't have the extra fixed checks, so I don't think there's a
need to Cc stable.
> > ---
> >
> > mm/cma.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 16c6650..6b14346 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -239,6 +239,9 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > size = ALIGN(size, alignment);
> > limit &= ~(alignment - 1);
> >
> > + if (!base)
> > + fixed = false;
> > +
> > /* size should be aligned with order_per_bit */
> > if (!IS_ALIGNED(size >> PAGE_SHIFT, 1 << order_per_bit))
> > return -EINVAL;
> > @@ -262,7 +265,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > }
> >
> > /* Reserve memory */
> > - if (base && fixed) {
> > + if (fixed) {
> > if (memblock_is_region_reserved(base, size) ||
> > memblock_reserve(base, size) < 0) {
> > ret = -EBUSY;
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: laurent.pinchart@ideasonboard.com (Laurent Pinchart)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic
Date: Fri, 24 Oct 2014 02:50:42 +0300 [thread overview]
Message-ID: <3165257.hQsT1mEnTD@avalon> (raw)
In-Reply-To: <xa1tk33qlo93.fsf@mina86.com>
Hi Michal,
On Thursday 23 October 2014 18:55:20 Michal Nazarewicz wrote:
> On Thu, Oct 23 2014, Laurent Pinchart wrote:
> > The fixed parameter to cma_declare_contiguous() tells the function
> > whether the given base address must be honoured or should be considered
> > as a hint only. The API considers a zero base address as meaning any
> > base address, which must never be considered as a fixed value.
> >
> > Part of the implementation correctly checks both fixed and base != 0,
> > but two locations check the fixed value only. Set fixed to false when
> > base is 0 to fix that and simplify the code.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Michal Nazarewicz <mina86@mina86.com>
>
> And like before, this should also probably also go to stable.
v3.17 and older don't have the extra fixed checks, so I don't think there's a
need to Cc stable.
> > ---
> >
> > mm/cma.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 16c6650..6b14346 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -239,6 +239,9 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > size = ALIGN(size, alignment);
> > limit &= ~(alignment - 1);
> >
> > + if (!base)
> > + fixed = false;
> > +
> > /* size should be aligned with order_per_bit */
> > if (!IS_ALIGNED(size >> PAGE_SHIFT, 1 << order_per_bit))
> > return -EINVAL;
> > @@ -262,7 +265,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > }
> >
> > /* Reserve memory */
> > - if (base && fixed) {
> > + if (fixed) {
> > if (memblock_is_region_reserved(base, size) ||
> > memblock_reserve(base, size) < 0) {
> > ret = -EBUSY;
--
Regards,
Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic
Date: Fri, 24 Oct 2014 02:50:42 +0300 [thread overview]
Message-ID: <3165257.hQsT1mEnTD@avalon> (raw)
In-Reply-To: <xa1tk33qlo93.fsf@mina86.com>
Hi Michal,
On Thursday 23 October 2014 18:55:20 Michal Nazarewicz wrote:
> On Thu, Oct 23 2014, Laurent Pinchart wrote:
> > The fixed parameter to cma_declare_contiguous() tells the function
> > whether the given base address must be honoured or should be considered
> > as a hint only. The API considers a zero base address as meaning any
> > base address, which must never be considered as a fixed value.
> >
> > Part of the implementation correctly checks both fixed and base != 0,
> > but two locations check the fixed value only. Set fixed to false when
> > base is 0 to fix that and simplify the code.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Michal Nazarewicz <mina86@mina86.com>
>
> And like before, this should also probably also go to stable.
v3.17 and older don't have the extra fixed checks, so I don't think there's a
need to Cc stable.
> > ---
> >
> > mm/cma.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 16c6650..6b14346 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -239,6 +239,9 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > size = ALIGN(size, alignment);
> > limit &= ~(alignment - 1);
> >
> > + if (!base)
> > + fixed = false;
> > +
> > /* size should be aligned with order_per_bit */
> > if (!IS_ALIGNED(size >> PAGE_SHIFT, 1 << order_per_bit))
> > return -EINVAL;
> > @@ -262,7 +265,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > }
> >
> > /* Reserve memory */
> > - if (base && fixed) {
> > + if (fixed) {
> > if (memblock_is_region_reserved(base, size) ||
> > memblock_reserve(base, size) < 0) {
> > ret = -EBUSY;
--
Regards,
Laurent Pinchart
--
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: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michal Nazarewicz <mina86@mina86.com>
Cc: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, linux-sh@vger.kernel.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
Russell King - ARM Linux <linux@arm.linux.org.uk>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>
Subject: Re: [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic
Date: Fri, 24 Oct 2014 02:50:42 +0300 [thread overview]
Message-ID: <3165257.hQsT1mEnTD@avalon> (raw)
In-Reply-To: <xa1tk33qlo93.fsf@mina86.com>
Hi Michal,
On Thursday 23 October 2014 18:55:20 Michal Nazarewicz wrote:
> On Thu, Oct 23 2014, Laurent Pinchart wrote:
> > The fixed parameter to cma_declare_contiguous() tells the function
> > whether the given base address must be honoured or should be considered
> > as a hint only. The API considers a zero base address as meaning any
> > base address, which must never be considered as a fixed value.
> >
> > Part of the implementation correctly checks both fixed and base != 0,
> > but two locations check the fixed value only. Set fixed to false when
> > base is 0 to fix that and simplify the code.
> >
> > Signed-off-by: Laurent Pinchart
> > <laurent.pinchart+renesas@ideasonboard.com>
>
> Acked-by: Michal Nazarewicz <mina86@mina86.com>
>
> And like before, this should also probably also go to stable.
v3.17 and older don't have the extra fixed checks, so I don't think there's a
need to Cc stable.
> > ---
> >
> > mm/cma.c | 5 ++++-
> > 1 file changed, 4 insertions(+), 1 deletion(-)
> >
> > diff --git a/mm/cma.c b/mm/cma.c
> > index 16c6650..6b14346 100644
> > --- a/mm/cma.c
> > +++ b/mm/cma.c
> > @@ -239,6 +239,9 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > size = ALIGN(size, alignment);
> > limit &= ~(alignment - 1);
> >
> > + if (!base)
> > + fixed = false;
> > +
> > /* size should be aligned with order_per_bit */
> > if (!IS_ALIGNED(size >> PAGE_SHIFT, 1 << order_per_bit))
> > return -EINVAL;
> > @@ -262,7 +265,7 @@ int __init cma_declare_contiguous(phys_addr_t base,
> > }
> >
> > /* Reserve memory */
> > - if (base && fixed) {
> > + if (fixed) {
> > if (memblock_is_region_reserved(base, size) ||
> > memblock_reserve(base, size) < 0) {
> > ret = -EBUSY;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-10-23 23:50 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-23 14:33 [PATCH 0/4] Low/high memory CMA reservation fixes Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 1/4] mm: cma: Don't crash on allocation if CMA area can't be activated Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 16:53 ` Michal Nazarewicz
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-23 23:42 ` Laurent Pinchart
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:02 ` Weijie Yang
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 2:50 ` Joonsoo Kim
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 9:54 ` Laurent Pinchart
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-24 16:34 ` Michal Nazarewicz
2014-10-23 14:33 ` [PATCH 2/4] mm: cma: Always consider a 0 base address reservation as dynamic Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 16:55 ` Michal Nazarewicz
2014-10-23 23:50 ` Laurent Pinchart [this message]
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 23:50 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 3/4] mm: cma: Ensure that reservations never cross the low/high mem boundary Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 2:53 ` Joonsoo Kim
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-24 10:00 ` Laurent Pinchart
2014-10-23 14:33 ` [PATCH 4/4] mm: cma: Use %pa to print physical addresses Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 14:33 ` Laurent Pinchart
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 16:56 ` Michal Nazarewicz
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
2014-10-23 17:51 ` Geert Uytterhoeven
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=3165257.hQsT1mEnTD@avalon \
--to=laurent.pinchart@ideasonboard.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.