All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baoquan He <bhe@redhat.com>
To: linux-kernel@vger.kernel.org
Cc: "Baoquan He" <bhe@redhat.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Brijesh Singh" <brijesh.singh@amd.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Borislav Petkov" <bp@suse.de>,
	"Tom Lendacky" <thomas.lendacky@amd.com>,
	"Wei Yang" <richard.weiyang@gmail.com>
Subject: [PATCH v2 2/3] resource: add walk_system_ram_res_rev()
Date: Sun,  8 Apr 2018 10:47:23 +0800	[thread overview]
Message-ID: <20180408024724.16812-3-bhe@redhat.com> (raw)
In-Reply-To: <20180408024724.16812-1-bhe@redhat.com>

This function, being a variant of walk_system_ram_res() introduced in
commit 8c86e70acead ("resource: provide new functions to walk through
resources"), walks through a list of all the resources of System RAM
in reversed order, i.e., from higher to lower.

It will be used in kexec_file code.

Signed-off-by: Baoquan He <bhe@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Brijesh Singh <brijesh.singh@amd.com>
Cc: "Jérôme Glisse" <jglisse@redhat.com>
Cc: Borislav Petkov <bp@suse.de>
Cc: Tom Lendacky <thomas.lendacky@amd.com>
Cc: Wei Yang <richard.weiyang@gmail.com>
---
 include/linux/ioport.h |  3 +++
 kernel/resource.c      | 40 ++++++++++++++++++++++++++++++++++++++++
 2 files changed, 43 insertions(+)

diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 745f2acc3674..ae2c409a0634 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -277,6 +277,9 @@ extern int
 walk_system_ram_res(u64 start, u64 end, void *arg,
 		    int (*func)(struct resource *, void *));
 extern int
+walk_system_ram_res_rev(u64 start, u64 end, void *arg,
+			int (*func)(struct resource *, void *));
+extern int
 walk_iomem_res_desc(unsigned long desc, unsigned long flags, u64 start, u64 end,
 		    void *arg, int (*func)(struct resource *, void *));
 
diff --git a/kernel/resource.c b/kernel/resource.c
index 05b1efa595c2..332a27403c33 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -23,6 +23,8 @@
 #include <linux/pfn.h>
 #include <linux/mm.h>
 #include <linux/resource_ext.h>
+#include <linux/string.h>
+#include <linux/vmalloc.h>
 #include <asm/io.h>
 
 
@@ -487,6 +489,44 @@ int walk_system_ram_res(u64 start, u64 end, void *arg,
 }
 
 /*
+ * This function, being a variant of walk_system_ram_res(), calls the @func
+ * callback against all memory ranges of type System RAM which are marked as
+ * IORESOURCE_SYSTEM_RAM and IORESOUCE_BUSY in reversed order, i.e., from
+ * higher to lower.
+ */
+int walk_system_ram_res_rev(u64 start, u64 end, void *arg,
+				int (*func)(struct resource *, void *))
+{
+	unsigned long flags;
+	struct resource *res;
+	int ret = -1;
+
+	flags = IORESOURCE_SYSTEM_RAM | IORESOURCE_BUSY;
+
+	read_lock(&resource_lock);
+	list_for_each_entry_reverse(res, &iomem_resource.child, sibling) {
+		if (start >= end)
+			break;
+		if ((res->flags & flags) != flags)
+			continue;
+		if (res->desc != IORES_DESC_NONE)
+			continue;
+		if (res->end < start)
+			break;
+
+		if ((res->end >= start) && (res->start < end)) {
+			ret = (*func)(res, arg);
+			if (ret)
+				break;
+		}
+		end = res->start - 1;
+
+	}
+	read_unlock(&resource_lock);
+	return ret;
+}
+
+/*
  * This function calls the @func callback against all memory ranges, which
  * are ranges marked as IORESOURCE_MEM and IORESOUCE_BUSY.
  */
-- 
2.13.6

  parent reply	other threads:[~2018-04-08  2:47 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-08  2:47 [PATCH v2 0/3] resource: Use list_head to link sibling resource Baoquan He
2018-04-08  2:47 ` [PATCH v2 1/3] " Baoquan He
2018-04-08  2:47   ` Baoquan He
2018-04-08  2:47   ` Baoquan He
2018-04-08  2:47   ` Baoquan He
2018-04-08  4:12   ` kbuild test robot
2018-04-08  4:12     ` kbuild test robot
2018-04-08  4:12     ` kbuild test robot
2018-04-08  4:12     ` kbuild test robot
2018-04-08  9:09     ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-08  5:55   ` kbuild test robot
2018-04-08  5:55     ` kbuild test robot
2018-04-08  5:55     ` kbuild test robot
2018-04-08  5:55     ` kbuild test robot
2018-04-08  9:09     ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-08  9:09       ` Baoquan He
2018-04-09  9:08   ` [PATCH v3 1/3] resource: Use list_head to link resource sibling Baoquan He
2018-04-09  9:08     ` Baoquan He
2018-04-09  9:08     ` Baoquan He
2018-04-09 14:49     ` Rob Herring
2018-04-09 14:49       ` Rob Herring
2018-04-09 14:49       ` Rob Herring
2018-04-09 16:05       ` Nicolas Pitre
2018-04-09 16:05         ` Nicolas Pitre
2018-04-09 16:05         ` Nicolas Pitre
2018-04-09 16:05         ` Nicolas Pitre
2018-04-10 13:44       ` Baoquan He
2018-04-10 13:44         ` Baoquan He
2018-04-10 13:44         ` Baoquan He
2018-04-10 13:44         ` Baoquan He
2018-04-11  3:22         ` Wei Yang
2018-04-11  3:22           ` Wei Yang
2018-04-11  3:22           ` Wei Yang
2018-04-09 15:38     ` Dan Williams
2018-04-09 15:38       ` Dan Williams
2018-04-09 15:38       ` Dan Williams
2018-04-10  2:10       ` Baoquan He
2018-04-10  2:10         ` Baoquan He
2018-04-10  2:10         ` Baoquan He
2018-04-10  2:10         ` Baoquan He
2018-04-10  2:34         ` Dan Williams
2018-04-10  2:34           ` Dan Williams
2018-04-10  2:34           ` Dan Williams
2018-04-10  2:34           ` Dan Williams
2018-04-10  2:49           ` Baoquan He
2018-04-10  2:49             ` Baoquan He
2018-04-10  2:49             ` Baoquan He
2018-04-10  2:49             ` Baoquan He
2018-04-08  2:47 ` Baoquan He [this message]
2018-04-08  2:47 ` [PATCH v2 3/3] kexec_file: Load kernel at top of system RAM if required Baoquan He
2018-04-08  2:47   ` Baoquan He

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=20180408024724.16812-3-bhe@redhat.com \
    --to=bhe@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=brijesh.singh@amd.com \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.weiyang@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.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 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.