From: George Dunlap <george.dunlap@eu.citrix.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Konrad Rzeszutek Wilk <konrad@kernel.org>,
xen-devel@lists.xensource.com,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: [PATCH 2/2] expert_mode: Add a new configuration option for expert users.
Date: Wed, 17 Jul 2013 12:03:18 +0100 [thread overview]
Message-ID: <51E679F6.6040305@eu.citrix.com> (raw)
In-Reply-To: <20966.30808.647898.994541@mariner.uk.xensource.com>
On 17/07/13 11:56, Ian Jackson wrote:
> Ian Campbell writes ("Re: [Xen-devel] [PATCH 2/2] expert_mode: Add a new configuration option for expert users."):
>> On Fri, 2013-07-12 at 14:08 -0400, Konrad Rzeszutek Wilk wrote:
>>> This could also be called 'seatbelt' option.
>>>
>>> libxl has a variety of checks where it will fail out an operation
>>> unless the user has provided an --force (or --ignore) parameter.
>>> Currently one such check is for the 'vcpu-set' command which
>>> will error out if the count of virtual cpus is greater than the
>>> physical cpus. This parameter will ignore such checks and allow
>>> the user to do the operations without the need for override flags.
>> Does this overlap somewhat with various commands which individually
>> take a -f(orce) option?
> Clearly it should disable all of those -f's too.
>
>>> +=item B<expert_mode=BOOLEAN>
>>> +
>>> +Do not act on host performed checks that might lead to performance
>>> +degradations. Currently checks are made for following operations:
>>> + - C<vcpu-set> - if the number of VCPUs set for a guest is higher than the
>>> + physical count the operation will error out.
> I don't think this is a very coherent specification. Surely it should
> override "all -f options" or something similar.
I think that makes sense for some but not all. For example, for "xl
shutdown", -f means "send an ACPI event if no PV drivers are detected".
I don't think we'd want to change that behavior with such a switch.
(Arguably -f was the wrong option to use for that in the first place,
but it's a bit late for that now.)
-George.
next prev parent reply other threads:[~2013-07-17 11:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 18:08 [PATCH] xl.conf defaults changes for Xen 4.4. (v1) Konrad Rzeszutek Wilk
2013-07-12 18:08 ` [PATCH 1/2] claim: By default enable it Konrad Rzeszutek Wilk
2013-07-16 9:03 ` Ian Campbell
2013-07-12 18:08 ` [PATCH 2/2] expert_mode: Add a new configuration option for expert users Konrad Rzeszutek Wilk
2013-07-16 9:04 ` Ian Campbell
2013-07-16 15:21 ` Konrad Rzeszutek Wilk
2013-07-17 10:56 ` Ian Jackson
2013-07-17 11:03 ` George Dunlap [this message]
2013-07-17 11:12 ` Ian Campbell
2013-07-17 11:13 ` George Dunlap
2013-07-17 17:17 ` Konrad Rzeszutek Wilk
2013-07-18 11:08 ` George Dunlap
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=51E679F6.6040305@eu.citrix.com \
--to=george.dunlap@eu.citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=konrad@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).