Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.kernel > #67509 > unrolled thread

Bug#964845: Please enable CONFIG_SUSPEND in the cloud image kernel

Back to article view | Back to linux.debian.kernel

Contents

  Bug#964845: Please enable CONFIG_SUSPEND in the cloud image kernel Wanli Li <liwanli@google.com> - 2020-07-11 01:10 +0200
    Bug#964845: Any Update Wanli Li <liwanli@google.com> - 2020-10-28 20:40 +0100
      Bug#964845: Any Update Ben Hutchings <ben@decadent.org.uk> - 2020-10-28 22:30 +0100
        Bug#964845: Any Update Wanli Li <liwanli@google.com> - 2020-10-28 23:40 +0100
    Processed: Re: Bug#964845: Any Update "Debian Bug Tracking System" <owner@bugs.debian.org> - 2020-10-28 22:30 +0100
    Bug#964845: marked as done (Please enable CONFIG_SUSPEND in the  cloud image kernel) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2021-01-21 15:20 +0100

#67509 — Bug#964845: Please enable CONFIG_SUSPEND in the cloud image kernel

Package: linux-image-cloud-amd64
Version: 4.19+105+deb10u4
Severity: wishlist

Dear Maintainer,

Please consider enabling CONFIG_SUSPEND for the cloud variant kernel.
This makes it possible for the operating system to suspend to RAM.

- Wanli Li

-- System Information:
Debian Release: 10.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.19.0-9-cloud-amd64 (SMP w/1 CPU core)
Locale: LANG=C.UTF-8, LC_CTYPE=C.UTF-8 (charmap=UTF-8),
LANGUAGE=C.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-image-cloud-amd64 depends on:
ii  linux-image-4.19.0-9-cloud-amd64  4.19.118-2+deb10u1

linux-image-cloud-amd64 recommends no packages.

linux-image-cloud-amd64 suggests no packages.

[toc] | [next] | [standalone]

#68458 — Bug#964845: Any Update

[Multipart message — attachments visible in raw view] — view raw

Hi, just wanted to know whether there's any update on this feature request?

Wanli

[toc] | [prev] | [next] | [standalone]

#68459 — Bug#964845: Any Update

[Multipart message — attachments visible in raw view] — view raw

Control: tag -1 moreinfo

On Wed, 2020-10-28 at 12:29 -0700, Wanli Li wrote:
> Hi, just wanted to know whether there's any update on this feature request?

Why would this be needed in a cloud deployment?  Hypervisors should be
able to suspend and resume guests without specific support in the guest
kernel.

Ben.

-- 
Ben Hutchings
You can't have everything.  Where would you put it?

[toc] | [prev] | [next] | [standalone]

#68462 — Bug#964845: Any Update

[Multipart message — attachments visible in raw view] — view raw

Hi Ben,

It's true that the hypervisor can save the guest state and restore it later
without the help from the guest kernel.

However, to make the user space applications in the guest (like the network
daemons) aware of the suspend/resume, we want the entire suspend to RAM
process (begins with hypervisor asserting SLPBTN_STS [1] and ends with
guest kernel asserting SLP_TYP0 [2]) to run into completion so that guest
OS can be prepared for the issues caused by the suspend/resume (e.g. the
time jump). The write to SLP_TYP0 also serves as an acknowledgement from
the guest OS that the sleep request has been processed successfully by the
guest, the hypervisor can then start the saving of the guest state.

Daemons like acpid and systemd seem to also need "mem" to be included in
/sys/power/state in order to respond to SLPBTN_STS [1] and I think whether
"mem" is in /sys/power/state is controlled by the CONFIG_SUSPEND.

[1] ACPI 4.0 <https://uefi.org/sites/default/files/resources/ACPI_4.pdf>
4.7.3.1.1
[2] ACPI 4.0 <https://uefi.org/sites/default/files/resources/ACPI_4.pdf>
4.7.3.2.1


On Wed, Oct 28, 2020 at 2:24 PM Ben Hutchings <ben@decadent.org.uk> wrote:

> Control: tag -1 moreinfo
>
> On Wed, 2020-10-28 at 12:29 -0700, Wanli Li wrote:
> > Hi, just wanted to know whether there's any update on this feature
> request?
>
> Why would this be needed in a cloud deployment?  Hypervisors should be
> able to suspend and resume guests without specific support in the guest
> kernel.
>
> Ben.
>
> --
> Ben Hutchings
> You can't have everything.  Where would you put it?
>
>
>

[toc] | [prev] | [next] | [standalone]

#68460 — Processed: Re: Bug#964845: Any Update

Processing control commands:

> tag -1 moreinfo
Bug #964845 [src:linux] Please enable CONFIG_SUSPEND in the cloud image kernel
Added tag(s) moreinfo.

-- 
964845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964845
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [next] | [standalone]

#69240 — Bug#964845: marked as done (Please enable CONFIG_SUSPEND in the cloud image kernel)

[Multipart message — attachments visible in raw view] — view raw

Your message dated Thu, 21 Jan 2021 14:10:10 +0000
with message-id <E1l2af4-000F6C-03@fasolo.debian.org>
and subject line Bug#964845: fixed in linux 5.10.9-1
has caused the Debian Bug report #964845,
regarding Please enable CONFIG_SUSPEND in the cloud image kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
964845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964845
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.kernel

csiph-web