From: Peter Zijlstra <peterz@infradead.org>
To: lkp@lists.01.org
Subject: Re: [x86, paravirt] fd6f48529f: aim7.jobs-per-min -26.1% regression
Date: Thu, 01 Dec 2016 08:04:06 +0100 [thread overview]
Message-ID: <20161201070406.GI3092@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <20161130180729.GB15492@yexl-desktop>
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
On Thu, Dec 01, 2016 at 02:07:29AM +0800, kernel test robot wrote:
>
> Greeting,
>
> FYI, we noticed a -26.1% regression of aim7.jobs-per-min due to commit:
>
>
> commit: fd6f48529f4067c6bfbead88d3d7d117d51150f6 ("x86,paravirt: Optimize native pv_lock_ops.vcpu_is_preempted")
> https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
>
>
> 8ba24710fb279053 fd6f48529f4067c6bfbead88d3
So that really is against its parent..
Does something like so fix it?
--- a/arch/x86/kernel/paravirt_patch_32.c
+++ b/arch/x86/kernel/paravirt_patch_32.c
@@ -56,15 +56,19 @@ unsigned native_patch(u8 type, u16 clobb
end = end_pv_lock_ops_queued_spin_unlock;
goto patch_site;
}
+ goto patch_default;
+
case PARAVIRT_PATCH(pv_lock_ops.vcpu_is_preempted):
if (pv_is_native_vcpu_is_preempted()) {
start = start_pv_lock_ops_vcpu_is_preempted;
end = end_pv_lock_ops_vcpu_is_preempted;
goto patch_site;
}
+ goto patch_default;
#endif
default:
+patch_default:
ret = paravirt_patch_default(type, clobbers, ibuf, addr, len);
break;
--- a/arch/x86/kernel/paravirt_patch_64.c
+++ b/arch/x86/kernel/paravirt_patch_64.c
@@ -68,15 +68,19 @@ unsigned native_patch(u8 type, u16 clobb
end = end_pv_lock_ops_queued_spin_unlock;
goto patch_site;
}
+ goto patch_default;
+
case PARAVIRT_PATCH(pv_lock_ops.vcpu_is_preempted):
if (pv_is_native_vcpu_is_preempted()) {
start = start_pv_lock_ops_vcpu_is_preempted;
end = end_pv_lock_ops_vcpu_is_preempted;
goto patch_site;
}
+ goto patch_default;
#endif
default:
+patch_default:
ret = paravirt_patch_default(type, clobbers, ibuf, addr, len);
break;
next prev parent reply other threads:[~2016-12-01 7:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-30 18:07 [x86, paravirt] fd6f48529f: aim7.jobs-per-min -26.1% regression kernel test robot
2016-12-01 7:04 ` Peter Zijlstra [this message]
2016-11-30 23:17 ` Ye Xiaolong
2016-12-01 7:21 ` Peter Zijlstra
2016-12-01 16:49 ` Ye Xiaolong
2016-12-07 13:17 ` Peter Zijlstra
2016-12-08 1:12 ` Huang, Ying
2016-12-08 8:39 ` Huang, Ying
2016-12-08 11:08 ` Peter Zijlstra
2016-12-09 2:36 ` Huang, Ying
2016-12-09 5:36 ` Peter Zijlstra
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=20161201070406.GI3092@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=lkp@lists.01.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 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.