From: Stefan Hajnoczi <stefanha@gmail.com>
To: Al Patel <alps.oss@gmail.com>
Cc: qemu-devel@nongnu.org, qemu-discuss@nongnu.org
Subject: Re: [Qemu-devel] Question on qemu threads
Date: Thu, 2 Oct 2014 16:15:52 +0100 [thread overview]
Message-ID: <20141002151552.GG6250@stefanha-thinkpad.redhat.com> (raw)
In-Reply-To: <CAF9p440-TGKGGMNWY_=wdkn0Kr0JQJgZCMtmHit-iw2eh=TCKg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Tue, Sep 30, 2014 at 01:44:48PM -0400, Al Patel wrote:
> In the current system, what are the extra threads?
The set of thread is dynamic because worker threads are started and
terminated depending on guest activity. You cannot make assumptions
about threads and QEMU provides monitor commands that expose the tids.
> Secondly, I am currently not using libvirt and having to start qemu from
> command line. I still want to pin the vcpu to a pcpu and want to use
> taskset on a thread. Unless I know which thread is emulating the vcpu
> how can I pin that thread?
>
> Do you have any other thoughts on the pinning part?
Use libvirt if you can. It will save you a ton of time.
If you really cannot use it, you can still look at its source code to
understand how it does what it does. See qemuProcessDetectVcpuPIDs() in
libvirt and the QEMU query-cpus QMP command.
Stefan
[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2014-10-02 15:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 17:44 [Qemu-devel] Question on qemu threads Al Patel
2014-09-30 20:43 ` Brian Jackson
2014-10-02 15:15 ` Stefan Hajnoczi [this message]
2014-10-06 16:52 ` Al Patel
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=20141002151552.GG6250@stefanha-thinkpad.redhat.com \
--to=stefanha@gmail.com \
--cc=alps.oss@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-discuss@nongnu.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 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).