From: Waiman Long <longman@redhat.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-arch@vger.kernel.org, "Juergen Gross" <jgross@suse.com>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
x86@kernel.org, kvm@vger.kernel.org,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Boris Ostrovsky" <boris.ostrovsky@oracle.com>,
"Pan Xinhui" <xinhui.pan@linux.vnet.ibm.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
"Chris Wright" <chrisw@sous-sol.org>,
"Ingo Molnar" <mingo@redhat.com>,
"H. Peter Anvin" <hpa@zytor.com>,
xen-devel@lists.xenproject.org,
"Alok Kataria" <akataria@vmware.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function
Date: Fri, 10 Feb 2017 11:35:02 -0500 [thread overview]
Message-ID: <1c949ed0-1b88-ae6e-4e6c-426502bfab5f@redhat.com> (raw)
In-Reply-To: <20170210161928.GI6515@twins.programming.kicks-ass.net>
On 02/10/2017 11:19 AM, Peter Zijlstra wrote:
> On Fri, Feb 10, 2017 at 10:43:09AM -0500, Waiman Long wrote:
>> It was found when running fio sequential write test with a XFS ramdisk
>> on a VM running on a 2-socket x86-64 system, the %CPU times as reported
>> by perf were as follows:
>>
>> 69.75% 0.59% fio [k] down_write
>> 69.15% 0.01% fio [k] call_rwsem_down_write_failed
>> 67.12% 1.12% fio [k] rwsem_down_write_failed
>> 63.48% 52.77% fio [k] osq_lock
>> 9.46% 7.88% fio [k] __raw_callee_save___kvm_vcpu_is_preempt
>> 3.93% 3.93% fio [k] __kvm_vcpu_is_preempted
>>
> Thinking about this again, wouldn't something like the below also work?
>
>
> diff --git a/arch/x86/kernel/kvm.c b/arch/x86/kernel/kvm.c
> index 099fcba4981d..6aa33702c15c 100644
> --- a/arch/x86/kernel/kvm.c
> +++ b/arch/x86/kernel/kvm.c
> @@ -589,6 +589,7 @@ static void kvm_wait(u8 *ptr, u8 val)
> local_irq_restore(flags);
> }
>
> +#ifdef CONFIG_X86_32
> __visible bool __kvm_vcpu_is_preempted(int cpu)
> {
> struct kvm_steal_time *src = &per_cpu(steal_time, cpu);
> @@ -597,6 +598,31 @@ __visible bool __kvm_vcpu_is_preempted(int cpu)
> }
> PV_CALLEE_SAVE_REGS_THUNK(__kvm_vcpu_is_preempted);
>
> +#else
> +
> +extern bool __raw_callee_save___kvm_vcpu_is_preempted(int);
> +
> +asm(
> +".pushsection .text;"
> +".global __raw_callee_save___kvm_vcpu_is_preempted;"
> +".type __raw_callee_save___kvm_vcpu_is_preempted, @function;"
> +"__raw_callee_save___kvm_vcpu_is_preempted:"
> +FRAME_BEGIN
> +"push %rdi;"
> +"push %rdx;"
> +"movslq %edi, %rdi;"
> +"movq $steal_time+16, %rax;"
> +"movq __per_cpu_offset(,%rdi,8), %rdx;"
> +"cmpb $0, (%rdx,%rax);"
> +"setne %al;"
> +"pop %rdx;"
> +"pop %rdi;"
> +FRAME_END
> +"ret;"
> +".popsection");
> +
> +#endif
> +
> /*
> * Setup pv_lock_ops to exploit KVM_FEATURE_PV_UNHALT if present.
> */
That should work for now. I have done something similar for
__pv_queued_spin_unlock. However, this has the problem of creating a
dependency on the exact layout of the steal_time structure. Maybe the
constant 16 can be passed in as a parameter offsetof(struct
kvm_steal_time, preempted) to the asm call.
Cheers,
Longman
next prev parent reply other threads:[~2017-02-10 16:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-10 15:43 [PATCH v2] x86/paravirt: Don't make vcpu_is_preempted() a callee-save function Waiman Long
2017-02-10 16:19 ` Peter Zijlstra
2017-02-10 16:35 ` Waiman Long [this message]
2017-02-10 17:00 ` Waiman Long
2017-02-13 10:47 ` Peter Zijlstra
2017-02-13 10:53 ` Peter Zijlstra
2017-02-13 19:42 ` Waiman Long
2017-02-13 20:06 ` hpa
2017-02-13 21:57 ` Peter Zijlstra
2017-02-13 22:24 ` Waiman Long
2017-02-13 22:31 ` Peter Zijlstra
[not found] ` <3dc50409-60dd-ad47-f971-448191e66038@redhat.com>
2017-02-13 20:12 ` Waiman Long
2017-02-13 21:52 ` Peter Zijlstra
2017-02-13 22:00 ` hpa
2017-02-13 22:07 ` hpa
2017-02-13 22:34 ` Waiman Long
2017-02-13 22:36 ` hpa
2017-02-14 9:39 ` Peter Zijlstra
2017-02-14 14:46 ` Waiman Long
2017-02-14 16:03 ` Peter Zijlstra
2017-02-14 16:18 ` [Xen-devel] " Andrew Cooper
2017-02-13 19:41 ` Waiman Long
2017-02-10 16:22 ` Paolo Bonzini
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=1c949ed0-1b88-ae6e-4e6c-426502bfab5f@redhat.com \
--to=longman@redhat.com \
--cc=akataria@vmware.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chrisw@sous-sol.org \
--cc=hpa@zytor.com \
--cc=jeremy@goop.org \
--cc=jgross@suse.com \
--cc=kvm@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--cc=virtualization@lists.linux-foundation.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xinhui.pan@linux.vnet.ibm.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