linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Mark Langsdorf <mark.langsdorf@amd.com>,
	Joerg Roedel <joerg.roedel@amd.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][KVM][retry 1] Add support for Pause Filtering to AMD SVM
Date: Mon, 11 May 2009 18:28:38 +0300	[thread overview]
Message-ID: <4A084426.2080604@redhat.com> (raw)
In-Reply-To: <20090511151823.GC9492@elte.hu>

Ingo Molnar wrote:
> * Avi Kivity <avi@redhat.com> wrote:
>
>   
>>> I.e. the 3000 cycles value itself could be eliminated as well. 
>>> (with just a common-sense max of say 100,000 cycles enforced)
>>>       
>> Yeah, though that has a much smaller effect as it's only 
>> responsible for a few microseconds of spinning.
>>     
>
> 3000 cycles would be 1-2 usecs. Isnt the VM exit+entry cost still in 
> that range?
>   

It's 3000 executions of rep nop, so you need to account for the entire 
spinlock loop body.

The Linux spinlock is

             "1:\t"
             "cmpl %0, %2\n\t"
             "je 2f\n\t"
             "rep ; nop\n\t"
             "movzwl %1, %2\n\t"
             /* don't need lfence here, because loads are in-order */
             "jmp 1b\n"

5 instructions, maybe 2-3 cycles, not counting any special rep nop 
overhead.  Mark, any idea what the spin time is?

VM entry/exit is around 1us on the newer processors.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-05-11 15:29 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 [this message]
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
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=4A084426.2080604@redhat.com \
    --to=avi@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.langsdorf@amd.com \
    --cc=mingo@elte.hu \
    /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).