public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Oscar Garcia <oscar@softlab.cs.tsukuba.ac.jp>
Cc: kvm@vger.kernel.org
Subject: Re: VMEXIT and Threads
Date: Mon, 6 Oct 2014 16:07:16 -0300	[thread overview]
Message-ID: <20141006190716.GA5731@amt.cnet> (raw)
In-Reply-To: <54321E64.8070306@softlab.cs.tsukuba.ac.jp>


On Mon, Oct 06, 2014 at 01:45:24PM +0900, Oscar Garcia wrote:
> Hello,
>
> I have a question about parallel vmexit calls, I would appreciate
> any answer or suggestion.
>
> I have a host with debian 7 (intel i7 - RAM 8GB), the guest OS is
> also debian. I am running a program with some threads, every thread
> makes a vmexit call. 

How is that vmexit call made?

> Also every thread runs in a isolated vcpu. The
> problem is that the program does not run fluently, it looks like
> that every thread interfere with each other.

Can you be more precise about this? Did you perform a measurement?

>  This situation does not happen when separately processes call vmexit
> simultaneously. The question is: there is any restriction (any lock)
> that block the threads. I am not sure maybe libc, RCU, on even Qemu
> and KVM?

In QEMU there is a mutex which is shared by all vcpus, and is acquired 
right after entry in QEMU, named qemu_mutex. 


      parent reply	other threads:[~2014-10-06 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-06  4:45 VMEXIT and Threads Oscar Garcia
2014-10-06  6:51 ` Paolo Bonzini
2014-10-06  7:29   ` Jan Kiszka
2014-10-06 19:07 ` Marcelo Tosatti [this message]

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=20141006190716.GA5731@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=oscar@softlab.cs.tsukuba.ac.jp \
    /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