From: Andrew Morton <akpm@linux-foundation.org>
To: Laura Abbott <lauraa@codeaurora.org>
Cc: Will Deacon <will.deacon@arm.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Russell King <linux@arm.linux.org.uk>,
David Riley <davidriley@chromium.org>,
linux-arm-kernel@lists.infradead.org,
Ritesh Harjain <ritesh.harjani@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Thierry Reding <thierry.reding@gmail.com>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCHv6 2/5] lib/genalloc.c: Add genpool range check function
Date: Fri, 8 Aug 2014 15:40:08 -0700 [thread overview]
Message-ID: <20140808154008.4e5183b67d29159a83ffcf25@linux-foundation.org> (raw)
In-Reply-To: <1407529397-6642-2-git-send-email-lauraa@codeaurora.org>
On Fri, 8 Aug 2014 13:23:14 -0700 Laura Abbott <lauraa@codeaurora.org> wrote:
>
> After allocating an address from a particular genpool,
> there is no good way to verify if that address actually
> belongs to a genpool. Introduce addr_in_gen_pool which
> will return if an address plus size falls completely
> within the genpool range.
>
> ...
>
> /**
> + * addr_in_gen_pool - checks if an address falls within the range of a pool
> + * @pool: the generic memory pool
> + * @start: start address
> + * @size: size of the region
> + *
> + * Check if the range of addresses falls within the specified pool.
This description should make it clear that the entire range must be
within the pool - that an overlap is "no".
> Takes
> + * the rcu_read_lock for the duration of the check.
I don't think this part is worth including.
> + */
> +bool addr_in_gen_pool(struct gen_pool *pool, unsigned long start,
> + size_t size)
> +{
> + bool found = false;
> + unsigned long end = start + size;
> + struct gen_pool_chunk *chunk;
> +
> + rcu_read_lock();
> + list_for_each_entry_rcu(chunk, &(pool)->chunks, next_chunk) {
> + if (start >= chunk->start_addr && start <= chunk->end_addr) {
> + if (end <= chunk->end_addr) {
> + found = true;
> + break;
> + }
> + }
> + }
> + rcu_read_unlock();
> + return found;
> +}
--
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>
next prev parent reply other threads:[~2014-08-08 22:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-08 20:23 [PATCHv6 1/5] lib/genalloc.c: Add power aligned algorithm Laura Abbott
2014-08-08 20:23 ` [PATCHv6 2/5] lib/genalloc.c: Add genpool range check function Laura Abbott
2014-08-08 22:40 ` Andrew Morton [this message]
2014-08-08 20:23 ` [PATCHv6 3/5] common: dma-mapping: Introduce common remapping functions Laura Abbott
2014-08-08 22:45 ` Andrew Morton
2014-08-08 23:25 ` Laura Abbott
2014-08-11 18:05 ` Catalin Marinas
2014-08-11 18:04 ` Catalin Marinas
2014-08-08 20:23 ` [PATCHv6 4/5] arm: use genalloc for the atomic pool Laura Abbott
2014-08-08 20:23 ` [PATCHv6 5/5] arm64: Add atomic pool for non-coherent and CMA allocations Laura Abbott
2014-08-08 22:36 ` [PATCHv6 1/5] lib/genalloc.c: Add power aligned algorithm Andrew Morton
2014-08-08 22:41 ` Laura Abbott
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=20140808154008.4e5183b67d29159a83ffcf25@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=davidriley@chromium.org \
--cc=lauraa@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux@arm.linux.org.uk \
--cc=ritesh.harjani@gmail.com \
--cc=thierry.reding@gmail.com \
--cc=will.deacon@arm.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox