All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir.fraser@eu.citrix.com>
To: Michal Novotny <minovotn@redhat.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Question about vcpu_avail
Date: Tue, 24 Nov 2009 16:28:01 +0000	[thread overview]
Message-ID: <C731BA11.1735%keir.fraser@eu.citrix.com> (raw)
In-Reply-To: <4B0BFB4C.50102@redhat.com>

On 24/11/2009 15:27, "Michal Novotny" <minovotn@redhat.com> wrote:

>> If you add new config fields to xend, then libvirt callers are going to need
>> to be modified to expose them to users, aren't they (e.g., in a GUI or
>> whatever)? If the callers need modifying anyway, then they can just be
>> modified in a similar way to what I propose for xm, and deconstruct into the
>> config primitives that xend already understands.
> 
> Well, the thing is whether it isn't better to be added to Xend itself
> instead of xm ? This could avoid further modifications. Maybe the
> callers have to be modified a little but I am not sure.

Let me put it this way then: xend already allows you to express what you
want to be able to do, through vcpus/vcpu_avail. Prettifying that for end
users is an issue of UI design.

 -- Keir

      reply	other threads:[~2009-11-24 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 15:02 Question about vcpu_avail Michal Novotny
2009-11-23 15:28 ` Keir Fraser
2009-11-24 11:27   ` Michal Novotny
2009-11-24 14:24     ` Keir Fraser
2009-11-24 14:51       ` Michal Novotny
2009-11-24 15:05         ` Keir Fraser
2009-11-24 15:08           ` Michal Novotny
2009-11-24 15:20             ` Keir Fraser
2009-11-24 15:27               ` Michal Novotny
2009-11-24 16:28                 ` Keir Fraser [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=C731BA11.1735%keir.fraser@eu.citrix.com \
    --to=keir.fraser@eu.citrix.com \
    --cc=minovotn@redhat.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.