xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@citrix.com>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
	George Dunlap <george.dunlap@eu.citrix.com>
Cc: Stefano Stabellini <stefano.stabellini@citrix.com>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH 5/5] raisin: Add XEN_CONFIG_EXTRA to config file
Date: Mon, 19 Oct 2015 10:24:06 +0100	[thread overview]
Message-ID: <5624B6B6.4020409@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1510161450470.27957@kaball.uk.xensource.com>

On 16/10/15 14:53, Stefano Stabellini wrote:
> On Wed, 14 Oct 2015, George Dunlap wrote:
>> Allowing the user to enable or disable specific functionality, such as
>> stubdoms.
>>
>> Signed-off-by: George Dunlap <george.dunlap@eu.citrix.com>
> 
> I don't like this very much: if we want to disable stubdoms by default
> with all configs, then I would prefer to simply add --disable-stubdom to
> components/xen without introducing XEN_CONFIG_EXTRA.
> 
> Otherwise if we want to give users the chance to add an extra config
> option, I would introduce a generic way to do that, so that people can
> use it with any components they want, QEMU, libvirt, etc.

You did notice that this config option is disabled by default, right?  I
added the line commented-out as an example of the sort of thing you
might want to do.

I don't think we want to disable stubdoms by default across the board.

I wouldn't object to adding empty config variables to the other
components; I just don't have a good way to test them at the moment.

 -George

  reply	other threads:[~2015-10-19  9:24 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 16:21 [PATCH 0/5] raisin: Miscelaneous improvements George Dunlap
2015-10-14 16:21 ` [PATCH 1/5] raisin: Handle aliases for packages, add pciutils-dev / libpci-dev alias George Dunlap
2015-10-16 13:37   ` Stefano Stabellini
2015-10-19  9:52     ` George Dunlap
2015-10-14 16:21 ` [PATCH 2/5] raisin: Detect systemd George Dunlap
2015-10-14 16:34   ` George Dunlap
2015-10-16 13:41     ` Stefano Stabellini
2015-10-19  9:54       ` George Dunlap
2015-10-19 11:09         ` Stefano Stabellini
2015-10-16 13:39   ` Stefano Stabellini
2015-10-16 14:02     ` Ian Campbell
2015-10-16 14:04       ` Stefano Stabellini
2015-10-19 10:01         ` George Dunlap
2015-10-19 11:15           ` Stefano Stabellini
2015-10-14 16:21 ` [PATCH 3/5] raisin: Allow iasl to alias acpica-tools, unify Fedora and CentOS deps for xen George Dunlap
2015-10-16 13:42   ` Stefano Stabellini
2015-10-14 16:21 ` [PATCH 4/5] raisin: Change update/release parsing OSes George Dunlap
2015-10-16 13:49   ` Stefano Stabellini
2015-10-19  9:16     ` George Dunlap
2015-10-19 11:26       ` Stefano Stabellini
2015-10-19 11:39         ` George Dunlap
2015-10-14 16:21 ` [PATCH 5/5] raisin: Add XEN_CONFIG_EXTRA to config file George Dunlap
2015-10-16 13:53   ` Stefano Stabellini
2015-10-19  9:24     ` George Dunlap [this message]
2015-10-19 11:37       ` Stefano Stabellini
2015-10-19 11:42         ` George Dunlap
2015-10-19 11:49           ` Stefano Stabellini

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=5624B6B6.4020409@citrix.com \
    --to=george.dunlap@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=stefano.stabellini@eu.citrix.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 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).