* [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
@ 2015-06-30 15:54 Chen Yu
2015-07-02 6:19 ` joeyli
0 siblings, 1 reply; 10+ messages in thread
From: Chen Yu @ 2015-06-30 15:54 UTC (permalink / raw)
To: linux-pm; +Cc: rafael.j.wysocki, rui.zhang, len.brown, aaron.lu, jlee, Chen Yu
Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
regions") was reverted, because this patch makes resume from hibernation
on Lenovo x230 unreliable. But reverting may bring back the kernel
exception firstly reported in former patch. In general, there are three
problems in current code when resuming from hibernation:
1.Resuming page may also be in second kernel's e820 reserved region.
BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
this causes kernel exception described in Commit 84c91b7ae07c
("PM / hibernate: avoid unsafe pages in e820 reserved regions")
2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
regions causes some regions at e820 table not page aligned,
e820_mark_nosave_regions will misjudgment the non-page aligned space to
be "hole" space and add to nosave regions, this causes resuming failed.
Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
3.e820 memory map inconsistence. Sometimes resuming system may have
larger memory capacity than the one before hibernation. If a strict
superset relationship is satisfied, it should be allowed to resume.
For example, use case of memory hotplug after hibernation.
e820 memory map before hibernation:
BIOS-e820: [mem 0x0000000020200000-0x0000000077517fff] usable
BIOS-e820: [mem 0x0000000077518000-0x0000000077567fff] reserved
e820 memory map during resuming:
BIOS-e820: [mem 0x0000000020200000-0x000000007753ffff] usable
BIOS-e820: [mem 0x0000000077540000-0x0000000077567fff] reserved
This patch solves above three problems, by checking whether each page to
be restored is strictly subset of current system's available memory zone
region. If it is, it's safe to continue, otherwise terminate.
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
---
kernel/power/snapshot.c | 69 ++++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 60 insertions(+), 9 deletions(-)
diff --git a/kernel/power/snapshot.c b/kernel/power/snapshot.c
index 5235dd4..ebbb995 100644
--- a/kernel/power/snapshot.c
+++ b/kernel/power/snapshot.c
@@ -881,6 +881,9 @@ static struct memory_bitmap *forbidden_pages_map;
/* Set bits in this map correspond to free page frames. */
static struct memory_bitmap *free_pages_map;
+/* Set bits in this map correspond to all valie page frames. */
+static struct memory_bitmap *valid_pages_map;
+
/*
* Each page frame allocated for creating the image is marked by setting the
* corresponding bits in forbidden_pages_map and free_pages_map simultaneously
@@ -922,6 +925,11 @@ static void swsusp_unset_page_forbidden(struct page *page)
memory_bm_clear_bit(forbidden_pages_map, page_to_pfn(page));
}
+int swsusp_page_is_valid(struct page *page)
+{
+ return valid_pages_map ?
+ memory_bm_test_bit(valid_pages_map, page_to_pfn(page)) : 0;
+}
/**
* mark_nosave_pages - set bits corresponding to the page frames the
* contents of which should not be saved in a given bitmap.
@@ -955,6 +963,31 @@ static void mark_nosave_pages(struct memory_bitmap *bm)
}
}
+/* mark_valid_pages - set bits corresponding to all page frames */
+static void mark_valid_pages(struct memory_bitmap *bm)
+{
+ struct zone *zone;
+ unsigned long pfn, max_zone_pfn;
+
+ for_each_populated_zone(zone) {
+ max_zone_pfn = zone_end_pfn(zone);
+ for (pfn = zone->zone_start_pfn; pfn < max_zone_pfn; pfn++)
+ if (pfn_valid(pfn))
+ mem_bm_set_bit_check(bm, pfn);
+ }
+}
+
+static bool is_valid_orig_page(unsigned long pfn)
+{
+ if (!swsusp_page_is_valid(pfn_to_page(pfn))) {
+ pr_err(
+ "PM: %#010llx to restored not in current valid memory region\n",
+ (unsigned long long) pfn << PAGE_SHIFT);
+ return false;
+ } else
+ return true;
+}
+
/**
* create_basic_memory_bitmaps - create bitmaps needed for marking page
* frames that should not be saved and free page frames. The pointers
@@ -965,13 +998,15 @@ static void mark_nosave_pages(struct memory_bitmap *bm)
int create_basic_memory_bitmaps(void)
{
- struct memory_bitmap *bm1, *bm2;
+ struct memory_bitmap *bm1, *bm2, *bm3;
int error = 0;
- if (forbidden_pages_map && free_pages_map)
+ if (forbidden_pages_map && free_pages_map &&
+ valid_pages_map)
return 0;
else
- BUG_ON(forbidden_pages_map || free_pages_map);
+ BUG_ON(forbidden_pages_map || free_pages_map ||
+ valid_pages_map);
bm1 = kzalloc(sizeof(struct memory_bitmap), GFP_KERNEL);
if (!bm1)
@@ -989,14 +1024,27 @@ int create_basic_memory_bitmaps(void)
if (error)
goto Free_second_object;
+ bm3 = kzalloc(sizeof(struct memory_bitmap), GFP_KERNEL);
+ if (!bm3)
+ goto Free_second_bitmap;
+
+ error = memory_bm_create(bm3, GFP_KERNEL, PG_ANY);
+ if (error)
+ goto Free_third_object;
+
forbidden_pages_map = bm1;
free_pages_map = bm2;
+ valid_pages_map = bm3;
mark_nosave_pages(forbidden_pages_map);
-
+ mark_valid_pages(valid_pages_map);
pr_debug("PM: Basic memory bitmaps created\n");
return 0;
+ Free_third_object:
+ kfree(bm3);
+ Free_second_bitmap:
+ memory_bm_free(bm2, PG_UNSAFE_CLEAR);
Free_second_object:
kfree(bm2);
Free_first_bitmap:
@@ -1015,19 +1063,24 @@ int create_basic_memory_bitmaps(void)
void free_basic_memory_bitmaps(void)
{
- struct memory_bitmap *bm1, *bm2;
+ struct memory_bitmap *bm1, *bm2, *bm3;
- if (WARN_ON(!(forbidden_pages_map && free_pages_map)))
+ if (WARN_ON(!(forbidden_pages_map && free_pages_map &&
+ valid_pages_map)))
return;
bm1 = forbidden_pages_map;
bm2 = free_pages_map;
+ bm3 = valid_pages_map;
forbidden_pages_map = NULL;
free_pages_map = NULL;
+ valid_pages_map = NULL;
memory_bm_free(bm1, PG_UNSAFE_CLEAR);
kfree(bm1);
memory_bm_free(bm2, PG_UNSAFE_CLEAR);
kfree(bm2);
+ memory_bm_free(bm3, PG_UNSAFE_CLEAR);
+ kfree(bm3);
pr_debug("PM: Basic memory bitmaps freed\n");
}
@@ -2023,7 +2076,7 @@ static int mark_unsafe_pages(struct memory_bitmap *bm)
do {
pfn = memory_bm_next_pfn(bm);
if (likely(pfn != BM_END_OF_MAP)) {
- if (likely(pfn_valid(pfn)))
+ if (likely(pfn_valid(pfn)) && is_valid_orig_page(pfn))
swsusp_set_page_free(pfn_to_page(pfn));
else
return -EFAULT;
@@ -2053,8 +2106,6 @@ static int check_header(struct swsusp_info *info)
char *reason;
reason = check_image_kernel(info);
- if (!reason && info->num_physpages != get_num_physpages())
- reason = "memory size";
if (reason) {
printk(KERN_ERR "PM: Image mismatch: %s\n", reason);
return -EPERM;
--
1.9.1
^ permalink raw reply related [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-06-30 15:54 [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones Chen Yu
@ 2015-07-02 6:19 ` joeyli
2015-07-02 8:00 ` chenyu5
0 siblings, 1 reply; 10+ messages in thread
From: joeyli @ 2015-07-02 6:19 UTC (permalink / raw)
To: Chen Yu; +Cc: linux-pm, rafael.j.wysocki, rui.zhang, len.brown, aaron.lu
Hi Chen Yu,
On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
> regions") was reverted, because this patch makes resume from hibernation
> on Lenovo x230 unreliable. But reverting may bring back the kernel
> exception firstly reported in former patch. In general, there are three
> problems in current code when resuming from hibernation:
>
> 1.Resuming page may also be in second kernel's e820 reserved region.
> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
> this causes kernel exception described in Commit 84c91b7ae07c
> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
>
> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
> regions causes some regions at e820 table not page aligned,
> e820_mark_nosave_regions will misjudgment the non-page aligned space to
> be "hole" space and add to nosave regions, this causes resuming failed.
> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
>
Sorry for I am not fully understand why checking pfn_valid could avoid
the above 2. issue?
Per my understood should waiting Yinghai Lu's patches for killing
E820_RESERVED_KERN to avoid the aligned problem.
Thanks a lot!
Joey Lee
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-02 6:19 ` joeyli
@ 2015-07-02 8:00 ` chenyu5
2015-07-06 8:37 ` joeyli
0 siblings, 1 reply; 10+ messages in thread
From: chenyu5 @ 2015-07-02 8:00 UTC (permalink / raw)
To: joeyli
Cc: linux-pm, rafael.j.wysocki, rui.zhang, len.brown, aaron.lu,
ying.huang
Hi, Joey
thanks for your reply,
On 2015年07月02日 14:19, joeyli wrote:
> Hi Chen Yu,
>
> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
>> regions") was reverted, because this patch makes resume from hibernation
>> on Lenovo x230 unreliable. But reverting may bring back the kernel
>> exception firstly reported in former patch. In general, there are three
>> problems in current code when resuming from hibernation:
>>
>> 1.Resuming page may also be in second kernel's e820 reserved region.
>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
>> this causes kernel exception described in Commit 84c91b7ae07c
>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
>>
>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
>> reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
>> regions causes some regions at e820 table not page aligned,
>> e820_mark_nosave_regions will misjudgment the non-page aligned space to
>> be "hole" space and add to nosave regions, this causes resuming failed.
>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
>>
>
> Sorry for I am not fully understand why checking pfn_valid could avoid
> the above 2. issue?
>
[Yu] According to e820_mark_nosave_regions, two kinds of e820
regions will be regarded as nosave:
a.e820.map holes between each e820entry
b.e820entry with (!E820_RAM && !E820_RESERVED_KERN)
dmesg in
https://bugzilla.kernel.org/show_bug.cgi?id=96111
shows that:
BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057] usable
PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
e820 map was changed by situation a, but it should not be added to
nosave list, right?
and according to saveable_page, only pages in the zone will be saved:
if (page_zone(page_ != zone)
return NULL;
The function of is_valid_orig_page in this patch treats setup_data as
valid page, so I think this workaround issue 2.
> Per my understood should waiting Yinghai Lu's patches for killing
> E820_RESERVED_KERN to avoid the aligned problem.
[Yu] yes, it is a graceful solution, but I don't see that in 4.1? And
we encountered problem 3 in our testing enviroment, so I wrote a patch
to deal with it first.
>
>
> Thanks a lot!
> Joey Lee
>
Best Regards,
Yu
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-02 8:00 ` chenyu5
@ 2015-07-06 8:37 ` joeyli
2015-07-16 0:30 ` Rafael J. Wysocki
0 siblings, 1 reply; 10+ messages in thread
From: joeyli @ 2015-07-06 8:37 UTC (permalink / raw)
To: chenyu5
Cc: linux-pm, rafael.j.wysocki, rui.zhang, len.brown, aaron.lu,
ying.huang
Hi Chen Yu,
On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
> Hi, Joey
> thanks for your reply,
>
> On 2015年07月02日 14:19, joeyli wrote:
> >Hi Chen Yu,
> >
> >On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> >>Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
> >>regions") was reverted, because this patch makes resume from hibernation
> >>on Lenovo x230 unreliable. But reverting may bring back the kernel
> >>exception firstly reported in former patch. In general, there are three
> >>problems in current code when resuming from hibernation:
> >>
> >>1.Resuming page may also be in second kernel's e820 reserved region.
> >>BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
> >>this causes kernel exception described in Commit 84c91b7ae07c
> >>("PM / hibernate: avoid unsafe pages in e820 reserved regions")
> >>
> >>2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> >>reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
> >>regions causes some regions at e820 table not page aligned,
> >>e820_mark_nosave_regions will misjudgment the non-page aligned space to
> >>be "hole" space and add to nosave regions, this causes resuming failed.
> >>Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
> >>
> >
> >Sorry for I am not fully understand why checking pfn_valid could avoid
> >the above 2. issue?
> >
> [Yu] According to e820_mark_nosave_regions, two kinds of e820
> regions will be regarded as nosave:
> a.e820.map holes between each e820entry
> b.e820entry with (!E820_RAM && !E820_RESERVED_KERN)
> dmesg in
> https://bugzilla.kernel.org/show_bug.cgi?id=96111
> shows that:
>
> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057] usable
> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
>
> e820 map was changed by situation a, but it should not be added to
> nosave list, right?
>
> and according to saveable_page, only pages in the zone will be saved:
> if (page_zone(page_ != zone)
> return NULL;
>
> The function of is_valid_orig_page in this patch treats setup_data as
> valid page, so I think this workaround issue 2.
>
>
> >Per my understood should waiting Yinghai Lu's patches for killing
> >E820_RESERVED_KERN to avoid the aligned problem.
> [Yu] yes, it is a graceful solution, but I don't see that in 4.1? And
> we encountered problem 3 in our testing enviroment, so I wrote a patch
> to deal with it first.
> >
> >
> >Thanks a lot!
> >Joey Lee
> >
Thanks for your explanation, then your patch makes sense to me.
Please feel free to add tag:
Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
Thanks a lot!
Joey Lee
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-06 8:37 ` joeyli
@ 2015-07-16 0:30 ` Rafael J. Wysocki
2015-07-21 1:28 ` chenyu5
0 siblings, 1 reply; 10+ messages in thread
From: Rafael J. Wysocki @ 2015-07-16 0:30 UTC (permalink / raw)
To: joeyli
Cc: chenyu5, linux-pm, rafael.j.wysocki, rui.zhang, len.brown,
aaron.lu, ying.huang
On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
> Hi Chen Yu,
>
> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
> > Hi, Joey
> > thanks for your reply,
> >
> > On 2015年07月02日 14:19, joeyli wrote:
> > >Hi Chen Yu,
> > >
> > >On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> > >>Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
> > >>regions") was reverted, because this patch makes resume from hibernation
> > >>on Lenovo x230 unreliable. But reverting may bring back the kernel
> > >>exception firstly reported in former patch. In general, there are three
> > >>problems in current code when resuming from hibernation:
> > >>
> > >>1.Resuming page may also be in second kernel's e820 reserved region.
> > >>BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
> > >>this causes kernel exception described in Commit 84c91b7ae07c
> > >>("PM / hibernate: avoid unsafe pages in e820 reserved regions")
> > >>
> > >>2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> > >>reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
> > >>regions causes some regions at e820 table not page aligned,
> > >>e820_mark_nosave_regions will misjudgment the non-page aligned space to
> > >>be "hole" space and add to nosave regions, this causes resuming failed.
> > >>Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
> > >>
> > >
> > >Sorry for I am not fully understand why checking pfn_valid could avoid
> > >the above 2. issue?
> > >
> > [Yu] According to e820_mark_nosave_regions, two kinds of e820
> > regions will be regarded as nosave:
> > a.e820.map holes between each e820entry
> > b.e820entry with (!E820_RAM && !E820_RESERVED_KERN)
> > dmesg in
> > https://bugzilla.kernel.org/show_bug.cgi?id=96111
> > shows that:
> >
> > BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
> > reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057] usable
> > PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
> >
> > e820 map was changed by situation a, but it should not be added to
> > nosave list, right?
> >
> > and according to saveable_page, only pages in the zone will be saved:
> > if (page_zone(page_ != zone)
> > return NULL;
> >
> > The function of is_valid_orig_page in this patch treats setup_data as
> > valid page, so I think this workaround issue 2.
> >
> >
> > >Per my understood should waiting Yinghai Lu's patches for killing
> > >E820_RESERVED_KERN to avoid the aligned problem.
> > [Yu] yes, it is a graceful solution, but I don't see that in 4.1? And
> > we encountered problem 3 in our testing enviroment, so I wrote a patch
> > to deal with it first.
> > >
> > >
> > >Thanks a lot!
> > >Joey Lee
> > >
>
> Thanks for your explanation, then your patch makes sense to me.
>
> Please feel free to add tag:
>
> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
Patch queued up for 4.3, thanks!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-16 0:30 ` Rafael J. Wysocki
@ 2015-07-21 1:28 ` chenyu5
2015-07-22 1:03 ` Rafael J. Wysocki
0 siblings, 1 reply; 10+ messages in thread
From: chenyu5 @ 2015-07-21 1:28 UTC (permalink / raw)
To: Rafael J. Wysocki; +Cc: linux-pm, rafael.j.wysocki, joeyli, yex.tian
On 2015年07月16日 08:30, Rafael J. Wysocki wrote:
> On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
>> Hi Chen Yu,
>>
>> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
>>> Hi, Joey
>>> thanks for your reply,
>>>
>>> On 2015年07月02日 14:19, joeyli wrote:
>>>> Hi Chen Yu,
>>>>
>>>> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
>>>>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
>>>>> regions") was reverted, because this patch makes resume from hibernation
>>>>> on Lenovo x230 unreliable. But reverting may bring back the kernel
>>>>> exception firstly reported in former patch. In general, there are three
>>>>> problems in current code when resuming from hibernation:
>>>>>
>>>>> 1.Resuming page may also be in second kernel's e820 reserved region.
>>>>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
>>>>> this causes kernel exception described in Commit 84c91b7ae07c
>>>>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
>>>>>
>>>>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
>>>>> reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
>>>>> regions causes some regions at e820 table not page aligned,
>>>>> e820_mark_nosave_regions will misjudgment the non-page aligned space to
>>>>> be "hole" space and add to nosave regions, this causes resuming failed.
>>>>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
>>>>>
>>>>
>>>> Sorry for I am not fully understand why checking pfn_valid could avoid
>>>> the above 2. issue?
>>>>
>>> [Yu] According to e820_mark_nosave_regions, two kinds of e820
>>> regions will be regarded as nosave:
>>> a.e820.map holes between each e820entry
>>> b.e820entry with (!E820_RAM && !E820_RESERVED_KERN)
>>> dmesg in
>>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
>>> shows that:
>>>
>>> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
>>> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057] usable
>>> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
>>>
>>> e820 map was changed by situation a, but it should not be added to
>>> nosave list, right?
>>>
>>> and according to saveable_page, only pages in the zone will be saved:
>>> if (page_zone(page_ != zone)
>>> return NULL;
>>>
>>> The function of is_valid_orig_page in this patch treats setup_data as
>>> valid page, so I think this workaround issue 2.
>>>
>>>
>>>> Per my understood should waiting Yinghai Lu's patches for killing
>>>> E820_RESERVED_KERN to avoid the aligned problem.
>>> [Yu] yes, it is a graceful solution, but I don't see that in 4.1? And
>>> we encountered problem 3 in our testing enviroment, so I wrote a patch
>>> to deal with it first.
>>>>
>>>>
>>>> Thanks a lot!
>>>> Joey Lee
>>>>
>>
>> Thanks for your explanation, then your patch makes sense to me.
>>
>> Please feel free to add tag:
>>
>> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
>
> Patch queued up for 4.3, thanks!
>
Hi Rafeal,
Please help drop this patch for now, QA has
found some problems with this patch applied,
we're working on it now. Sorry for inconvenience.
Regards,
Yu
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-21 1:28 ` chenyu5
@ 2015-07-22 1:03 ` Rafael J. Wysocki
2015-07-22 8:58 ` Chen, Yu C
0 siblings, 1 reply; 10+ messages in thread
From: Rafael J. Wysocki @ 2015-07-22 1:03 UTC (permalink / raw)
To: chenyu5; +Cc: linux-pm, rafael.j.wysocki, joeyli, yex.tian
On Tuesday, July 21, 2015 09:28:32 AM chenyu5 wrote:
> On 2015年07月16日 08:30, Rafael J. Wysocki wrote:
> > On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
> >> Hi Chen Yu,
> >>
> >> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
> >>> Hi, Joey
> >>> thanks for your reply,
> >>>
> >>> On 2015年07月02日 14:19, joeyli wrote:
> >>>> Hi Chen Yu,
> >>>>
> >>>> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> >>>>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820 reserved
> >>>>> regions") was reverted, because this patch makes resume from hibernation
> >>>>> on Lenovo x230 unreliable. But reverting may bring back the kernel
> >>>>> exception firstly reported in former patch. In general, there are three
> >>>>> problems in current code when resuming from hibernation:
> >>>>>
> >>>>> 1.Resuming page may also be in second kernel's e820 reserved region.
> >>>>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff] reserved
> >>>>> this causes kernel exception described in Commit 84c91b7ae07c
> >>>>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
> >>>>>
> >>>>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> >>>>> reserved regions") is applied to fix problem 1, and if E820_RESERVED_KERN
> >>>>> regions causes some regions at e820 table not page aligned,
> >>>>> e820_mark_nosave_regions will misjudgment the non-page aligned space to
> >>>>> be "hole" space and add to nosave regions, this causes resuming failed.
> >>>>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for detail.
> >>>>>
> >>>>
> >>>> Sorry for I am not fully understand why checking pfn_valid could avoid
> >>>> the above 2. issue?
> >>>>
> >>> [Yu] According to e820_mark_nosave_regions, two kinds of e820
> >>> regions will be regarded as nosave:
> >>> a.e820.map holes between each e820entry
> >>> b.e820entry with (!E820_RAM && !E820_RESERVED_KERN)
> >>> dmesg in
> >>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
> >>> shows that:
> >>>
> >>> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
> >>> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057] usable
> >>> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
> >>>
> >>> e820 map was changed by situation a, but it should not be added to
> >>> nosave list, right?
> >>>
> >>> and according to saveable_page, only pages in the zone will be saved:
> >>> if (page_zone(page_ != zone)
> >>> return NULL;
> >>>
> >>> The function of is_valid_orig_page in this patch treats setup_data as
> >>> valid page, so I think this workaround issue 2.
> >>>
> >>>
> >>>> Per my understood should waiting Yinghai Lu's patches for killing
> >>>> E820_RESERVED_KERN to avoid the aligned problem.
> >>> [Yu] yes, it is a graceful solution, but I don't see that in 4.1? And
> >>> we encountered problem 3 in our testing enviroment, so I wrote a patch
> >>> to deal with it first.
> >>>>
> >>>>
> >>>> Thanks a lot!
> >>>> Joey Lee
> >>>>
> >>
> >> Thanks for your explanation, then your patch makes sense to me.
> >>
> >> Please feel free to add tag:
> >>
> >> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> >
> > Patch queued up for 4.3, thanks!
> >
> Hi Rafeal,
> Please help drop this patch for now, QA has
> found some problems with this patch applied,
> we're working on it now. Sorry for inconvenience.
Dropping, thanks for the heads up!
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply [flat|nested] 10+ messages in thread* RE: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-22 1:03 ` Rafael J. Wysocki
@ 2015-07-22 8:58 ` Chen, Yu C
2015-07-23 5:34 ` joeyli
0 siblings, 1 reply; 10+ messages in thread
From: Chen, Yu C @ 2015-07-22 8:58 UTC (permalink / raw)
To: Rafael J. Wysocki, joeyli
Cc: linux-pm@vger.kernel.org, Wysocki, Rafael J, Tian, YeX
> -----Original Message-----
> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
> Sent: Wednesday, July 22, 2015 9:04 AM
> To: Chen, Yu C
> Cc: linux-pm@vger.kernel.org; Wysocki, Rafael J; joeyli; Tian, YeX
> Subject: Re: [RFC PATCH] PM / hibernate: make sure each resuming page is
> in current memory zones
>
> On Tuesday, July 21, 2015 09:28:32 AM chenyu5 wrote:
> > On 2015年07月16日 08:30, Rafael J. Wysocki wrote:
> > > On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
> > >> Hi Chen Yu,
> > >>
> > >> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
> > >>> Hi, Joey
> > >>> thanks for your reply,
> > >>>
> > >>> On 2015年07月02日 14:19, joeyli wrote:
> > >>>> Hi Chen Yu,
> > >>>>
> > >>>> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> > >>>>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> > >>>>> reserved
> > >>>>> regions") was reverted, because this patch makes resume from
> > >>>>> hibernation on Lenovo x230 unreliable. But reverting may bring
> > >>>>> back the kernel exception firstly reported in former patch. In
> > >>>>> general, there are three problems in current code when resuming
> from hibernation:
> > >>>>>
> > >>>>> 1.Resuming page may also be in second kernel's e820 reserved
> region.
> > >>>>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff]
> reserved
> > >>>>> this causes kernel exception described in Commit 84c91b7ae07c
> > >>>>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
> > >>>>>
> > >>>>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in
> > >>>>> e820 reserved regions") is applied to fix problem 1, and if
> > >>>>> E820_RESERVED_KERN regions causes some regions at e820 table
> not
> > >>>>> page aligned, e820_mark_nosave_regions will misjudgment the
> > >>>>> non-page aligned space to be "hole" space and add to nosave
> regions, this causes resuming failed.
> > >>>>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for
> detail.
> > >>>>>
> > >>>>
> > >>>> Sorry for I am not fully understand why checking pfn_valid could
> > >>>> avoid the above 2. issue?
> > >>>>
> > >>> [Yu] According to e820_mark_nosave_regions, two kinds of e820
> > >>> regions will be regarded as nosave:
> > >>> a.e820.map holes between each e820entry b.e820entry with
> > >>> (!E820_RAM && !E820_RESERVED_KERN) dmesg in
> > >>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
> > >>> shows that:
> > >>>
> > >>> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
> > >>> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057]
> > >>> usable
> > >>> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
> > >>>
> > >>> e820 map was changed by situation a, but it should not be added to
> > >>> nosave list, right?
> > >>>
> > >>> and according to saveable_page, only pages in the zone will be saved:
> > >>> if (page_zone(page_ != zone)
> > >>> return NULL;
> > >>>
> > >>> The function of is_valid_orig_page in this patch treats setup_data
> > >>> as valid page, so I think this workaround issue 2.
> > >>>
> > >>>
> > >>>> Per my understood should waiting Yinghai Lu's patches for killing
> > >>>> E820_RESERVED_KERN to avoid the aligned problem.
> > >>> [Yu] yes, it is a graceful solution, but I don't see that in 4.1?
> > >>> And we encountered problem 3 in our testing enviroment, so I wrote
> > >>> a patch to deal with it first.
> > >>>>
> > >>>>
> > >>>> Thanks a lot!
> > >>>> Joey Lee
> > >>>>
> > >>
> > >> Thanks for your explanation, then your patch makes sense to me.
> > >>
> > >> Please feel free to add tag:
> > >>
> > >> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> > >
> > > Patch queued up for 4.3, thanks!
> > >
> > Hi Rafeal,
> > Please help drop this patch for now, QA has found some problems with
> > this patch applied, we're working on it now. Sorry for inconvenience.
>
> Dropping, thanks for the heads up!
>
Hi,Rafeal, Joey
I've sent out another patch, it is based on Joey's
original patch, and it treats any adjacent E820_RAM/E820_RESERVED_KERN regions as
one. In this way, non-page-aligned setup_data address would not be added
to nosave regions, thus workaround the hibernation failor mentiones in
https://bugzilla.kernel.org/show_bug.cgi?id=96111
V1 patch has a problem that, NOT every page in page zone has a valid mapping address , thus
accessing these pages would cause problem. So I rewrite this path and send out another V2 version.
Thanks for your time.
Yu
>
> --
> I speak only for myself.
> Rafael J. Wysocki, Intel Open Source Technology Center.
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-22 8:58 ` Chen, Yu C
@ 2015-07-23 5:34 ` joeyli
2015-07-23 5:42 ` chenyu5
0 siblings, 1 reply; 10+ messages in thread
From: joeyli @ 2015-07-23 5:34 UTC (permalink / raw)
To: Chen, Yu C
Cc: Rafael J. Wysocki, linux-pm@vger.kernel.org, Wysocki, Rafael J,
Tian, YeX
Hi Chen Yu,
On Wed, Jul 22, 2015 at 08:58:11AM +0000, Chen, Yu C wrote:
>
>
> > -----Original Message-----
> > From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
> > Sent: Wednesday, July 22, 2015 9:04 AM
> > To: Chen, Yu C
> > Cc: linux-pm@vger.kernel.org; Wysocki, Rafael J; joeyli; Tian, YeX
> > Subject: Re: [RFC PATCH] PM / hibernate: make sure each resuming page is
> > in current memory zones
> >
> > On Tuesday, July 21, 2015 09:28:32 AM chenyu5 wrote:
> > > On 2015年07月16日 08:30, Rafael J. Wysocki wrote:
> > > > On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
> > > >> Hi Chen Yu,
> > > >>
> > > >> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
> > > >>> Hi, Joey
> > > >>> thanks for your reply,
> > > >>>
> > > >>> On 2015年07月02日 14:19, joeyli wrote:
> > > >>>> Hi Chen Yu,
> > > >>>>
> > > >>>> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
> > > >>>>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
> > > >>>>> reserved
> > > >>>>> regions") was reverted, because this patch makes resume from
> > > >>>>> hibernation on Lenovo x230 unreliable. But reverting may bring
> > > >>>>> back the kernel exception firstly reported in former patch. In
> > > >>>>> general, there are three problems in current code when resuming
> > from hibernation:
> > > >>>>>
> > > >>>>> 1.Resuming page may also be in second kernel's e820 reserved
> > region.
> > > >>>>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff]
> > reserved
> > > >>>>> this causes kernel exception described in Commit 84c91b7ae07c
> > > >>>>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
> > > >>>>>
> > > >>>>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in
> > > >>>>> e820 reserved regions") is applied to fix problem 1, and if
> > > >>>>> E820_RESERVED_KERN regions causes some regions at e820 table
> > not
> > > >>>>> page aligned, e820_mark_nosave_regions will misjudgment the
> > > >>>>> non-page aligned space to be "hole" space and add to nosave
> > regions, this causes resuming failed.
> > > >>>>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for
> > detail.
> > > >>>>>
> > > >>>>
> > > >>>> Sorry for I am not fully understand why checking pfn_valid could
> > > >>>> avoid the above 2. issue?
> > > >>>>
> > > >>> [Yu] According to e820_mark_nosave_regions, two kinds of e820
> > > >>> regions will be regarded as nosave:
> > > >>> a.e820.map holes between each e820entry b.e820entry with
> > > >>> (!E820_RAM && !E820_RESERVED_KERN) dmesg in
> > > >>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
> > > >>> shows that:
> > > >>>
> > > >>> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
> > > >>> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057]
> > > >>> usable
> > > >>> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
> > > >>>
> > > >>> e820 map was changed by situation a, but it should not be added to
> > > >>> nosave list, right?
> > > >>>
> > > >>> and according to saveable_page, only pages in the zone will be saved:
> > > >>> if (page_zone(page_ != zone)
> > > >>> return NULL;
> > > >>>
> > > >>> The function of is_valid_orig_page in this patch treats setup_data
> > > >>> as valid page, so I think this workaround issue 2.
> > > >>>
> > > >>>
> > > >>>> Per my understood should waiting Yinghai Lu's patches for killing
> > > >>>> E820_RESERVED_KERN to avoid the aligned problem.
> > > >>> [Yu] yes, it is a graceful solution, but I don't see that in 4.1?
> > > >>> And we encountered problem 3 in our testing enviroment, so I wrote
> > > >>> a patch to deal with it first.
> > > >>>>
> > > >>>>
> > > >>>> Thanks a lot!
> > > >>>> Joey Lee
> > > >>>>
> > > >>
> > > >> Thanks for your explanation, then your patch makes sense to me.
> > > >>
> > > >> Please feel free to add tag:
> > > >>
> > > >> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
> > > >
> > > > Patch queued up for 4.3, thanks!
> > > >
> > > Hi Rafeal,
> > > Please help drop this patch for now, QA has found some problems with
> > > this patch applied, we're working on it now. Sorry for inconvenience.
> >
> > Dropping, thanks for the heads up!
> >
> Hi,Rafeal, Joey
> I've sent out another patch, it is based on Joey's
> original patch, and it treats any adjacent E820_RAM/E820_RESERVED_KERN regions as
> one. In this way, non-page-aligned setup_data address would not be added
> to nosave regions, thus workaround the hibernation failor mentiones in
> https://bugzilla.kernel.org/show_bug.cgi?id=96111
>
> V1 patch has a problem that, NOT every page in page zone has a valid mapping address , thus
> accessing these pages would cause problem. So I rewrite this path and send out another V2 version.
> Thanks for your time.
>
> Yu
> >
Thanks for your work on this patch, but the E820_RESERVED_KERN will be removed
anyhow. So I prefer waiting Yinghai Lu's patch for killing E820_RESERVED_KERN.
Regards
Joey Lee
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones
2015-07-23 5:34 ` joeyli
@ 2015-07-23 5:42 ` chenyu5
0 siblings, 0 replies; 10+ messages in thread
From: chenyu5 @ 2015-07-23 5:42 UTC (permalink / raw)
To: joeyli
Cc: Rafael J. Wysocki, linux-pm@vger.kernel.org, Wysocki, Rafael J,
Tian, YeX
On 2015年07月23日 13:34, joeyli wrote:
> Hi Chen Yu,
>
> On Wed, Jul 22, 2015 at 08:58:11AM +0000, Chen, Yu C wrote:
>>
>>
>>> -----Original Message-----
>>> From: Rafael J. Wysocki [mailto:rjw@rjwysocki.net]
>>> Sent: Wednesday, July 22, 2015 9:04 AM
>>> To: Chen, Yu C
>>> Cc: linux-pm@vger.kernel.org; Wysocki, Rafael J; joeyli; Tian, YeX
>>> Subject: Re: [RFC PATCH] PM / hibernate: make sure each resuming page is
>>> in current memory zones
>>>
>>> On Tuesday, July 21, 2015 09:28:32 AM chenyu5 wrote:
>>>> On 2015年07月16日 08:30, Rafael J. Wysocki wrote:
>>>>> On Monday, July 06, 2015 04:37:39 PM joeyli wrote:
>>>>>> Hi Chen Yu,
>>>>>>
>>>>>> On Thu, Jul 02, 2015 at 04:00:42PM +0800, chenyu5 wrote:
>>>>>>> Hi, Joey
>>>>>>> thanks for your reply,
>>>>>>>
>>>>>>> On 2015年07月02日 14:19, joeyli wrote:
>>>>>>>> Hi Chen Yu,
>>>>>>>>
>>>>>>>> On Tue, Jun 30, 2015 at 11:54:28PM +0800, Chen Yu wrote:
>>>>>>>>> Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in e820
>>>>>>>>> reserved
>>>>>>>>> regions") was reverted, because this patch makes resume from
>>>>>>>>> hibernation on Lenovo x230 unreliable. But reverting may bring
>>>>>>>>> back the kernel exception firstly reported in former patch. In
>>>>>>>>> general, there are three problems in current code when resuming
>>> from hibernation:
>>>>>>>>>
>>>>>>>>> 1.Resuming page may also be in second kernel's e820 reserved
>>> region.
>>>>>>>>> BIOS-e820: [mem 0x0000000069d4f000-0x0000000069e12fff]
>>> reserved
>>>>>>>>> this causes kernel exception described in Commit 84c91b7ae07c
>>>>>>>>> ("PM / hibernate: avoid unsafe pages in e820 reserved regions")
>>>>>>>>>
>>>>>>>>> 2.If Commit 84c91b7ae07c ("PM / hibernate: avoid unsafe pages in
>>>>>>>>> e820 reserved regions") is applied to fix problem 1, and if
>>>>>>>>> E820_RESERVED_KERN regions causes some regions at e820 table
>>> not
>>>>>>>>> page aligned, e820_mark_nosave_regions will misjudgment the
>>>>>>>>> non-page aligned space to be "hole" space and add to nosave
>>> regions, this causes resuming failed.
>>>>>>>>> Refer to https://bugzilla.kernel.org/show_bug.cgi?id=96111 for
>>> detail.
>>>>>>>>>
>>>>>>>>
>>>>>>>> Sorry for I am not fully understand why checking pfn_valid could
>>>>>>>> avoid the above 2. issue?
>>>>>>>>
>>>>>>> [Yu] According to e820_mark_nosave_regions, two kinds of e820
>>>>>>> regions will be regarded as nosave:
>>>>>>> a.e820.map holes between each e820entry b.e820entry with
>>>>>>> (!E820_RAM && !E820_RESERVED_KERN) dmesg in
>>>>>>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
>>>>>>> shows that:
>>>>>>>
>>>>>>> BIOS-e820: [mem 0x000000005baff000-0x00000000d684ffff] usable
>>>>>>> reserve setup_data: [mem 0x000000009d3e0018-0x000000009d3f0057]
>>>>>>> usable
>>>>>>> PM: Registered nosave memory: [mem 0x9d3e0000-0x9d3e0fff]
>>>>>>>
>>>>>>> e820 map was changed by situation a, but it should not be added to
>>>>>>> nosave list, right?
>>>>>>>
>>>>>>> and according to saveable_page, only pages in the zone will be saved:
>>>>>>> if (page_zone(page_ != zone)
>>>>>>> return NULL;
>>>>>>>
>>>>>>> The function of is_valid_orig_page in this patch treats setup_data
>>>>>>> as valid page, so I think this workaround issue 2.
>>>>>>>
>>>>>>>
>>>>>>>> Per my understood should waiting Yinghai Lu's patches for killing
>>>>>>>> E820_RESERVED_KERN to avoid the aligned problem.
>>>>>>> [Yu] yes, it is a graceful solution, but I don't see that in 4.1?
>>>>>>> And we encountered problem 3 in our testing enviroment, so I wrote
>>>>>>> a patch to deal with it first.
>>>>>>>>
>>>>>>>>
>>>>>>>> Thanks a lot!
>>>>>>>> Joey Lee
>>>>>>>>
>>>>>>
>>>>>> Thanks for your explanation, then your patch makes sense to me.
>>>>>>
>>>>>> Please feel free to add tag:
>>>>>>
>>>>>> Reviewed-by: Lee, Chun-Yi <joeyli.kernel@gmail.com>
>>>>>
>>>>> Patch queued up for 4.3, thanks!
>>>>>
>>>> Hi Rafeal,
>>>> Please help drop this patch for now, QA has found some problems with
>>>> this patch applied, we're working on it now. Sorry for inconvenience.
>>>
>>> Dropping, thanks for the heads up!
>>>
>> Hi,Rafeal, Joey
>> I've sent out another patch, it is based on Joey's
>> original patch, and it treats any adjacent E820_RAM/E820_RESERVED_KERN regions as
>> one. In this way, non-page-aligned setup_data address would not be added
>> to nosave regions, thus workaround the hibernation failor mentiones in
>> https://bugzilla.kernel.org/show_bug.cgi?id=96111
>>
>> V1 patch has a problem that, NOT every page in page zone has a valid mapping address , thus
>> accessing these pages would cause problem. So I rewrite this path and send out another V2 version.
>> Thanks for your time.
>>
>> Yu
>>>
>
> Thanks for your work on this patch, but the E820_RESERVED_KERN will be removed
> anyhow. So I prefer waiting Yinghai Lu's patch for killing E820_RESERVED_KERN.
>
OK. I'll wait for Yinghai's patch and yours.
Thanks.
Yu
>
> Regards
> Joey Lee
>
^ permalink raw reply [flat|nested] 10+ messages in thread
end of thread, other threads:[~2015-07-23 5:39 UTC | newest]
Thread overview: 10+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2015-06-30 15:54 [RFC PATCH] PM / hibernate: make sure each resuming page is in current memory zones Chen Yu
2015-07-02 6:19 ` joeyli
2015-07-02 8:00 ` chenyu5
2015-07-06 8:37 ` joeyli
2015-07-16 0:30 ` Rafael J. Wysocki
2015-07-21 1:28 ` chenyu5
2015-07-22 1:03 ` Rafael J. Wysocki
2015-07-22 8:58 ` Chen, Yu C
2015-07-23 5:34 ` joeyli
2015-07-23 5:42 ` chenyu5
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).