From: Greg KH <greg@kroah.com>
To: Valentin Vidic <Valentin.Vidic@CARNet.hr>
Cc: stable@vger.kernel.org, Michael Lass <bevan@bi-co.net>
Subject: Re: Xen: decreasing cpu steal clock counter
Date: Thu, 31 Aug 2017 16:08:51 +0200 [thread overview]
Message-ID: <20170831140851.GA5242@kroah.com> (raw)
In-Reply-To: <20170831135139.udxgnxuhvvrjksjd@gavran.carpriv.carnet.hr>
On Thu, Aug 31, 2017 at 03:51:39PM +0200, Valentin Vidic wrote:
> On Thu, Aug 31, 2017 at 03:37:09PM +0200, Greg KH wrote:
> > What patch?
>
> Attaching the patch from this link:
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=871608;filename=handle-decreasing-steal-clock.patch;msg=5
I can't do anything with non-upstream patches for stable kernels. You
have read
https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
right?
> > What is the git commit id of the aptch in Linus's tree that resolves
> > this issue?
>
> The issue was fixed later in 4.11, but this might be a bigger change
> so not sure if you want to take that:
>
> 2b1f967d80e8e5d7361f0e1654c842869570f573
> sched/cputime: Complete nsec conversion of tick based accounting
I always would rather take the original change that is in Linus's tree,
as 99% of the time we take something different, it ends up being wrong.
But I kind of doubt the above git commit id is the right one to take :(
I need some feedback from the Xen maintainers before I can do anything
else.
thanks,
greg k-h
next prev parent reply other threads:[~2017-08-31 14:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-31 10:44 Xen: decreasing cpu steal clock counter Valentin Vidic
2017-08-31 13:37 ` Greg KH
2017-08-31 13:51 ` Valentin Vidic
2017-08-31 14:08 ` Greg KH [this message]
2017-08-31 15:05 ` Valentin Vidic
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=20170831140851.GA5242@kroah.com \
--to=greg@kroah.com \
--cc=Valentin.Vidic@CARNet.hr \
--cc=bevan@bi-co.net \
--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.