From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
rjw@sisk.pl
Subject: Re: [PATCH 1/2] PM: make VT switching to the suspend console optional
Date: Fri, 2 Nov 2012 23:43:02 +0000 [thread overview]
Message-ID: <20121102234302.28b773a7@pyramind.ukuu.org.uk> (raw)
In-Reply-To: <1351892621-4840-2-git-send-email-jbarnes@virtuousgeek.org>
On Fri, 2 Nov 2012 14:43:40 -0700
Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> KMS drivers can potentially restore the display configuration without
> userspace help. Such drivers can set a new global, pm_vt_switch, to
> false if they support this feature. In that case, the PM layer won't VT
> switch to the suspend console at suspend time and then back to the
> original VT on resume, but rather leave things alone for a nicer looking
> suspend and resume sequence.
What if you are multi-head ? What are the locking rules for a suspend/kms
module unload race, what happens when you load/unload and hand over
multiple frame buffers ? What if you have vts split across two adapters ?
Put me down as 100% in favour of the feature but we need to be a bit more
careful about the implementation. The logic probably needs to be in the
vt layer.
I suspect we actually need a per vt flag for this, or a flag on the
underlying object below the vt somewhere.
So NAK for the implementation ACK for the idea.
Alan
next prev parent reply other threads:[~2012-11-02 23:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 21:43 [RFC] Suspend/resume without VT switches Jesse Barnes
2012-11-02 21:43 ` [PATCH 1/2] PM: make VT switching to the suspend console optional Jesse Barnes
2012-11-02 23:43 ` Alan Cox [this message]
2012-11-03 0:20 ` Jesse Barnes
2012-11-03 0:42 ` Alan Cox
2012-11-03 0:40 ` Jesse Barnes
2012-11-02 21:43 ` [PATCH 2/2] drm/i915: support resume without VT switch Jesse Barnes
2012-11-02 21:51 ` [RFC] Suspend/resume without VT switches Rafael J. Wysocki
2012-11-02 23:29 ` Jesse Barnes
2012-11-02 23:38 ` Rafael J. Wysocki
2012-11-03 0:22 ` Jesse Barnes
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=20121102234302.28b773a7@pyramind.ukuu.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®