public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wei Yang <richardw.yang@linux.intel.com>
To: Wei Yang <richardw.yang@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, jack@suse.cz, dan.j.williams@intel.com
Subject: Re: [PATCH] kernel, resource: use resource_overlaps() to simplify region_intersects()
Date: Tue, 12 Feb 2019 08:13:08 +0800	[thread overview]
Message-ID: <20190212001308.GA27906@richard> (raw)
In-Reply-To: <20190121012028.3913-1-richardw.yang@linux.intel.com>

On Mon, Jan 21, 2019 at 09:20:28AM +0800, Wei Yang wrote:
>The three checks in region_intersects() is to see whether two resources
>overlap. This means it could be simplified with one resource_overlaps().
>
>Also fix two typo in related function.
>
>Signed-off-by: Wei Yang <richardw.yang@linux.intel.com>

Hello~

Would someone like to take a look?

>---
> kernel/iomem.c    |  4 ++--
> kernel/resource.c | 11 +++++------
> 2 files changed, 7 insertions(+), 8 deletions(-)
>
>diff --git a/kernel/iomem.c b/kernel/iomem.c
>index f7525e14ebc6..93c264444510 100644
>--- a/kernel/iomem.c
>+++ b/kernel/iomem.c
>@@ -55,7 +55,7 @@ static void *try_ram_remap(resource_size_t offset, size_t size,
>  *
>  * MEMREMAP_WB - matches the default mapping for System RAM on
>  * the architecture.  This is usually a read-allocate write-back cache.
>- * Morever, if MEMREMAP_WB is specified and the requested remap region is RAM
>+ * Moreover, if MEMREMAP_WB is specified and the requested remap region is RAM
>  * memremap() will bypass establishing a new mapping and instead return
>  * a pointer into the direct map.
>  *
>@@ -86,7 +86,7 @@ void *memremap(resource_size_t offset, size_t size, unsigned long flags)
> 	/* Try all mapping types requested until one returns non-NULL */
> 	if (flags & MEMREMAP_WB) {
> 		/*
>-		 * MEMREMAP_WB is special in that it can be satisifed
>+		 * MEMREMAP_WB is special in that it can be satisfied
> 		 * from the direct map.  Some archs depend on the
> 		 * capability of memremap() to autodetect cases where
> 		 * the requested range is potentially in System RAM.
>diff --git a/kernel/resource.c b/kernel/resource.c
>index b0fbf685c77a..34dfb94305bb 100644
>--- a/kernel/resource.c
>+++ b/kernel/resource.c
>@@ -521,21 +521,20 @@ EXPORT_SYMBOL_GPL(page_is_ram);
> int region_intersects(resource_size_t start, size_t size, unsigned long flags,
> 		      unsigned long desc)
> {
>-	resource_size_t end = start + size - 1;
>+	struct resource res;
> 	int type = 0; int other = 0;
> 	struct resource *p;
> 
>+	res.start = start;
>+	res.end = start + size - 1;
>+
> 	read_lock(&resource_lock);
> 	for (p = iomem_resource.child; p ; p = p->sibling) {
> 		bool is_type = (((p->flags & flags) == flags) &&
> 				((desc == IORES_DESC_NONE) ||
> 				 (desc == p->desc)));
> 
>-		if (start >= p->start && start <= p->end)
>-			is_type ? type++ : other++;
>-		if (end >= p->start && end <= p->end)
>-			is_type ? type++ : other++;
>-		if (p->start >= start && p->end <= end)
>+		if (resource_overlaps(p, &res))
> 			is_type ? type++ : other++;
> 	}
> 	read_unlock(&resource_lock);
>-- 
>2.19.1

-- 
Wei Yang
Help you, Help me

  reply	other threads:[~2019-02-12  0:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-21  1:20 [PATCH] kernel, resource: use resource_overlaps() to simplify region_intersects() Wei Yang
2019-02-12  0:13 ` Wei Yang [this message]
2019-03-05  5:45   ` Like Xu
2019-03-05  5:49     ` Wei Yang
2019-02-19  3:21 ` Yuan Yao

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=20190212001308.GA27906@richard \
    --to=richardw.yang@linux.intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox