mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Linus Torvalds" <torvalds@linux-foundation.org>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Jeff Garzik" <jeff@garzik.org>, "Tejun Heo" <htejun@gmail.com>,
	"Ingo Molnar" <mingo@elte.hu>,
	"David Witbrodt" <dawitbro@sbcglobal.net>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"Kernel Testers" <kernel-testers@vger.kernel.org>
Subject: Re: Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd
Date: Sat, 30 Aug 2008 14:12:12 -0700	[thread overview]
Message-ID: <86802c440808301412k4e0b5562ie03ce41547ddab9a@mail.gmail.com> (raw)
In-Reply-To: <200808302246.48199.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 640 bytes --]

On Sat, Aug 30, 2008 at 1:46 PM, Rafael J. Wysocki <rjw@sisk.pl> wrote:
> On Saturday, 30 of August 2008, Yinghai Lu wrote:
>> please check
>>
>> [PATCH] x86: split e820 reserved entries record to late v4
>> [PATCH] x86: split e820 reserved entries record to late v4 - fix v6
>
> What kernel should I apply those to and in what order?

linus git tree
1. [PATCH] x86: split e820 reserved entries record to late v4
2. [PATCH] x86: split e820 reserved entries record to late v4 - fix v6

tip/master
1. Resource handling: add 'insert_resource_expand_to_fit()' function
2. [PATCH] x86: split e820 reserved entries record to late v4 - fix v6

YH

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: insert_resource_expand_to_fit.patch --]
[-- Type: text/x-patch; name=insert_resource_expand_to_fit.patch, Size: 5015 bytes --]

commit bef69ea0dcce574a425feb0a5aa4c63dd108b9a6
Author: Linus Torvalds <torvalds@linux-foundation.org>
Date:   Fri Aug 29 20:18:31 2008 -0700

    Resource handling: add 'insert_resource_expand_to_fit()' function
    
    Not used anywhere yet, but this complements the existing plain
    'insert_resource()' functionality with a version that can expand the
    resource we are adding in order to fix up any conflicts it has with
    existing resources.
    
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

diff --git a/include/linux/ioport.h b/include/linux/ioport.h
index 22d2115..8d3b7a9 100644
--- a/include/linux/ioport.h
+++ b/include/linux/ioport.h
@@ -109,6 +109,7 @@ extern struct resource iomem_resource;
 extern int request_resource(struct resource *root, struct resource *new);
 extern int release_resource(struct resource *new);
 extern int insert_resource(struct resource *parent, struct resource *new);
