From: Avi Kivity <avi@redhat.com>
To: Mark Langsdorf <mark.langsdorf@amd.com>
Cc: Joerg Roedel <joerg.roedel@amd.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][KVM][retry 2] Add support for Pause Filtering to AMD SVM
Date: Fri, 08 May 2009 21:44:22 +0300 [thread overview]
Message-ID: <4A047D86.1070407@redhat.com> (raw)
In-Reply-To: <200905081203.55484.mark.langsdorf@amd.com>
Mark Langsdorf wrote:
> From 01813db8627e74018c8cec90df7e345839351f23 Mon Sep 17 00:00:00 2001
> From: Mark Langsdorf <mark.langsdorf@amd.com>
> Date: Thu, 7 May 2009 09:44:10 -0500
> Subject: [PATCH] Add support for Pause Filtering to AMD SVM
>
What's the differences wrt retry 1?
> This feature creates a new field in the VMCB called Pause
> Filter Count. If Pause Filter Count is greater than 0 and
> intercepting PAUSEs is enabled, the processor will increment
> an internal counter when a PAUSE instruction occurs instead
> of intercepting. When the internal counter reaches the
> Pause Filter Count value, a PAUSE intercept will occur.
>
> This feature can be used to detect contended spinlocks,
> especially when the lock holding VCPU is not scheduled.
> Rescheduling another VCPU prevents the VCPU seeking the
> lock from wasting its quantum by spinning idly.
>
> Experimental results show that most spinlocks are held
> for less than 1000 PAUSE cycles or more than a few
> thousand. Default the Pause Filter Counter to 3000 to
> detect the contended spinlocks.
>
3000.
> Processor support for this feature is indicated by a CPUID
> bit.
>
> On a 24 core system running 4 guests each with 16 VCPUs,
> this patch improved overall performance of each guest's
> 32 job kernbench by approximately 1%. Further performance
> improvement may be possible with a more sophisticated
> yield algorithm.
>
Like I mentioned earlier, I don't think schedule() does anything on CFS.
Try sched_yield(), but set /proc/sys/kernel/sched_compat_yield.
> +
> + if (svm_has(SVM_FEATURE_PAUSE_FILTER)) {
> + control->pause_filter_count = 5000;
> + control->intercept |= (1ULL << INTERCEPT_PAUSE);
> + }
> +
>
Here, 5000?
> }
>
> static int svm_vcpu_reset(struct kvm_vcpu *vcpu)
> @@ -2087,6 +2094,15 @@ static int interrupt_window_interception(struct vcpu_svm *svm,
> return 1;
> }
>
> +static int pause_interception(struct vcpu_svm *svm, struct kvm_run *kvm_run)
> +{
> + /* Simple yield */
> + vcpu_put(&svm->vcpu);
> + schedule();
> + vcpu_load(&svm->vcpu);
> + return 1;
> +}
> +
>
You don't need to vcpu_put() and vcpu_load(). The scheduler will call
them for you if/when it switches tasks.
--
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.
next prev parent reply other threads:[~2009-05-08 18:44 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-05 14:09 [PATCH][KVM] Add support for Pause Filtering to AMD SVM Mark Langsdorf
2009-05-05 16:05 ` Bert Wesarg
2009-05-07 13:55 ` Joerg Roedel
2009-05-07 15:00 ` [PATCH][KVM][retry 1] " Mark Langsdorf
2009-05-07 15:31 ` Avi Kivity
2009-05-11 14:15 ` Ingo Molnar
2009-05-11 14:24 ` Avi Kivity
2009-05-11 14:33 ` Ingo Molnar
2009-05-11 14:51 ` Avi Kivity
2009-05-11 14:59 ` Ingo Molnar
2009-05-11 15:12 ` Avi Kivity
2009-05-11 15:18 ` Ingo Molnar
2009-05-11 15:28 ` Avi Kivity
2009-05-11 15:36 ` Langsdorf, Mark
2009-05-11 15:40 ` Avi Kivity
2009-05-11 15:58 ` [PATCH][KVM][retry 1] Add support for Pause Filtering to AMDSVM Langsdorf, Mark
2009-05-11 15:01 ` [PATCH][KVM][retry 1] Add support for Pause Filtering to AMD SVM Peter Zijlstra
2009-05-11 15:06 ` Avi Kivity
2009-05-11 14:42 ` Peter Zijlstra
2009-05-11 15:05 ` Avi Kivity
2009-05-08 17:03 ` [PATCH][KVM][retry 2] " Mark Langsdorf
2009-05-08 18:44 ` Avi Kivity [this message]
2009-05-08 18:47 ` Langsdorf, Mark
2009-05-19 18:56 ` [PATCH][KVM][retry 3] " Mark Langsdorf
2009-05-20 7:40 ` Ingo Molnar
2009-05-20 7:59 ` Peter Zijlstra
2009-05-20 8:38 ` Avi Kivity
2009-05-20 8:42 ` Peter Zijlstra
2009-05-20 8:49 ` Avi Kivity
2009-05-20 8:54 ` Peter Zijlstra
2009-05-20 9:04 ` Avi Kivity
2009-05-20 9:10 ` Peter Zijlstra
2009-05-20 9:17 ` Avi Kivity
2009-05-20 13:52 ` Langsdorf, Mark
2009-05-20 12:00 ` Avi Kivity
2009-05-20 22:25 ` [PATCH][KVM][retry 4] " Mark Langsdorf
2009-05-21 8:47 ` Avi Kivity
2009-07-08 5:19 ` Sheng Yang
2009-07-08 14:59 ` Langsdorf, Mark
2009-07-09 1:50 ` Sheng Yang
2009-07-22 22:40 ` Langsdorf, Mark
2009-08-05 9:08 ` Zhai, Edwin
2009-05-11 14:38 ` [PATCH][KVM] " Peter Zijlstra
2009-05-11 14:51 ` Ingo Molnar
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=4A047D86.1070407@redhat.com \
--to=avi@redhat.com \
--cc=joerg.roedel@amd.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.langsdorf@amd.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;
as well as URLs for NNTP newsgroup(s).