mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: WANG Chao <chaowang@redhat.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>,
	x86@kernel.org (maintainer:X86 ARCHITECTURE...),
	Matt Fleming <matt.fleming@intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Santosh Shilimkar <santosh.shilimkar@ti.com>,
	Borislav Petkov <bp@suse.de>,
	Daniel Kiper <daniel.kiper@oracle.com>,
	"Bryan O'Donoghue" <pure.logic@nexus-software.ie>,
	linux-kernel@vger.kernel.org (open list:X86 ARCHITECTURE...)
Subject: [PATCH 2/2] x86: add macro for_each_setup_data()
Date: Wed,  7 Jan 2015 18:55:49 +0800	[thread overview]
Message-ID: <1420628150-16872-2-git-send-email-chaowang@redhat.com> (raw)
In-Reply-To: <1420628150-16872-1-git-send-email-chaowang@redhat.com>

A common task for parsing setup_data is to iterate over setup_data's
linked list, remap and do something and unmap. Now add macro
for_each_setup_data() to do that.

Signed-off-by: WANG Chao <chaowang@redhat.com>
---
 arch/x86/kernel/setup.c | 37 ++++++++++++-------------------------
 1 file changed, 12 insertions(+), 25 deletions(-)

diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index c4648ada..1e24c37 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -424,35 +424,30 @@ static void __init reserve_initrd(void)
 }
 #endif /* CONFIG_BLK_DEV_INITRD */
 
+#define for_each_setup_data(pa_data, data) \
+	for (pa_data = boot_params.hdr.setup_data; \
+		pa_data && (data = early_memremap(pa_data, sizeof(*data))); \
+		pa_data = data->next, early_iounmap(data, sizeof(*data)))
+
 static void __init parse_setup_data(void)
 {
 	struct setup_data *data;
-	u64 pa_data, pa_next;
-
-	pa_data = boot_params.hdr.setup_data;
-	while (pa_data) {
-		u32 data_len, data_type;
-
-		data = early_memremap(pa_data, sizeof(*data));
-		data_len = data->len + sizeof(struct setup_data);
-		data_type = data->type;
-		pa_next = data->next;
-		early_iounmap(data, sizeof(*data));
+	u64 pa_data;
 
-		switch (data_type) {
+	for_each_setup_data(pa_data, data) {
+		switch (data->type) {
 		case SETUP_E820_EXT:
-			parse_e820_ext(pa_data, data_len);
+			parse_e820_ext(pa_data, data->len + sizeof(*data));
 			break;
 		case SETUP_DTB:
 			add_dtb(pa_data);
 			break;
 		case SETUP_EFI:
-			parse_efi_setup(pa_data, data_len);
+			parse_efi_setup(pa_data, data->len + sizeof(*data));
 			break;
 		default:
 			break;
 		}
-		pa_data = pa_next;
 	}
 }
 
@@ -462,14 +457,10 @@ static void __init e820_reserve_setup_data(void)
 	u64 pa_data;
 	int found = 0;
 
-	pa_data = boot_params.hdr.setup_data;
-	while (pa_data) {
-		data = early_memremap(pa_data, sizeof(*data));
+	for_each_setup_data(pa_data, data) {
 		e820_update_range(pa_data, sizeof(*data)+data->len,
 			 E820_RAM, E820_RESERVED_KERN);
 		found = 1;
-		pa_data = data->next;
-		early_iounmap(data, sizeof(*data));
 	}
 	if (!found)
 		return;
@@ -485,12 +476,8 @@ static void __init memblock_x86_reserve_range_setup_data(void)
 	struct setup_data *data;
 	u64 pa_data;
 
-	pa_data = boot_params.hdr.setup_data;
-	while (pa_data) {
-		data = early_memremap(pa_data, sizeof(*data));
+	for_each_setup_data(pa_data, data) {
 		memblock_reserve(pa_data, sizeof(*data) + data->len);
-		pa_data = data->next;
-		early_iounmap(data, sizeof(*data));
 	}
 }
 
-- 
2.1.0


  reply	other threads:[~2015-01-07 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-07 10:55 [PATCH 1/2] x86: early_memremap exact size of struct setup_data WANG Chao
2015-01-07 10:55 ` WANG Chao [this message]
2015-01-23 14:24   ` [PATCH 2/2] x86: add macro for_each_setup_data() Thomas Gleixner
2015-01-23 15:18 ` [tip:x86/mm] x86, setup: Let early_memremap() handle page alignment tip-bot for WANG Chao

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=1420628150-16872-2-git-send-email-chaowang@redhat.com \
    --to=chaowang@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=bp@suse.de \
    --cc=daniel.kiper@oracle.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matt.fleming@intel.com \
    --cc=mingo@redhat.com \
    --cc=pure.logic@nexus-software.ie \
    --cc=santosh.shilimkar@ti.com \
    --cc=tglx@linutronix.de \
    --cc=x86@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

Powered by JetHome