Re: Applications & ACPI events

Patrick Mochel
2003-10-14T23:04:31Z

> > It's also unncessary for X to do a full save/restore of the video card on
> > every VT switch. I personally find it annoying to wait a second or two
> > when switching from X to the console.
>
> ??
>
> What if game or another X server is running on different console.

Is it really the current X server's responsibility to provide for what
ever may be running on what ever console the user switches to? That seems
backwards - the application that is being switched to should save the
state of that which it's switching from. This is an X question, though,
and not fodder for this list..

> Patch looks reasonable, but:
>
> STATE= should really be more finegrained. ACPI s3 is really differnent
> from apm -s, and it looks to me like you'll only tell userspace 'mem'.

Well, it depends on what X (and in general userspace) needs to know on a
power-state transition. Alan, how does/will X behave differently for each
power state that we can enter?

I really don't want to lose the abstraction, since it currently is
platform-neutral, and doesn't include any x86isms.

> Hmm, apm.. they already have some mechanism to do just this. These two
> should be coordinated. [And this one certainly looks nicer than apm
> way.]

I agree. If we can agree on an interface, it should be usable for any
platform's power management notification.

> Kernel waiting for userspace to finish with pm_sem held... If that
> code tries to do "echo platform > disk" in the meantime, you get ugly
> deadlock.

Then, that would be a bug, and would be fixed in early stages of testing.
:)

Pat