All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: armbru@redhat.com, qemu-devel@nongnu.org, lcapitulino@redhat.com
Subject: Re: [Qemu-devel] [PATCH v2] scripts: qmp: Introduce vcpu pinning helper script
Date: Tue, 8 Nov 2016 00:21:28 +0800	[thread overview]
Message-ID: <20161107162128.GC3719@pxdev.xzpeter.org> (raw)
In-Reply-To: <2f10cdd9-0424-d61e-a36b-5c4895ecffbb@redhat.com>

On Thu, Nov 03, 2016 at 04:01:08PM +0100, Maxime Coquelin wrote:
> Hi Peter,
> 
> On 10/04/2016 01:22 PM, Maxime Coquelin wrote:
> >This python script calls 'query-cpus' QMP command to retrieve
> >vCPUs thread IDs.
> >Thread IDs are then used by taskset to pin vCPUs to physical
> >CPUs passed in command line.
> >
> >In case more vCPUs are present than the number of CPUs assigned
> >in command line, multiple vCPUs get pinned to physical CPUs.
> >
> >If multiple vCPUs share a same thread ID (e.g. with TCG), the
> >thread ID is pinned a single time.
> >
> >Signed-off-by: Maxime Coquelin <maxime.coquelin@redhat.com>
> >---
> >Changes since RFC:
> >==================
> > - If vCPUs share a same TID, don't pin them multiple times (peterx)
> >
> > scripts/qmp/qmp-vcpu-pin | 45 +++++++++++++++++++++++++++++++++++++++++++++
> > 1 file changed, 45 insertions(+)
> > create mode 100755 scripts/qmp/qmp-vcpu-pin
> 
> I added your proposed change not to pin same TID multiple time,
> does it look good to you?

Though I am still not familiar with the python and QMP stuffs, but yes
this looks good to me, so:

Reviewed-by: Peter Xu <peterx@redhat.com>

Sorry for the late response.

-- peterx

      reply	other threads:[~2016-11-07 16:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-04 11:22 [Qemu-devel] [PATCH v2] scripts: qmp: Introduce vcpu pinning helper script Maxime Coquelin
2016-11-03 15:01 ` Maxime Coquelin
2016-11-07 16:21   ` Peter Xu [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=20161107162128.GC3719@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=armbru@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=qemu-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.