From: Sean Christopherson <seanjc@google.com>
To: Grzegorz Jaszczyk <jaz@semihalf.com>
Cc: linux-kernel@vger.kernel.org, Dmytro Maluka <dmy@semihalf.com>,
Zide Chen <zide.chen@intel.corp-partner.google.com>,
Peter Fang <peter.fang@intel.corp-partner.google.com>,
Tomasz Nowicki <tn@semihalf.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Jonathan Corbet <corbet@lwn.net>,
Vitaly Kuznetsov <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
Jim Mattson <jmattson@google.com>, Joerg Roedel <joro@8bytes.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
"maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)"
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Len Brown <lenb@kernel.org>, Pavel Machek <pavel@ucw.cz>,
Ashish Kalra <ashish.kalra@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Hans de Goede <hdegoede@redhat.com>,
Sachi King <nakato@nakato.io>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
David Dunn <daviddunn@google.com>,
Wei Wang <wei.w.wang@intel.com>,
Nicholas Piggin <npiggin@gmail.com>,
"open list:KERNEL VIRTUAL MACHINE (KVM)" <kvm@vger.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
"open list:ACPI" <linux-acpi@vger.kernel.org>,
"open list:HIBERNATION (aka Software Suspend,
aka swsusp)" <linux-pm@vger.kernel.org>,
Dominik Behr <dbehr@google.com>,
Dmitry Torokhov <dtor@google.com>
Subject: Re: [PATCH 1/2] x86: notify hypervisor about guest entering s2idle state
Date: Thu, 16 Jun 2022 16:48:15 +0000 [thread overview]
Message-ID: <Yqtez/J540yD7VdD@google.com> (raw)
In-Reply-To: <CAH76GKNSfaHwpy46r1WWTVgnsuijqcHe=H5nvUTUUs1UbdZvkQ@mail.gmail.com>
On Wed, Jun 15, 2022, Grzegorz Jaszczyk wrote:
> pt., 10 cze 2022 o 16:30 Sean Christopherson <seanjc@google.com> napisał(a):
> > MMIO or PIO for the actual exit, there's nothing special about hypercalls. As for
> > enumerating to the guest that it should do something, why not add a new ACPI_LPS0_*
> > function? E.g. something like
> >
> > static void s2idle_hypervisor_notify(void)
> > {
> > if (lps0_dsm_func_mask > 0)
> > acpi_sleep_run_lps0_dsm(ACPI_LPS0_EXIT_HYPERVISOR_NOTIFY
> > lps0_dsm_func_mask, lps0_dsm_guid);
> > }
>
> Great, thank you for your suggestion! I will try this approach and
> come back. Since this will be the main change in the next version,
> will it be ok for you to add Suggested-by: Sean Christopherson
> <seanjc@google.com> tag?
If you want, but there's certainly no need to do so. But I assume you or someone
at Intel will need to get formal approval for adding another ACPI LPS0 function?
I.e. isn't there work to be done outside of the kernel before any patches can be
merged?
next prev parent reply other threads:[~2022-06-16 16:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 11:03 [PATCH 0/2] x86: notify hypervisor/VMM about guest entering s2idle Grzegorz Jaszczyk
2022-06-09 11:03 ` [PATCH 1/2] x86: notify hypervisor about guest entering s2idle state Grzegorz Jaszczyk
2022-06-09 14:27 ` Dave Hansen
2022-06-10 11:36 ` Grzegorz Jaszczyk
2022-06-10 12:49 ` Dave Hansen
2022-06-13 5:03 ` Mario Limonciello
2022-06-15 18:00 ` Grzegorz Jaszczyk
2022-06-09 14:55 ` Sean Christopherson
2022-06-10 12:26 ` Grzegorz Jaszczyk
2022-06-10 14:29 ` Sean Christopherson
2022-06-15 18:53 ` Grzegorz Jaszczyk
2022-06-16 16:48 ` Sean Christopherson [this message]
2022-06-16 16:58 ` Limonciello, Mario
2022-06-20 15:43 ` Grzegorz Jaszczyk
2022-06-20 16:32 ` Limonciello, Mario
2022-06-22 9:53 ` Grzegorz Jaszczyk
2022-06-22 21:50 ` Limonciello, Mario
2022-06-23 16:47 ` Sean Christopherson
2022-06-23 16:50 ` Grzegorz Jaszczyk
2022-06-23 17:19 ` Limonciello, Mario
2022-06-09 11:03 ` [PATCH 2/2] KVM: x86: notify user space about guest entering s2idle Grzegorz Jaszczyk
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=Yqtez/J540yD7VdD@google.com \
--to=seanjc@google.com \
--cc=acme@redhat.com \
--cc=ashish.kalra@amd.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=dave.hansen@linux.intel.com \
--cc=daviddunn@google.com \
--cc=dbehr@google.com \
--cc=dmy@semihalf.com \
--cc=dtor@google.com \
--cc=hdegoede@redhat.com \
--cc=hpa@zytor.com \
--cc=jaz@semihalf.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=mingo@redhat.com \
--cc=nakato@nakato.io \
--cc=npiggin@gmail.com \
--cc=pavel@ucw.cz \
--cc=pbonzini@redhat.com \
--cc=peter.fang@intel.corp-partner.google.com \
--cc=rafael@kernel.org \
--cc=tglx@linutronix.de \
--cc=tn@semihalf.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=wei.w.wang@intel.com \
--cc=x86@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).