All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ryan Harper <ryanh@us.ibm.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH 0 of 5] multiple cpumask and vcpu-pin all keyword
Date: Wed, 16 Aug 2006 15:49:34 -0500	[thread overview]
Message-ID: <patchbomb.1155761374@localhost.localdomain> (raw)

[-- Attachment #1: Type: text/plain, Size: 1019 bytes --]

This series of patches relates to the cpus parameter and pinning vcpus.
The first patch is a clean-up of getVcpuInfo, which previously only
returned the vcpu to cpu mapping.  This was insufficient for extracting
affinity information.  The patch extends getVcpuInfo to return a dict of
all the fields in xm vcpu-list for a domain.  It also fixes a couple
users of the function and moves them to a new vcpu_to_cpu function which
retains the old behavior of getVcpuInfo.

The second patch adds multiple cpumask support to the cpus variable. We
currently support two formats:

cpus = [ "0", "2-4" ] and cpus = "0|2-4".  The documentation encourages
the use of the python list notation.

The third patch introduces a testcase for the cpus parameter in the
create subset.

The forth patch adds support for the keyword 'all' to the vcpu-pin
operation.  Using 'all' in place of a specific vcpu will apply the
cpumask to all vcpus in the domain.

The fifth patch creates a testcase for the 'all' keyword in the vcpu-pin
subset.

[-- Attachment #2: Type: text/plain, Size: 1278 bytes --]

17 files changed, 278 insertions(+), 60 deletions(-)
docs/man/xm.pod.1                                             |    4 
tools/examples/xmexample.hvm                                  |    9 -
tools/examples/xmexample.vti                                  |    9 -
tools/examples/xmexample1                                     |    9 -
tools/examples/xmexample2                                     |   11 +
tools/examples/xmexample3                                     |   12 -
tools/python/xen/xend/XendDomain.py                           |   17 +-
tools/python/xen/xend/XendDomainInfo.py                       |   64 +++++--
tools/python/xen/xend/server/SrvDomain.py                     |    2 
tools/python/xen/xm/main.py                                   |    9 -
tools/xm-test/lib/XmTestLib/Xm.py                             |   31 +++
tools/xm-test/tests/create/17_create_cpusparm_pos.py          |   81 ++++++++++
tools/xm-test/tests/create/Makefile.am                        |    3 
tools/xm-test/tests/vcpu-disable/01_vcpu-disable_basic_pos.py |   16 +
tools/xm-test/tests/vcpu-pin/01_vcpu-pin_basic_pos.py         |    4 
tools/xm-test/tests/vcpu-pin/02_vcpu-pin_all_pos.py           |   54 ++++++
tools/xm-test/tests/vcpu-pin/Makefile.am                      |    3 

[-- Attachment #3: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2006-08-16 20:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-16 20:49 Ryan Harper [this message]
2006-08-16 20:49 ` [PATCH 1 of 5] Change getVcpuInfo to return more information Ryan Harper
2006-08-16 20:49 ` [PATCH 2 of 5] Add support for specifying multi cpumasks in cpus parameter Ryan Harper
2006-08-16 20:49 ` [PATCH 3 of 5] Add testcase for multi-cpumask " Ryan Harper
2006-08-16 20:49 ` [PATCH 4 of 5] Add keyword 'all' to vcpu-pin Ryan Harper
2006-08-16 20:49 ` [PATCH 5 of 5] Add testcase for vcpu-pin all Ryan Harper
2006-08-16 21:02 ` [PATCH 0 of 5] multiple cpumask and vcpu-pin all keyword Daniel Veillard
2006-08-16 21:05   ` Ryan Harper
2006-08-16 21:12     ` Ryan Harper
2006-08-16 21:22       ` Daniel Veillard

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=patchbomb.1155761374@localhost.localdomain \
    --to=ryanh@us.ibm.com \
    --cc=xen-devel@lists.xensource.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 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.