public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: Pavel Machek <pavel@suse.cz>,
	Linux-pm mailing list <linux-pm@lists.osdl.org>,
	Vojtech Pavlik <vojtech@suse.cz>, Stefan Seyfried <seife@suse.de>,
	kernel list <linux-kernel@vger.kernel.org>,
	Andy Isaacson <adi@hexapodia.org>
Subject: Re: [linux-pm] Re: swsusp 'disk' fails in bk-current - intel_agp at fault?
Date: Tue, 29 Mar 2005 16:38:35 -0500	[thread overview]
Message-ID: <d120d500050329133838b0ebb6@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.50.0503291321490.29474-100000@monsoon.he.net>

On Tue, 29 Mar 2005 13:23:35 -0800 (PST), Patrick Mochel
<mochel@digitalimplant.org> wrote:
> 
> On Tue, 29 Mar 2005, Pavel Machek wrote:
> 
> > I don't really want us to try execve during resume... Could we simply
> > artifically fail that execve with something if (in_suspend()) return
> > -EINVAL; [except that in_suspend() just is not there, but there were
> > some proposals to add it].
> >
> > Or just avoid calling hotplug at all in resume case? And then do
> > coldplug-like scan when userspace is ready...
> 
> I thought that cold-plugging only worked for devices, not all objects.
> 

It really depens on the script - nothing stops it from traversing
entire /sys tree and if an object it not exported in the tree I'd say
userspace should not care about such object anyway.

> Can we just queue up hotplug events? That way we wouldn't lose any across
> the transition, and could be used to send resume events to userspace for
> various devices that need help..
>

The point is that at this point any changes to the system state will
be discarded - we already did the image and about to write it. When we
resume for real all those events will be regenerated once again.
 
-- 
Dmitry

  reply	other threads:[~2005-03-29 21:41 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-23 18:49 swsusp 'disk' fails in bk-current - intel_agp at fault? Andy Isaacson
2005-03-24 14:27 ` Stefan Seyfried
2005-03-24 18:10   ` Andy Isaacson
2005-03-24 19:18     ` Dmitry Torokhov
2005-03-24 20:20       ` Andy Isaacson
2005-03-24 21:10         ` Dmitry Torokhov
2005-03-24 23:54           ` Andy Isaacson
2005-03-25  9:22             ` Stefan Seyfried
2005-03-25 10:13               ` Pavel Machek
2005-03-25 14:19                 ` Dmitry Torokhov
2005-03-25 14:24                   ` Pavel Machek
2005-03-25 14:52                     ` Dmitry Torokhov
2005-03-25 15:42                       ` Pavel Machek
2005-03-25 16:04                         ` Dmitry Torokhov
2005-03-28 23:00                           ` Pavel Machek
2005-03-29 23:19                           ` Rafael J. Wysocki
2005-03-29 21:49                       ` Rafael J. Wysocki
2005-03-25 18:36                 ` Andy Isaacson
2005-03-29 16:18               ` Dmitry Torokhov
2005-03-29 18:18                 ` Pavel Machek
2005-03-29 19:11                   ` Dmitry Torokhov
2005-03-29 19:23                     ` Pavel Machek
2005-03-29 20:05                       ` Dmitry Torokhov
2005-03-29 20:52                         ` Pavel Machek
2005-03-29 21:07                           ` Dmitry Torokhov
2005-03-29 21:12                             ` Pavel Machek
2005-03-29 21:33                               ` Dmitry Torokhov
2005-03-29 21:44                                 ` Pavel Machek
2005-03-29 22:31                                   ` [linux-pm] " Nigel Cunningham
2005-03-29 22:35                                     ` Pavel Machek
2005-03-29 23:46                                       ` Nigel Cunningham
2005-03-31  7:26                                       ` Dmitry Torokhov
2005-03-31  8:39                                         ` Pavel Machek
2005-03-31 15:02                                           ` Dmitry Torokhov
2005-03-31 16:02                                         ` Patrick Mochel
2005-03-31 16:32                                           ` Dmitry Torokhov
2005-03-31 22:16                                             ` Nigel Cunningham
2005-03-31 22:18                                             ` Pavel Machek
2005-03-31 22:28                                               ` Nigel Cunningham
2005-04-01  8:49                                                 ` Rafael J. Wysocki
2005-04-01 10:33                                                   ` Stefan Seyfried
2005-03-29 23:05                               ` Rafael J. Wysocki
2005-03-29 21:23                           ` [linux-pm] " Patrick Mochel
2005-03-29 21:38                             ` Dmitry Torokhov [this message]
2005-03-30  9:52                             ` Greg KH
2005-03-25 14:58             ` Dmitry Torokhov
2005-03-30  7:26               ` Andy Isaacson
2005-03-24 21:14         ` Dmitry Torokhov
2005-03-24 20:38     ` Stefan Seyfried
2005-03-29 18:42       ` Dmitry Torokhov
2005-03-30  7:24         ` Andy Isaacson
     [not found] ` <20050525171825.51a06908.akpm@osdl.org>
2005-05-27 17:44   ` Andy Isaacson

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=d120d500050329133838b0ebb6@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=adi@hexapodia.org \
    --cc=dtor_core@ameritech.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    --cc=mochel@digitalimplant.org \
    --cc=pavel@suse.cz \
    --cc=seife@suse.de \
    --cc=vojtech@suse.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