From: Greg KH <greg@kroah.com>
To: Ingo Molnar <mingo@kernel.org>
Cc: karol herbst <karolherbst@gmail.com>,
stable kernel team <stable@vger.kernel.org>
Subject: Re: mmiotrace fixes in stable kernels
Date: Mon, 2 May 2016 11:44:42 -0700 [thread overview]
Message-ID: <20160502184442.GA18236@kroah.com> (raw)
In-Reply-To: <20160425073951.GB27425@gmail.com>
On Mon, Apr 25, 2016 at 09:39:51AM +0200, Ingo Molnar wrote:
>
> (Greg Cc:-ed)
>
> * karol herbst <karolherbst@gmail.com> wrote:
>
> > I am sure this is the only one, but I never checked if anything else
> > is needed. Maybe to be sure it would be safe to just add it to 4.5 and
> > 4.4, because I am sure it works there without needing anything else
> > and most distributions have already packages for 4.4 or newer.
> >
> > Thanks
> >
> > Karol
> >
> > 2016-04-23 13:05 GMT+02:00 Ingo Molnar <mingo@kernel.org>:
> > >
> > > * karol herbst <karolherbst@gmail.com> wrote:
> > >
> > >> Hi Ingo,
> > >>
> > >> thanks for merging my mmiotrace fix :) As it seems it helps quite a
> > >> lot and I was wondering if it would be able to merge the fix for older
> > >> kernels as well.
> > >
> > > Sure. Do we only need:
> > >
> > > cfa52c0cfa4d ("x86/mm/kmmio: Fix mmiotrace for hugepages")
> > >
> > > ... or are other fixes necessary as well?
>
> Ok.
>
> Greg, mind picking up upstream commit:
>
> cfa52c0cfa4d ("x86/mm/kmmio: Fix mmiotrace for hugepages")
>
> for -stable v4.3, v4.4 and v4.5? I checked that it cherry-picked fine. (I have not
> performed a functional test on the other hand, maybe Karol wants to do that?)
Now queued up, thanks.
greg k-h
prev parent reply other threads:[~2016-05-02 18:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAEXux-aQ_=bMQiN3dbx0zT74BQpOV2YENnc2czxF9bdwc58z+g@mail.gmail.com>
[not found] ` <20160423110546.GA12034@gmail.com>
[not found] ` <CAEXux-arpPfdBkQ=EbQjuZOggH2W4XcSq4QoTmqzKSsGP_MLdA@mail.gmail.com>
2016-04-25 7:39 ` mmiotrace fixes in stable kernels Ingo Molnar
2016-04-25 10:49 ` karol herbst
2016-05-02 18:44 ` Greg KH [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=20160502184442.GA18236@kroah.com \
--to=greg@kroah.com \
--cc=karolherbst@gmail.com \
--cc=mingo@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).