public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>,
	linux-acpi@vger.kernel.org, linux-pm@lists.osdl.org,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.19: ACPI reports AC not present after resume from STD
Date: Mon, 26 Feb 2007 23:35:41 +0300	[thread overview]
Message-ID: <200702262335.47874.arvidjaar@mail.ru> (raw)
In-Reply-To: <200702251958.37315.rjw@sisk.pl>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Воскресенье 25 февраля 2007, Rafael J. Wysocki wrote:
>
> The patch looks good, but the changelog does not.  First, AFAICT, the
> x86_64 code doesn't touch anything outside the e820 map.  Why do you think
> it does?
>

the following code:

       paddr = round_down(e820.map[0].addr + e820.map[0].size, PAGE_SIZE);
        for (i = 1; i < e820.nr_map; i++) {
                struct e820entry *ei = &e820.map[i];

                if (paddr < ei->addr)
                        e820_mark_nosave_range(paddr,
                                        round_up(ei->addr, PAGE_SIZE));

obviously will mark region *between* two e820 regions if they are not 
adjacent. I do not say that it is wrong (I have no idea); but exactly because 
I have no idea I tried to avoid it.

> Second, it is not true that the region in question is at 0xee00 on x86_64.
> At least on my box it's above the end of RAM.
>

On my box the problem region starts at ee800 :) But you are right, it does not 
belong here.

> I think the x86_64 version is correct too.
>

I do not say it is not. I just say that it does something I cannot verify so I 
better avoid it (i.e. I better change existing behaviour as little as 
possible).

- -andrey
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFF40SjR6LMutpd94wRAlLvAKCMkVxMkKNwpGX/J3on0jQS659+zgCgmofK
vuG4p3gR4yBjfoHuMAR0cDU=
=JG9z
-----END PGP SIGNATURE-----
_______________________________________________
linux-pm mailing list
linux-pm@lists.osdl.org
https://lists.osdl.org/mailman/listinfo/linux-pm

  reply	other threads:[~2007-02-26 20:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8E389A5F2FEABA4CB1DEC35A25CB39CE82FE9F@mssmsx411>
     [not found] ` <200702132116.05404.arvidjaar@mail.ru>
2007-02-24  9:55   ` 2.6.19: ACPI reports AC not present after resume from STD Andrey Borzenkov
2007-02-24 19:46     ` Rafael J. Wysocki
2007-02-24 23:26       ` Andrey Borzenkov
2007-02-25 10:17         ` Rafael J. Wysocki
2007-02-25 10:37           ` Andrey Borzenkov
2007-02-25 10:51             ` Rafael J. Wysocki
2007-02-25 17:14               ` Andrey Borzenkov
2007-02-25 18:58                 ` Rafael J. Wysocki
2007-02-26 20:35                   ` Andrey Borzenkov [this message]
2007-02-26 21:23                     ` Rafael J. Wysocki

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=200702262335.47874.arvidjaar@mail.ru \
    --to=arvidjaar@mail.ru \
    --cc=akpm@osdl.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=rjw@sisk.pl \
    /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