mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
	kvm@vger.kernel.org, Nicolas Saenz Julienne <nsaenz@amazon.com>
Cc: vkuznets@redhat.com, pbonzini@redhat.com, tglx@linutronix.de,
	mingo@redhat.com, bp@alien8.de, dave.hansen@linux.intel.com,
	x86@kernel.org, hpa@zytor.com, graf@amazon.de, rkagan@amazon.de,
	linux-kernel@vger.kernel.org, anelkz@amazon.de,
	stable@vger.kernel.org
Subject: Re: [PATCH v3] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
Date: Tue, 17 Oct 2023 18:16:20 -0700	[thread overview]
Message-ID: <169759163972.1787364.3932584247097617727.b4-ty@google.com> (raw)
In-Reply-To: <20231017155101.40677-1-nsaenz@amazon.com>

On Tue, 17 Oct 2023 15:51:02 +0000, Nicolas Saenz Julienne wrote:
> Don't apply the stimer's counter side effects when modifying its
> value from user-space, as this may trigger spurious interrupts.
> 
> For example:
>  - The stimer is configured in auto-enable mode.
>  - The stimer's count is set and the timer enabled.
>  - The stimer expires, an interrupt is injected.
>  - The VM is live migrated.
>  - The stimer config and count are deserialized, auto-enable is ON, the
>    stimer is re-enabled.
>  - The stimer expires right away, and injects an unwarranted interrupt.
> 
> [...]

Applied to kvm-x86 misc, thanks!

[1/1] KVM: x86: hyper-v: Don't auto-enable stimer on write from user-space
      https://github.com/kvm-x86/linux/commit/d6800af51c76

--
https://github.com/kvm-x86/linux/tree/next

      parent reply	other threads:[~2023-10-18  1:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-17 15:51 Nicolas Saenz Julienne
2023-10-17 16:02 ` Vitaly Kuznetsov
2023-10-18  1:16 ` Sean Christopherson [this message]

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=169759163972.1787364.3932584247097617727.b4-ty@google.com \
    --to=seanjc@google.com \
    --cc=anelkz@amazon.de \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=graf@amazon.de \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=nsaenz@amazon.com \
    --cc=pbonzini@redhat.com \
    --cc=rkagan@amazon.de \
    --cc=stable@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --cc=vkuznets@redhat.com \
    --cc=x86@kernel.org \
    /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®