+extern void insert_resource_expand_to_fit(struct resource *root, struct resource *new);
 extern int allocate_resource(struct resource *root, struct resource *new,
 			     resource_size_t size, resource_size_t min,
 			     resource_size_t max, resource_size_t align,
diff --git a/kernel/resource.c b/kernel/resource.c
index f5b518e..cf0a178 100644
--- a/kernel/resource.c
+++ b/kernel/resource.c
@@ -362,35 +362,21 @@ int allocate_resource(struct resource *root, struct resource *new,
 
 EXPORT_SYMBOL(allocate_resource);
 
-/**
- * insert_resource - Inserts a resource in the resource tree
- * @parent: parent of the new resource
- * @new: new resource to insert
- *
- * Returns 0 on success, -EBUSY if the resource can't be inserted.
- *
- * This function is equivalent to request_resource when no conflict
- * happens. If a conflict happens, and the conflicting resources
- * entirely fit within the range of the new resource, then the new
- * resource is inserted and the conflicting resources become children of
- * the new resource.
+/*
+ * Insert a resource into the resource tree. If successful, return NULL,
+ * otherwise return the conflicting resource (compare to __request_resource())
  */
-int insert_resource(struct resource *parent, struct resource *new)
+static struct resource * __insert_resource(struct resource *parent, struct resource *new)
 {
-	int result;
 	struct resource *first, *next;
 
-	write_lock(&resource_lock);
-
 	for (;; parent = first) {
-	 	result = 0;
 		first = __request_resource(parent, new);
 		if (!first)
-			goto out;
+			return first;
 
-		result = -EBUSY;
 		if (first == parent)
-			goto out;
+			return first;
 
 		if ((first->start > new->start) || (first->end < new->end))
 			break;
@@ -401,15 +387,13 @@ int insert_resource(struct resource *parent, struct resource *new)
 	for (next = first; ; next = next->sibling) {
 		/* Partial overlap? Bad, and unfixable */
 		if (next->start < new->start || next->end > new->end)
-			goto out;
+			return next;
 		if (!next->sibling)
 			break;
 		if (next->sibling->start > new->end)
 			break;
 	}
 
-	result = 0;
-
 	new->parent = parent;
 	new->sibling = next->sibling;
 	new->child = first;
@@ -426,10 +410,64 @@ int insert_resource(struct resource *parent, struct resource *new)
 			next = next->sibling;
 		next->sibling = new;
 	}
+	return NULL;
+}
 
- out:
+/**
+ * insert_resource - Inserts a resource in the resource tree
+ * @parent: parent of the new resource
+ * @new: new resource to insert
+ *
+ * Returns 0 on success, -EBUSY if the resource can't be inserted.
+ *
+ * This function is equivalent to request_resource when no conflict
+ * happens. If a conflict happens, and the conflicting resources
+ * entirely fit within the range of the new resource, then the new
+ * resource is inserted and the conflicting resources become children of
+ * the new resource.
+ */
+int insert_resource(struct resource *parent, struct resource *new)
+{
+	struct resource *conflict;
+
+	write_lock(&resource_lock);
+	conflict = __insert_resource(parent, new);
+	write_unlock(&resource_lock);
+	return conflict ? -EBUSY : 0;
+}
+
+/**
+ * insert_resource_expand_to_fit - Insert a resource into the resource tree
+ * @parent: parent of the new resource
+ * @new: new resource to insert
+ *
+ * Insert a resource into the resource tree, possibly expanding it in order
+ * to make it encompass any conflicting resources.
+ */
+void insert_resource_expand_to_fit(struct resource *root, struct resource *new)
+{
+	if (new->parent)
+		return;
+
+	write_lock(&resource_lock);
+	for (;;) {
+		struct resource *conflict;
+
+		conflict = __insert_resource(root, new);
+		if (!conflict)
+			break;
+		if (conflict == root)
+			break;
+
+		/* Ok, expand resource to cover the conflict, then try again .. */
+		if (conflict->start < new->start)
+			new->start = conflict->start;
+		if (conflict->end > new->end)
+			new->end = conflict->end;
+
+		printk("Expanded resource %s due to conflict with %s\n", new->name, conflict->name);
+	}
 	write_unlock(&resource_lock);
-	return result;
 }
 
 /**

  reply	other threads:[~2008-08-30 21:12 UTC|newest]

Thread overview: 94+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-28 23:26 Linux 2.6.27-rc5 Linus Torvalds
2008-08-29 15:42 ` cpu time oddity (was Re: Linux 2.6.27-rc5) Alistair John Strachan
2008-08-29 15:56   ` Alistair John Strachan
2008-08-29 17:13 ` Linux 2.6.27-rc5 Rafael J. Wysocki
2008-08-29 19:57   ` Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd Rafael J. Wysocki
2008-08-29 21:13     ` Yinghai Lu
2008-08-29 21:19       ` Yinghai Lu
2008-08-29 22:32         ` Rafael J. Wysocki
2008-08-29 22:31       ` Rafael J. Wysocki
2008-08-29 23:24         ` Yinghai Lu
2008-08-30  0:08           ` Linus Torvalds
2008-08-30  0:11             ` Yinghai Lu
2008-08-30  0:45               ` Linus Torvalds
2008-08-30  1:11                 ` Linus Torvalds
2008-08-30  1:30                   ` Yinghai Lu
2008-08-30  2:33                     ` Linus Torvalds
2008-08-30  2:56                       ` Linus Torvalds
2008-08-30  3:07                         ` Yinghai Lu
2008-08-30  3:24                           ` Linus Torvalds
2008-08-30  4:41                             ` Yinghai Lu
2008-08-30  5:02                               ` Yinghai Lu
2008-08-30  5:52                               ` Linus Torvalds
2008-08-30  6:18                                 ` Linus Torvalds
2008-08-30  8:02                                   ` Yinghai Lu
2008-08-30  5:22                             ` Yinghai Lu
2008-08-30  6:11                               ` Linus Torvalds
2008-08-30  3:15                         ` Linus Torvalds
2008-08-30  3:00                       ` Yinghai Lu
2008-08-30  3:10                         ` Linus Torvalds
2008-08-30  1:14                 ` Yinghai Lu
2008-08-30  2:16                   ` Linus Torvalds
2008-08-30  2:29                     ` Yinghai Lu
2008-08-30  0:20             ` Yinghai Lu
2008-08-30  0:27               ` Yinghai Lu
2008-08-30 13:32                 ` Rafael J. Wysocki
2008-08-30 16:05                   ` Yinghai Lu
2008-08-30 17:14                     ` Rafael J. Wysocki
2008-08-30 17:55                       ` Yinghai Lu
2008-08-30 18:11                         ` Yinghai Lu
2008-08-30 19:06                           ` Yinghai Lu
2008-08-30 19:51                             ` Rafael J. Wysocki
2008-08-30 20:10                               ` Yinghai Lu
2008-08-29 21:44     ` Linus Torvalds
2008-08-29 22:30       ` Rafael J. Wysocki
2008-08-30 17:39         ` Linus Torvalds
2008-08-30 18:07           ` Yinghai Lu
2008-08-30 18:43             ` Linus Torvalds
2008-08-30 19:10               ` Yinghai Lu
2008-08-30 19:31                 ` Linus Torvalds
2008-08-30 20:14                   ` Yinghai Lu
2008-08-30 20:38                     ` Yinghai Lu
2008-08-30 20:46                       ` Rafael J. Wysocki
2008-08-30 21:12                         ` Yinghai Lu [this message]
2008-08-30 21:13                           ` Yinghai Lu
2008-08-30 21:34                             ` Rafael J. Wysocki
2008-08-30 21:49                               ` Yinghai Lu
2008-08-31  1:10                               ` Yinghai Lu
2008-08-31 12:27                                 ` Rafael J. Wysocki
2008-08-31 17:42                                   ` Linus Torvalds
2008-08-31 17:54                                     ` Yinghai Lu
2008-08-31 18:03                                       ` Linus Torvalds
2008-08-31 21:03                                         ` Yinghai Lu
2008-09-01 17:53                                           ` Linus Torvalds
2008-08-30 22:41                     ` Linus Torvalds
2008-08-30 22:50                       ` Yinghai Lu
2008-08-30 23:28                         ` Linus Torvalds
2008-08-30 23:39                           ` Yinghai Lu
2008-08-31  0:27                             ` Yinghai Lu
2008-08-31  0:50                               ` Yinghai Lu
2008-08-31  3:00                                 ` Linus Torvalds
2008-08-31  3:53                                   ` Yinghai Lu
2008-08-31  3:58                                     ` Linus Torvalds
2008-08-31  4:12                                       ` Linus Torvalds
2008-08-30 19:14               ` Linus Torvalds
2008-08-30 19:26                 ` Yinghai Lu
2008-08-30 19:41                   ` Linus Torvalds
2008-08-30 19:48                     ` Yinghai Lu
2008-08-30 19:29                 ` Rafael J. Wysocki
2008-08-30 19:29                   ` Yinghai Lu
2008-08-30 19:20           ` Rafael J. Wysocki
2008-08-29 22:34     ` Jeff Garzik
2008-08-29 22:47       ` Rafael J. Wysocki
2008-08-30 10:34 ` [PATCH] Re: Linux 2.6.27-rc5 Helge Deller
2008-08-30 20:21   ` Rafael J. Wysocki
2008-09-01 22:28   ` Al Viro
2008-08-31 23:27 ` J.A. Magallón
     [not found]   ` <328e43f00808311825r71164541pd4159a4a33b9b038@mail.gmail.com>
2008-09-01  7:12     ` Francois Romieu
2008-08-30  6:13 Linux 2.6.27-rc5: System boot regression caused by commit a2bd7274b47124d2fc4dfdb8c0591f545ba749dd David Witbrodt
2008-08-30  6:21 ` Linus Torvalds
2008-08-30  6:58 David Witbrodt
2008-08-30 23:29 David Witbrodt
2008-08-31  0:16 ` Yinghai Lu
2008-08-31  1:25 David Witbrodt
2008-08-31  2:17 ` Yinghai Lu

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=86802c440808301412k4e0b5562ie03ce41547ddab9a@mail.gmail.com \
    --to=yhlu.kernel@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=dawitbro@sbcglobal.net \
    --cc=htejun@gmail.com \
    --cc=jeff@garzik.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®