From: Nigel Cunningham <nigel@suspend2.net>
To: linux-kernel@vger.kernel.org
Subject: [Suspend2][ 03/10] [Suspend2] Atomic copy get_next_bit_on routine.
Date: Tue, 27 Jun 2006 14:38:56 +1000 [thread overview]
Message-ID: <20060627043855.14546.37822.stgit@nigel.suspend2.net> (raw)
In-Reply-To: <20060627043846.14546.75810.stgit@nigel.suspend2.net>
This routine is used find the next bit in a bitmap that is on. It is used
during the atomic restore of highmem pages.
Signed-off-by: Nigel Cunningham <nigel@suspend2.net>
kernel/power/atomic_copy.c | 60 ++++++++++++++++++++++++++++++++++++++++++++
1 files changed, 60 insertions(+), 0 deletions(-)
diff --git a/kernel/power/atomic_copy.c b/kernel/power/atomic_copy.c
index 07b418c..6d1bc68 100644
--- a/kernel/power/atomic_copy.c
+++ b/kernel/power/atomic_copy.c
@@ -75,3 +75,63 @@ static void suspend_init_nosave_zone_tab
}
}
+/**
+ * __suspend_get_next_bit_on: Atomic-copy safe location of next bit on in a bitmap.
+ *
+ * @bitmap: The bitmap we are traversing.
+ * @zone_num: Which zone we are in.
+ * @counter: The current pfn.
+ *
+ * A version of __get_next_bit_on that can be used when doing the atomic
+ * copy. While doing it, we can't rely on the zone information being in
+ * a constant location.
+ **/
+static unsigned long __suspend_get_next_bit_on(dyn_pageflags_t bitmap,
+ int *zone_num, long counter)
+{
+ unsigned long *ul_ptr = NULL;
+ int reset_ul_ptr = 1;
+ BUG_ON(*zone_num == num_zones);
+
+ if (counter == -1) {
+ *zone_num = 0;
+
+ /*
+ * Test the end because the start can validly
+ * be zero.
+ */
+ while (!zone_nosave[*zone_num].end_pfn)
+ (*zone_num)++;
+ counter = zone_nosave[*zone_num].start_pfn - 1;
+ }
+
+ do {
+ counter++;
+ if (counter > zone_nosave[*zone_num].end_pfn) {
+ (*zone_num)++;
+ while (!zone_nosave[*zone_num].end_pfn &&
+ *zone_num < num_zones)
+ (*zone_num)++;
+
+ if (*zone_num == num_zones)
+ return -1;
+ counter = zone_nosave[*zone_num].start_pfn;
+ reset_ul_ptr = 1;
+ } else
+ if (!(counter & BIT_NUM_MASK))
+ reset_ul_ptr = 1;
+
+ if (reset_ul_ptr) {
+ reset_ul_ptr = 0;
+ ul_ptr = PAGE_UL_PTR(bitmap, *zone_num,
+ (counter - zone_nosave[*zone_num].start_pfn));
+ if (!*ul_ptr) {
+ counter += BIT_NUM_MASK - 1;
+ continue;
+ }
+ }
+ } while(!test_bit(PAGEBIT(counter), ul_ptr));
+
+ return counter;
+}
+
--
Nigel Cunningham nigel at suspend2 dot net
next prev parent reply other threads:[~2006-06-27 5:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-27 4:38 [Suspend2][ 00/10] Suspend2 Atomic Copy Patches Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 01/10] [Suspend2] Atomic copy file header Nigel Cunningham
2006-06-27 4:38 ` [Suspend2][ 02/10] [Suspend2] Initialise nosave zone table Nigel Cunningham
2006-06-27 4:38 ` Nigel Cunningham [this message]
2006-06-27 4:39 ` [Suspend2][ 04/10] [Suspend2] Prepare pbe list for atomic restore Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 05/10] [Suspend2] Highmem copyback routine Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 06/10] [Suspend2] Post-atomic restore routine Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 07/10] [Suspend2] Post suspend context-save routine Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 08/10] [Suspend2] Atomic copy routine Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 09/10] [Suspend2] Atomic copy highlevel routine Nigel Cunningham
2006-06-27 4:39 ` [Suspend2][ 10/10] [Suspend2] Atomic restore " Nigel Cunningham
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=20060627043855.14546.37822.stgit@nigel.suspend2.net \
--to=nigel@suspend2.net \
--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
all inboxes | Powered by JetHome®