All of lore.kernel.org
 help / color / mirror / Atom feed
From: "André Przywara" <andre.przywara@amd.com>
To: George Dunlap <george.dunlap@eu.citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH] Documentation: Include cpupool example in install
Date: Tue, 15 Feb 2011 01:28:11 +0100	[thread overview]
Message-ID: <4D59C89B.6060207@amd.com> (raw)
In-Reply-To: <e66f078e198dde642fd3.1297699182@elijah>

Am 14.02.2011 16:59, schrieb George Dunlap:
> xl cpupool-create at the moment requires a config file.  Make
> sure to include the example config file in the install.
Good point. Btw: When I did some experiments with cpupools, I couldn't 
create the cpupool config file on the fly and pipe it to the xl 
cpupool-create command, as it:
a) explicitly checks for a regular file to be named (and doesn't handle 
'-' or can cope with /dev/stdin)
b) stats the file to learn the file size (requiring this to be a 
seekable file, that's why check a)

These are restrictions which apply to guest config files, too, as they 
use the same functionality.
Is this just a limit in the implementation or is the requirement for a 
regular on-disk file there for a reason?
I could easily create a patch to do away with these restrictions (after 
the release), are there any arguments against this?

Regards,
Andre.

--
Andre Przywara
AMD-Operating System Research Center (OSRC), Dresden, Germany

  reply	other threads:[~2011-02-15  0:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-14 15:59 [PATCH] Documentation: Include cpupool example in install George Dunlap
2011-02-15  0:28 ` André Przywara [this message]
2011-02-15 15:14   ` Ian Jackson
2011-02-15 19:39 ` Ian Jackson

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=4D59C89B.6060207@amd.com \
    --to=andre.przywara@amd.com \
    --cc=george.dunlap@eu.citrix.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.