linux-kernel - Re: [char-misc 01/02 v2] mei: always use domain runtime pm callbacks.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0gb5ucyxUhHKzzqQwQbsUOyT1oRwpDcUxeieXRCPmmK-w@mail.gmail.com>
Date:   Tue, 26 Sep 2017 17:17:59 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Tomas Winkler <tomas.winkler@...el.com>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        Alexander Usyskin <alexander.usyskin@...el.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        "#4 . 13+" <stable@...r.kernel.org>,
        "Rafael J . Wysocki" <rafael@...nel.org>
Subject: Re: [char-misc 01/02 v2] mei: always use domain runtime pm callbacks.

On Tue, Sep 26, 2017 at 8:18 AM, Tomas Winkler <tomas.winkler@...el.com> wrote:
> From: Alexander Usyskin <alexander.usyskin@...el.com>
>
> This patch fixes a regression caused by the new changes
> in the "run wake" handlers.
>
> The mei devices that support D0i3 are no longer receiving an interrupt
> after entering runtime suspend state and will stall.
>
> pci_dev_run_wake function now returns "true" for some devices
> (including mei) for which it used to return "false",
> arguably incorrectly as "run wake" used to mean that
> wakeup signals can be generated for a device in
> the working state of the system, so it could not be enabled
> or disabled before too.
>
> MEI maps runtime suspend/resume to its own defined
> power gating (PG) states, (D0i3 or other depending on generation),
> hence we need to go around the native PCI runtime service which
> eventually brings the device into D3cold/hot state,
> but the mei devices cannot wake up from D3 unlike from D0i3/PG state,
> which keeps irq running.
> To get around PCI device native runtime pm,
> MEI uses runtime pm domain handlers which take precedence.
>
> Cc: <stable@...r.kernel.org> #4.13+
> Cc: Rafael J. Wysocki <rafael@...nel.org>
> Signed-off-by: Alexander Usyskin <alexander.usyskin@...el.com>
> Signed-off-by: Tomas Winkler <tomas.winkler@...el.com>

Acked-by: Rafael J. Wysocki <rafael.j.wysocki@...el.com>