All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: "Jin, Yao" <yao.jin@linux.intel.com>,
	stable@vger.kernel.org, "Jin, Yao" <yao.jin@intel.com>,
	"Liang, Kan" <kan.liang@intel.com>
Subject: Re: perf: Support uncore in 4.9.112
Date: Wed, 18 Jul 2018 10:09:44 -0700	[thread overview]
Message-ID: <20180718170944.GF25412@tassilo.jf.intel.com> (raw)
In-Reply-To: <20180718092950.GD17551@kroah.com>

On Wed, Jul 18, 2018 at 11:29:50AM +0200, Greg KH wrote:
> On Wed, Jul 18, 2018 at 08:41:28AM +0800, Jin, Yao wrote:
> > Hi,
> > 
> > The stable kernel 4.9.112 has supported Intel uncore feature in perf core.
> > While it also needs the perf tool supporting to let perf uncore feature
> > work.
> > 
> > Following backport patches enables basic perf uncore feature in 4.9.112.
> > 
> > For example, on skylake desktop,
> 
> Why would anyone care about this on a "desktop" for 4.9?  No one should
> be using 4.9.y on a desktop anymore, it's over 2 years old, why would
> they expect any "new" hardware support to work for them?  Why can't they

It's actually not new hardware support: Skylake is fairly old hardware
at this point.

> just use 4.14.y or better yet. 4.17.y?  Desktops should NOT be using a 2
> year old kernel.
> 
> Heck, servers shouldn't either, but that's a totally different rant.

These chips are not only used in desktops but also in servers.

> However, for hardware that is newer than the base kernel version
> release, I have no sympathy.  Just use a newer kernel, right?

We have customers which are on old kernels with new hardware. 
The backports happen either way. This is just an attempt to do it in a
coordinated fashion.

> What distro relies on a 4.9 kernel for brand new hardware that does not
> already support a newer kernel release for such hardware?

None afaik, but there is a lot of Linux use beyond distros.

-Andi

  reply	other threads:[~2018-07-18 17:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-18  0:41 perf: Support uncore in 4.9.112 Jin, Yao
2018-07-18  9:29 ` Greg KH
2018-07-18 17:09   ` Andi Kleen [this message]
2018-07-18 17:39     ` Greg KH
2018-07-19  4:43       ` Jin, Yao
2018-08-06  0:46       ` Jin, Yao
2018-08-07 13:09         ` Greg KH
2018-08-08  0:58           ` Jin, Yao
2018-08-08  6:40             ` Greg KH
2018-08-08  7:37               ` Jin, Yao
2018-08-08  8:40                 ` Greg KH
2018-08-09  5:59                   ` Jin, Yao
2018-08-09  7:47                     ` Greg KH
2018-08-09  8:07                       ` Jin, Yao

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=20180718170944.GF25412@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=kan.liang@intel.com \
    --cc=stable@vger.kernel.org \
    --cc=yao.jin@intel.com \
    --cc=yao.jin@linux.intel.com \
    /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.