mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Oliver Sang <oliver.sang@intel.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: Anna-Maria Behnsen <anna-maria@linutronix.de>,
	<oe-lkp@lists.linux.dev>, <lkp@intel.com>,
	<linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, <ying.huang@intel.com>,
	<feng.tang@intel.com>, <fengwei.yin@intel.com>,
	<oliver.sang@intel.com>
Subject: Re: [linus:master] [timers]  7ee9887703: stress-ng.uprobe.ops_per_sec -17.1% regression
Date: Tue, 2 Apr 2024 09:46:29 +0800	[thread overview]
Message-ID: <Zgtjdd0C2FzYVBto@xsang-OptiPlex-9020> (raw)
In-Reply-To: <Zgs5NxoUUoGIkuQO@pavilion.home>

hi, Frederic Weisbecker,

On Tue, Apr 02, 2024 at 12:46:15AM +0200, Frederic Weisbecker wrote:
> Le Wed, Mar 27, 2024 at 04:39:17PM +0800, kernel test robot a écrit :
> > 
> > 
> > Hello,
> > 
> > 
> > we reported
> > "[tip:timers/core] [timers]  7ee9887703:  netperf.Throughput_Mbps -1.2% regression"
> > in
> > https://lore.kernel.org/all/202403011511.24defbbd-oliver.sang@intel.com/
> > 
> > now we noticed this commit is in mainline and we captured further results.
> > 
> > still include netperf results for complete. below details FYI.
> > 
> > 
> > kernel test robot noticed a -17.1% regression of stress-ng.uprobe.ops_per_sec
> > on:
> 
> The good news is that I can reproduce.
> It has made me spot something already:
> 
>    https://lore.kernel.org/lkml/ZgsynV536q1L17IS@pavilion.home/T/#m28c37a943fdbcbadf0332cf9c32c350c74c403b0
> 
> But that's not enough to fix the regression. Investigation continues...

Thanks a lot for information! if you want us test any patch, please let us know.

> 
> Thanks.

  reply	other threads:[~2024-04-02  1:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27  8:39 kernel test robot
2024-04-01 22:46 ` Frederic Weisbecker
2024-04-02  1:46   ` Oliver Sang [this message]
2024-04-04 14:05     ` Frederic Weisbecker
2024-04-25  8:23     ` Anna-Maria Behnsen
2024-04-25 10:15       ` Christian Loehle
2024-04-26 10:15         ` Anna-Maria Behnsen
2024-04-26 11:35           ` Frederic Weisbecker
2024-04-26 15:39           ` Christian Loehle
2024-04-26  6:53       ` Oliver Sang
2024-04-26 16:03       ` Rafael J. Wysocki
2024-04-29  7:53         ` Lukasz Luba
2024-04-29  9:26           ` Anna-Maria Behnsen
2024-04-29 10:40             ` Anna-Maria Behnsen
2024-04-29 17:02               ` Rafael J. Wysocki
2024-05-02 12:56                 ` Anna-Maria Behnsen

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=Zgtjdd0C2FzYVBto@xsang-OptiPlex-9020 \
    --to=oliver.sang@intel.com \
    --cc=anna-maria@linutronix.de \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-lkp@lists.linux.dev \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®