public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	kvm@vger.kernel.org, "Len Brown" <lenb@kernel.org>,
	linux-acpi@vger.kernel.org
Subject: Re: [PATCH RFC] ACPI: disable extra P_LVLx access on KVM
Date: Mon, 23 Apr 2018 10:07:10 +0200	[thread overview]
Message-ID: <1969294.enFTGV94N4@aspire.rjw.lan> (raw)
In-Reply-To: <1522431741-4678-1-git-send-email-mst@redhat.com>

On Friday, March 30, 2018 7:43:58 PM CEST Michael S. Tsirkin wrote:
> As documented by commit b488f021 "ACPI: restore comment justifying
> 'extra' P_LVLx access", Linux does an extra IO read after entering idle
> because on (some) chipsets STPCLK# doesn't get asserted in time
> to prevent further instruction processing.
> 
> This can never be the case on KVM, and a timer read causes an expensive
> VM exit in turn causing useless load on host system. Detect KVM and skip
> the read.  TODO: whitelist more hypervisors?
> 
> Note: very lightly tested.  Pls don't apply this yet, I am working on a
> _CST implementation for KVM and will repost this without the RFC tag
> when it's been tested properly.
> 
> Posting now for early flames/feedback.
> 
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: kvm@vger.kernel.org
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>  drivers/acpi/processor_idle.c | 7 +++++--
>  1 file changed, 5 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/acpi/processor_idle.c b/drivers/acpi/processor_idle.c
> index abb559c..8ae28dc 100644
> --- a/drivers/acpi/processor_idle.c
> +++ b/drivers/acpi/processor_idle.c
> @@ -33,6 +33,7 @@
>  #include <linux/cpuidle.h>
>  #include <linux/cpu.h>
>  #include <acpi/processor.h>
> +#include <linux/kvm_para.h>
>  
>  /*
>   * Include the apic definitions for x86 to have the APIC timer related defines
> @@ -665,7 +666,8 @@ static void __cpuidle acpi_idle_do_entry(struct acpi_processor_cx *cx)
>  		/* Dummy wait op - must do something useless after P_LVL2 read
>  		   because chipsets cannot guarantee that STPCLK# signal
>  		   gets asserted in time to freeze execution properly. */
> -		inl(acpi_gbl_FADT.xpm_timer_block.address);
> +		if (!kvm_para_available())
> +			inl(acpi_gbl_FADT.xpm_timer_block.address);
>  	}
>  }
>  
> @@ -687,7 +689,8 @@ static int acpi_idle_play_dead(struct cpuidle_device *dev, int index)
>  		else if (cx->entry_method == ACPI_CSTATE_SYSTEMIO) {
>  			inb(cx->address);
>  			/* See comment in acpi_idle_do_entry() */
> -			inl(acpi_gbl_FADT.xpm_timer_block.address);
> +			if (!kvm_para_available())
> +				inl(acpi_gbl_FADT.xpm_timer_block.address);
>  		} else
>  			return -ENODEV;
>  	}
> 

While I have no objections to this change from the ACPI side, I'd like someone
from the KVM land to comment on this.

Thanks,
Rafael

  reply	other threads:[~2018-04-23  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-30 17:43 [PATCH RFC] ACPI: disable extra P_LVLx access on KVM Michael S. Tsirkin
2018-04-23  8:07 ` Rafael J. Wysocki [this message]
2018-04-23  8:36   ` Paolo Bonzini

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=1969294.enFTGV94N4@aspire.rjw.lan \
    --to=rjw@rjwysocki.net \
    --cc=kvm@vger.kernel.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.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