All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: "Radim Krčmář" <rkrcmar@redhat.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Cc: Yuki Shibuya <shibuya.yk@ncos.nec.co.jp>,
	Paolo Bonzini <pbonzini@redhat.com>,
	stable <stable@vger.kernel.org>
Subject: Re: [PATCH 4.5 007/238] KVM: i8254: change PIT discard tick policy
Date: Tue, 12 Apr 2016 00:23:35 +0100	[thread overview]
Message-ID: <1460417015.25201.67.camel@decadent.org.uk> (raw)

[-- Attachment #1: Type: text/plain, Size: 1268 bytes --]

On Wed, 2016-03-02 at 22:56 +0100, Radim Krčmář wrote:
> From: Radim Krčmář <rkrcmar@redhat.com>
> 
> commit 7dd0fdff145c5be7146d0ac06732ae3613412ac1 upstream.
> 
> Discard policy uses ack_notifiers to prevent injection of PIT interrupts
> before EOI from the last one.
> 
> This patch changes the policy to always try to deliver the interrupt,
> which makes a difference when its vector is in ISR.
> Old implementation would drop the interrupt, but proposed one injects to
> IRR, like real hardware would.
> 
> The old policy breaks legacy NMI watchdogs, where PIT is used through
> virtual wire (LVT0): PIT never sends an interrupt before receiving EOI,
> thus a guest deadlock with disabled interrupts will stop NMIs.
> 
> Note that NMI doesn't do EOI, so PIT also had to send a normal interrupt
> through IOAPIC.  (KVM's PIT is deeply rotten and luckily not used much
> in modern systems.)
> 
> Even though there is a chance of regressions, I think we can fix the
> LVT0 NMI bug without introducing a new tick policy.
[...]

Given the 'chance of regressions', should we let this sit in mainline
longer before including it in stable updates?

Ben.

-- 
Ben Hutchings
This sentence contradicts itself - no actually it doesn't.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2016-04-11 23:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 23:23 Ben Hutchings [this message]
2016-04-12  1:21 ` [PATCH 4.5 007/238] KVM: i8254: change PIT discard tick policy Greg Kroah-Hartman
2016-04-12 13:30   ` Radim Krčmář
2016-04-12 14:13     ` Greg Kroah-Hartman
2016-04-12 21:19       ` 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=1460417015.25201.67.camel@decadent.org.uk \
    --to=ben@decadent.org.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=shibuya.yk@ncos.nec.co.jp \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.