linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: hugang@soulinfo.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: software suspend patch [1/6]
Date: Sun, 28 Nov 2004 18:11:06 +0100	[thread overview]
Message-ID: <20041128171106.GD1214@elf.ucw.cz> (raw)
In-Reply-To: <20041128162558.GF28881@hugang.soulinfo.com>

Hi!

> >  device-tree.diff 
> >    base from suspend2 with a little changed.
> > 
> >  core.diff
> >   1: redefine struct pbe for using _no_ continuous as pagedir.
> >   2: make shrink memory as little as possible.
> >   3: using a bitmap speed up collide check in page relocating.
> >   4: pagecache saving ready.
> > 
> >  i386.diff
> >  ppc.diff
> >   i386 and powerpc suspend update.
> > 
> >  pagecachs_addon.diff
> >   if enable page caches saving, must using it, it making saving
> >   pagecaches safe. idea from suspend2.
> > 
> >   ppcfix.diff
> >   fix compile error. 
> >   $ gcc -v
> >    .... 
> >    gcc version 2.95.4 20011002 (Debian prerelease)
> > 
> > I'm using 2.6.9-ck3 With above patch, swsusp1 works prefect in my 
> > PowerPC and x86 PC with Highmem and prepempt option enabled.
> > 
> > I hope the core.diff@1,@2,@3 i386.diff ppc.diff will merge into 
> > mainline kernel ASAP, :). from I view point device-tree.diff is 
> > very usefuly when using pagecache saving and pagecachs_addon.diff
> > that's really hack for making pagecache saving safe.
> > 
> 
> --- 2.6.9-lzf/arch/ppc/syslib/open_pic.c	2004-11-26 12:32:58.000000000 +0800
> +++ 2.6.9/arch/ppc/syslib/open_pic.c	2004-11-28 23:16:58.000000000 +0800
> @@ -776,7 +776,8 @@ static void openpic_mapirq(u_int irq, cp
>  	if (ISR[irq] == 0)
>  		return;
>  	if (!cpus_empty(keepmask)) {
> -		cpumask_t irqdest = { .bits[0] = openpic_read(&ISR[irq]->Destination) };
> +		cpumask_t irqdest;
> +		irqdest.bits[0] = openpic_read(&ISR[irq]->Destination);
>  		cpus_and(irqdest, irqdest, keepmask);
>  		cpus_or(physmask, physmask, irqdest);
>  	}

ACK. Send this to Andrew Morton, Cc: Rusty trivial patch monkey
Russell <trivial@rustcorp.com.au>.
								Pavel

-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!

  reply	other threads:[~2004-11-28 17:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-27 22:07 Suspend 2 merge linux
2004-11-27 22:25 ` Pavel Machek
2004-11-28  8:29 ` Wichert Akkerman
2004-11-28 11:37   ` Pavel Machek
2004-11-28 16:23     ` software suspend patch [1/6] hugang
2004-11-28 16:24       ` software suspend patch [2/6] hugang
2004-11-28 17:03         ` Pavel Machek
2004-11-28 16:24       ` software suspend patch [3/6] hugang
2004-11-28 16:25       ` software suspend patch [4/6] hugang
2004-11-28 17:08         ` Pavel Machek
2004-11-28 16:25       ` software suspend patch [5/6] hugang
2004-11-28 16:25       ` software suspend patch [1/6] hugang
2004-11-28 17:11         ` Pavel Machek [this message]
2004-12-02 20:56           ` Guido Guenther
2004-11-28 16:58       ` Pavel Machek
2004-11-29 15:43         ` hugang
2005-01-09 22:43           ` Pavel Machek
2005-01-11  2:01             ` hugang
2005-01-11  3:15               ` Pavel Machek

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=20041128171106.GD1214@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=hugang@soulinfo.com \
    --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;
as well as URLs for NNTP newsgroup(s).