All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: speck@linutronix.de
Subject: [MODERATED] Re: [PATCH v2 0/4] performance walnuts
Date: Thu, 7 Mar 2019 23:06:48 +0100	[thread overview]
Message-ID: <20190307220648.GA7544@kroah.com> (raw)
In-Reply-To: <20190307214212.GB658@mgross-MOBL.amr.corp.intel.com>

On Thu, Mar 07, 2019 at 01:42:12PM -0800, speck for mark gross wrote:
> On Thu, Mar 07, 2019 at 03:13:17PM +0100, speck for Greg KH wrote:
> > On Wed, Mar 06, 2019 at 12:56:47PM +0100, speck for Greg KH wrote:
> > > On Wed, Mar 06, 2019 at 10:23:52AM +0100, speck for Thomas Gleixner wrote:
> > > > On Tue, 5 Mar 2019, speck for Peter Zijlstra wrote:
> > > > 
> > > > > Or whatever shiney new name they ought to get.
> > > > > 
> > > > > Apparently the intent is to have these patches magically appears in source
> > > > > repos on the 12th.
> > > > 
> > > > I made them magically appear in the speck repo:
> > > > 
> > > >   cvs.ou.linutronix.de:linux/speck/linux tsx-5.0
> > > > 
> > > > and backports in the branches tsx-4.20, tsx-4.19, tsx-4.14. Git bundles
> > > > are attached.
> > > > 
> > > > I leave the dead kernel backports to the honorable members of the Kernel
> > > > Necrophilia cult as usual.
> > > 
> > > Many thanks for doing these backports.  I'll use them for the stable
> > > updates next week.  As for kernels older than 4.14, I'll maybe try
> > > 4.9 on my own...
> > 
> > Attached below is the 4 patches backported to 4.9.y.  They build for me,
> > but I have no real way to test them (I didn't even boot them.)
> > 
> > If anyone cares about 4.9.y, can they test these out?  Note, all of the
> > major changes was in the last patch (see my sysfs rant for why that was
> > so).
> 
> I'm setting up a tree to run the same test cases we have been running on
> Peter's patch set recently.

Great, thanks!

As for 4.4.y, no, I'm not going to do patches for that tree.  If people
really want that, we can work on them after-the-fact on the stable
mailing list.  Hopefully no one is still using 4.4.y on x86 systems
anymore (except for enterprise kernels of course...)

thanks,

greg k-h

  reply	other threads:[~2019-03-07 22:07 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-05 21:23 [MODERATED] [PATCH v2 0/4] performance walnuts Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 1/4] perf/x86/intel: Make cpuc allocations consistent Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 2/4] perf/x86/intel: Generalize dynamic constraint creation Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 3/4] x86: Add TSX Force Abort CPUID/MSR Peter Zijlstra
2019-03-05 21:23 ` [MODERATED] [PATCH v2 4/4] perf/x86/intel: Implement support for TSX Force Abort Peter Zijlstra
2019-03-05 22:19 ` [MODERATED] Re: [PATCH v2 0/4] performance walnuts Linus Torvalds
2019-03-05 22:26   ` Jiri Kosina
2019-03-05 22:33   ` Nelson D'Souza
2019-03-06  9:23 ` Thomas Gleixner
2019-03-06 11:56   ` [MODERATED] " Greg KH
2019-03-06 13:02     ` David Woodhouse
2019-03-06 18:08       ` Greg KH
2019-03-06 18:32         ` Mark Hatle
2019-03-07 14:12           ` Greg KH
2019-03-07 17:42             ` Mark Hatle
2019-03-07 20:07             ` Thomas Gleixner
2019-03-07 14:13     ` [MODERATED] " Greg KH
2019-03-07 21:42       ` mark gross
2019-03-07 22:06         ` Greg KH [this message]
2019-03-08  9:15           ` Jiri Kosina

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=20190307220648.GA7544@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=speck@linutronix.de \
    /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.