public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: kernel list <linux-kernel@vger.kernel.org>,
	seife@suse.de,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: Re: smp/swsusp done right
Date: Wed, 30 Mar 2005 13:32:54 +0200	[thread overview]
Message-ID: <20050330113254.GE572@elf.ucw.cz> (raw)
In-Reply-To: <200503301242.38280.rjw@sisk.pl>

Hi!

> > This is against -mm kernel; it is smp swsusp done right, and it
> > actually works for me. Unlike previous hacks, it uses cpu hotplug
> > infrastructure. Disable CONFIG_MTRR before you try this...
> > 
> > Test this if you can, and report any problems. If not enough people
> > scream, this is going to -mm.
> > 								Pavel
> > 
> > --- clean-mm/drivers/pci/pci.c	2005-03-21 11:39:32.000000000 +0100
> > +++ linux-mm/drivers/pci/pci.c	2005-03-22 01:41:48.000000000 +0100
> > @@ -376,11 +376,13 @@
> >  	if (!pci_find_capability(dev, PCI_CAP_ID_PM))
> >  		return PCI_D0;
> >  
> > +#if 0
> >  	if (platform_pci_choose_state) {
> >  		ret = platform_pci_choose_state(dev, state);
> >  		if (ret >= 0)
> >  			state = ret;
> >  	}
> > +#endif
> >  	switch (state) {
> >  	case 0: return PCI_D0;
> >  	case 3: return PCI_D3hot;
> 
> You probably don't want the above change to go in the final patch?

No, not in final patch.

> > -	atomic_set(&cpu_counter, 0);
> > -	atomic_set(&freeze, 1);
> > -	smp_call_function(smp_pause, NULL, 0, 0);
> > -	while (atomic_read(&cpu_counter) < (num_online_cpus() - 1)) {
> > -		cpu_relax();
> > -		barrier();
> > +	error = 0;
> > +	cpus_clear(frozen_cpus);
> > +	printk("Freezing cpus ...\n");
> > +	for_each_online_cpu(cpu) {
> > +		if (cpu == 0)
> > +			continue;
> > +		error = cpu_down(cpu);
> > +		if (!error) {
> > +			cpu_set(cpu, frozen_cpus);
> > +			printk("CPU%d is down\n", cpu);
> > +			continue;
> > +		}
> > +		printk("Error taking cpu %d down: %d\n", cpu, error);
> >  	}
> > -	printk("ok\n");
> > +	BUG_ON(smp_processor_id() != 0);
> > +	if (error)
> > +		panic("cpus not sleeping");
> >  }
> 
> I'm not sure whether we should panic() here.  It may be better to make
> suspend fail and print a "please reboot immediately" message for the user.
> In that case, the user may be able to reboot without loosing data
> -	...

I guess I could just fail the suspend, but I want to see the messages
for now. (And I do not think it will ever trigger).
								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:[~2005-03-30 11:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 20:40 smp/swsusp done right Pavel Machek
2005-03-30 10:42 ` Rafael J. Wysocki
2005-03-30 11:32   ` Pavel Machek [this message]
2005-03-30 21:13 ` Zwane Mwaikambo
     [not found]   ` <Pine.LNX.4.61.0503301413050.12965-SOP5cCwKKQRMCHjbocvOOJqQE7yCjDx5@public.gmane.org>
2005-03-30 21:22     ` Pavel Machek
2005-03-30 21:44       ` Zwane Mwaikambo

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=20050330113254.GE572@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --cc=seife@suse.de \
    /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