All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Fehlig <jfehlig@suse.com>
To: Michal Privoznik <mprivozn@redhat.com>, libvir-list@redhat.com
Cc: ian.campbell@citrix.com, xen-devel@lists.xen.org
Subject: Re: [libvirt] [PATCH V2] Xen: support maxvcpus in xm and xl config
Date: Fri, 18 Dec 2015 18:25:49 -0700	[thread overview]
Message-ID: <5674B21D.8060702__37865.6091787436$1450488478$gmane$org@suse.com> (raw)
In-Reply-To: <5673F25B.70606@redhat.com>

On 12/18/2015 04:47 AM, Michal Privoznik wrote:
> On 15.12.2015 23:20, Jim Fehlig wrote:
>> From: Ian Campbell <ian.campbell@citrix.com>
>>
>> xend prior to 4.0 understands vcpus as maxvcpus and vcpu_avail
>> as a bit map of which cpus are online (default is all).
>>
>> xend from 4.0 onwards understands maxvcpus as maxvcpus and
>> vcpus as the number which are online (from 0..N-1). The
>> upstream commit (68a94cf528e6 "xm: Add maxvcpus support")
>> claims that if maxvcpus is omitted then the old behaviour
>> (i.e. obeying vcpu_avail) is retained, but AFAICT it was not,
>> in this case vcpu==maxcpus==online cpus. This is good for us
>> because handling anything else would be fiddly.
>>
>> This patch changes parsing of the virDomainDef maxvcpus and vcpus
>> entries to use the corresponding 'maxvcpus' and 'vcpus' settings
>> from xm and xl config. It also drops use of the old Xen 3.x
>> 'vcpu_avail' setting.
>>
>> The change also removes the maxvcpus limit of MAX_VIRT_VCPUS (since
>> maxvcpus is simply a count, not a bit mask), which is particularly
>> crucial on ARM where MAX_VIRT_CPUS == 1 (since all guests are
>> expected to support vcpu placement, and therefore only the boot
>> vcpu's info lives in the shared info page).
>>
>> Existing tests adjusted accordingly, and new tests added for the
>> 'maxvcpus' setting.
>>
>> Signed-off-by: Jim Fehlig <jfehlig@suse.com>
>> ---
>>
>> This is a respin of Ian's patch [1] to support parsing/formatting of the
>> 'maxvcpus' xm and xl config setting. It goes a bit further and removes
>> the old Xen 3.x 'vcpu_avail' setting and lifts the maxvcpus limit of
>> MAX_VIRT_CPUS entirely.
>>
>> The patch is based on my recent series [2] removing xend config version from
>> the codebase.
>>
>> [1] https://www.redhat.com/archives/libvir-list/2015-November/msg01155.html
>> [2] https://www.redhat.com/archives/libvir-list/2015-December/msg00616.html
>>
>>
>>  src/xenconfig/xen_common.c                    | 25 +++++++++++----------
>>  tests/xlconfigdata/test-paravirt-maxvcpus.cfg | 13 +++++++++++
>>  tests/xlconfigdata/test-paravirt-maxvcpus.xml | 28 ++++++++++++++++++++++++
>>  tests/xlconfigtest.c                          |  1 +
>>  tests/xmconfigdata/test-paravirt-maxvcpus.cfg | 13 +++++++++++
>>  tests/xmconfigdata/test-paravirt-maxvcpus.xml | 31 +++++++++++++++++++++++++++
>>  tests/xmconfigdata/test-paravirt-vcpu.cfg     |  4 ++--
>>  tests/xmconfigtest.c                          |  1 +
>>  8 files changed, 101 insertions(+), 15 deletions(-)
> ACK

Thanks, pushed now.

Regards,
Jim

      parent reply	other threads:[~2015-12-19  1:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1450218051-25842-1-git-send-email-jfehlig@suse.com>
2015-12-16 10:11 ` [PATCH V2] Xen: support maxvcpus in xm and xl config Ian Campbell
2015-12-16 11:09   ` Ian Campbell
2015-12-18 11:47 ` [libvirt] " Michal Privoznik
     [not found] ` <5673F25B.70606@redhat.com>
2015-12-19  1:25   ` Jim Fehlig [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='5674B21D.8060702__37865.6091787436$1450488478$gmane$org@suse.com' \
    --to=jfehlig@suse.com \
    --cc=ian.campbell@citrix.com \
    --cc=libvir-list@redhat.com \
    --cc=mprivozn@redhat.com \
    --cc=xen-devel@lists.xen.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.