From: Grzegorz Jaszczyk <jaz@semihalf.com>
To: linux-kernel@vger.kernel.org, rafael@kernel.org
Cc: dmy@semihalf.com, tn@semihalf.com, dbehr@google.com,
zide.chen@intel.corp-partner.google.com, seanjc@google.com,
upstream@semihalf.com, hdegoede@redhat.com, markgross@kernel.org,
dtor@google.com, Grzegorz Jaszczyk <jaz@semihalf.com>
Subject: [RFCv2 0/1] x86: allow to notify host about guest entering s2idle
Date: Thu, 9 Feb 2023 13:56:45 +0000 [thread overview]
Message-ID: <20230209135646.3179418-1-jaz@semihalf.com> (raw)
According to the mailing list discussion [1] about the preferred approach
for notifying hypervisor/VMM about guest entering s2idle state this RFC was
implemented.
Instead of original hypercall based approach, which involves KVM change [2]
and makes it hypervisor specific, implement different mechanism, which
takes advantage of MMIO/PIO trapping and makes it hypervisor independent.
For the RFCv1 [3]:
Patch #1 extends S2Idle ops by new notify handler which will be invoked as a
very last command before system actually enters S2Idle states. It also allows
to register and use driver specific notification hook which is used in
patch #2.
Patch #2 introduces new driver for virtual PMC, which registers
acpi_s2idle_dev_ops's notify handler. Its implementation is based on an
ACPI _DSM evaluation, which in turn can perform MMIO access and allow to
trap and therefore notify the VMM about guest entering S2Idle state.
For the RFCv2: the patch #1 was dropped as in the meantime Mario Limonciello
introduced a very similar patch [4] which uses s/notify/check and invokes the
callback a bit earlier just before s2idle_entry. Mentioned patch has already
been merged.
This patchset is marked as RFC since patch #2 implements driver for non
existing device "HYPE0001", which ACPI ID was not registered yet.
Furthermore the required registration process [5] will not be started
before getting positive feedback about this patchset.
[1] https://patchwork.kernel.org/project/linux-pm/patch/20220609110337.1238762-2-jaz@semihalf.com/
[2] https://patchwork.kernel.org/project/linux-pm/patch/20220609110337.1238762-3-jaz@semihalf.com/
[3] https://patchwork.kernel.org/project/linux-pm/cover/20220707125329.378277-1-jaz@semihalf.com/
[4] https://patchwork.kernel.org/project/linux-pm/patch/20220829162953.5947-2-mario.limonciello@amd.com
[5] https://uefi.org/PNP_ACPI_Registry
Grzegorz Jaszczyk (1):
platform/x86: Add virtual PMC driver used for S2Idle
drivers/platform/x86/Kconfig | 7 ++++
drivers/platform/x86/Makefile | 3 ++
drivers/platform/x86/virt_pmc.c | 73 +++++++++++++++++++++++++++++++++
3 files changed, 83 insertions(+)
create mode 100644 drivers/platform/x86/virt_pmc.c
--
2.39.1.519.gcb327c4b5f-goog
next reply other threads:[~2023-02-09 13:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 13:56 Grzegorz Jaszczyk [this message]
2023-02-09 13:56 ` [RFCv2 1/1] platform/x86: Add virtual PMC driver used for S2Idle Grzegorz Jaszczyk
2023-02-09 14:35 ` [RFCv2 0/1] x86: allow to notify host about guest entering s2idle Hans de Goede
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=20230209135646.3179418-1-jaz@semihalf.com \
--to=jaz@semihalf.com \
--cc=dbehr@google.com \
--cc=dmy@semihalf.com \
--cc=dtor@google.com \
--cc=hdegoede@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markgross@kernel.org \
--cc=rafael@kernel.org \
--cc=seanjc@google.com \
--cc=tn@semihalf.com \
--cc=upstream@semihalf.com \
--cc=zide.chen@intel.corp-partner.google.com \
/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®