mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Bae, Chang Seok" <chang.seok.bae@intel.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Sang, Oliver" <oliver.sang@intel.com>,
	Borislav Petkov <bp@suse.de>, LKML <linux-kernel@vger.kernel.org>,
	"lkp@lists.01.org" <lkp@lists.01.org>, lkp <lkp@intel.com>,
	"Huang, Ying" <ying.huang@intel.com>,
	"Tang, Feng" <feng.tang@intel.com>,
	"zhengjun.xing@linux.intel.com" <zhengjun.xing@linux.intel.com>,
	"Yin, Fengwei" <fengwei.yin@intel.com>
Subject: Re: [x86/signal]  3aac3ebea0:  will-it-scale.per_thread_ops -11.9% regression
Date: Tue, 7 Dec 2021 18:49:59 +0000	[thread overview]
Message-ID: <81783AEA-1313-4353-837D-8217DEF3B9A2@intel.com> (raw)
In-Reply-To: <87bl1s357p.ffs@tglx>

On Dec 7, 2021, at 05:38, Thomas Gleixner <tglx@linutronix.de> wrote:
> On Tue, Dec 07 2021 at 09:21, kernel test robot wrote:
>> (please be noted we made some further analysis before reporting out,
>> and thought it's likely the regression is related with the extra spinlock
>> introducded by enalbling DYNAMIC_SIGFRAME. below is the full report.)
>> 
>> FYI, we noticed a -11.9% regression of will-it-scale.per_thread_ops due to commit:
> 
> Does that use sigaltstack() ?

FWIW, I was also wondering about this with:

$ git clone https://github.com/antonblanchard/will-it-scale.git
$ cd will-it-scale/
$ git grep sigaltstack
$

But, the test seems to use python via runtest.py. And the python code has
sigaltstack():
    https://github.com/python/cpython/blob/main/Modules/faulthandler.c#L454

Thanks,
Chang

  reply	other threads:[~2021-12-07 18:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-07  1:21 kernel test robot
2021-12-07  1:44 ` Oliver Sang
2021-12-07 13:38 ` Thomas Gleixner
2021-12-07 18:49   ` Bae, Chang Seok [this message]
2021-12-07 20:36     ` Thomas Gleixner
2021-12-07 22:17       ` Bae, Chang Seok
2021-12-08  0:59         ` Yin Fengwei
2021-12-09  2:30   ` [LKP] " Carel Si
2021-12-07 23:14 ` Dave Hansen
2021-12-08 18:00   ` Bae, Chang Seok
2021-12-08 18:20     ` Dave Hansen
2021-12-08 19:14       ` Thomas Gleixner
2021-12-09  8:13       ` Thomas Gleixner
2021-12-10  4:15   ` [LKP] " Carel Si

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=81783AEA-1313-4353-837D-8217DEF3B9A2@intel.com \
    --to=chang.seok.bae@intel.com \
    --cc=bp@suse.de \
    --cc=feng.tang@intel.com \
    --cc=fengwei.yin@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=lkp@lists.01.org \
    --cc=oliver.sang@intel.com \
    --cc=tglx@linutronix.de \
    --cc=ying.huang@intel.com \
    --cc=zhengjun.xing@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 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®