All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Ben Hutchings <ben@decadent.org.uk>,
	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 07:13:13 -0700	[thread overview]
Message-ID: <20160412141313.GA7996@kroah.com> (raw)
In-Reply-To: <20160412133023.GA3696@potion.brq.redhat.com>

On Tue, Apr 12, 2016 at 03:30:23PM +0200, Radim Krčmář wrote:
> 2016-04-11 18:21-0700, Greg Kroah-Hartman:
> > On Tue, Apr 12, 2016 at 12:23:35AM +0100, Ben Hutchings wrote:
> > > On Wed, 2016-03-02 at 22:56 +0100, Radim Krčmář wrote:
> >> > 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?
> > 
> > Hm, good point, Radim, what do you think, is this good to go to stable
> > now?  This has been in since 4.6-rc1, so it's been a few weeks with
> > people running it already...
> 
> I think it is good to go.  No reasonable workload should regress and the
> fixed use-case is common on old linux guest.
> 
> This patch makes a difference if the guest doesn't EOI in PIT interrupts
> before the next one arrives.  PIT would have been unreliable in that
> situation, so all worloads that that could regress have likely been
> avoided.  Changes to NMI injection would need even crazier guest to
> regress.

Ok, thanks, leaving it in.

greg k-h

  reply	other threads:[~2016-04-12 14:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-11 23:23 [PATCH 4.5 007/238] KVM: i8254: change PIT discard tick policy Ben Hutchings
2016-04-12  1:21 ` Greg Kroah-Hartman
2016-04-12 13:30   ` Radim Krčmář
2016-04-12 14:13     ` Greg Kroah-Hartman [this message]
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=20160412141313.GA7996@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ben@decadent.org.uk \
    --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.