mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@digeo.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Suspend2 Merge: e820 table support.
Date: Thu, 16 Sep 2004 21:35:46 +1000	[thread overview]
Message-ID: <1095334545.4932.206.camel@laptop.cunninghams> (raw)
In-Reply-To: <20040916112711.GD5467@elf.ucw.cz>

Hi.

On Thu, 2004-09-16 at 21:27, Pavel Machek wrote:
> Hmm, it also contains (saveable()):
> 
>         BUG_ON(PageReserved(page) && PageNosave(page));

How do you cover those HighMem pages that get marked Reserved and are
unusable? (That's what the e820 logic was for, iirc. Think it was done
about February!). Not handling them resulted in MCEs when trying to do
the atomic copy or when restoring (seemed random).

> ..but that should be easy to kill. I'd be worried about this function:
> 
> static void free_suspend_pagedir_zone(struct zone *zone, unsigned long
> pagedir)
> {
>         unsigned long zone_pfn, pagedir_end, pagedir_pfn,
> pagedir_end_pfn;
>         pagedir_end = pagedir + (PAGE_SIZE << pagedir_order);
>         pagedir_pfn = __pa(pagedir) >> PAGE_SHIFT;
>         pagedir_end_pfn = __pa(pagedir_end) >> PAGE_SHIFT;
>         for (zone_pfn = 0; zone_pfn < zone->spanned_pages; ++zone_pfn)
> {
>                 struct page *page;
>                 unsigned long pfn = zone_pfn + zone->zone_start_pfn;
>                 if (!pfn_valid(pfn))
>                         continue;
>                 page = pfn_to_page(pfn);

Mmm. I should get around to using pfn_to_page. That's necessary for
discontig support, right? Haven't looked at that yet. (Yes, swsusp has
functionality suspend2 doesn't!) :>.

>                 if (!TestClearPageNosave(page))
>                         continue;
>                 else if (pfn >= pagedir_pfn && pfn < pagedir_end_pfn)
>                         continue;
>                 __free_page(page);
>         }
> }

Wow. This function is really hard to understand. Or maybe I'm really
ignorant :>. 

> I posted diff to get rid of it, but it did not get enough testing so
> it is not in mainline.
> 								Pavel

Regards,

Nigel
-- 
Nigel Cunningham
Pastoral Worker
Christian Reformed Church of Tuggeranong
PO Box 1004, Tuggeranong, ACT 2901

Many today claim to be tolerant. True tolerance, however, can cope with others
being intolerant.


  reply	other threads:[~2004-09-16 11:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-16 11:03 Nigel Cunningham
2004-09-16 11:14 ` Pavel Machek
2004-09-16 11:24   ` Nigel Cunningham
2004-09-16 11:27     ` Pavel Machek
2004-09-16 11:35       ` Nigel Cunningham [this message]
2004-09-16 11:37         ` Pavel Machek
2004-09-16 11:59           ` 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=1095334545.4932.206.camel@laptop.cunninghams \
    --to=ncunningham@linuxmail.org \
    --cc=akpm@digeo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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®