From: Julien Grall <julien@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
Scott Davis <scottwd@gmail.com>,
xen-devel@lists.xenproject.org
Cc: Scott Davis <scott.davis@starlab.io>,
Ian Jackson <iwj@xenproject.org>, Wei Liu <wl@xen.org>,
George Dunlap <george.dunlap@citrix.com>,
Nick Rosbrook <rosbrookn@ainfosec.com>,
Anthony PERARD <anthony.perard@citrix.com>,
Juergen Gross <jgross@suse.com>
Subject: Re: [PATCH] tools/xl: Add stubdomain_cmdline option to xl.cfg
Date: Wed, 21 Jul 2021 10:11:55 +0100 [thread overview]
Message-ID: <c4d5cb39-420b-a9e3-0b9c-bee7e5d41a78@xen.org> (raw)
In-Reply-To: <56f86674-7a6c-3f3a-40e9-dcb35cddbb88@citrix.com>
Hi,
On 21/07/2021 10:06, Andrew Cooper wrote:
> On 21/07/2021 09:21, Julien Grall wrote:
>> Hi Scott,
>>
>> On 20/07/2021 18:56, Scott Davis wrote:
>>> This adds an option to the xl domain configuration file syntax for
>>> specifying
>>> a kernel command line for device-model stubdomains. It is intended
>>> for use with
>>> Linux-based stubdomains.
>>
>> May I ask why embedding the command line in the kernel would not be a
>> solution? Do you expect it to change from stubdom to stubdom?
>
> Why should users of stubdoms be forced to embed command line options?
> Especially when its not the normal way of working?
I didn't suggest they should be forced. I was more interested to know
the setup because I was expecting stubdomain to use a very tailored kernel.
>
> They shouldn't, and this alone is enough justification for the change.
Everyone has a different perspective. I don't see the problem of asking
the question... Maybe I should have add "OOI" to make clear with wasn't
a complain.
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2021-07-21 9:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-20 17:56 [PATCH] tools/xl: Add stubdomain_cmdline option to xl.cfg Scott Davis
2021-07-21 8:21 ` Julien Grall
2021-07-21 9:00 ` Juergen Gross
2021-07-21 9:06 ` Andrew Cooper
2021-07-21 9:11 ` Julien Grall [this message]
2021-07-21 9:57 ` Ian Jackson
2021-07-21 22:30 ` Scott Davis
2021-07-21 12:42 ` Jason Andryuk
2021-07-21 12:50 ` Ian Jackson
2021-07-21 13:26 ` Jason Andryuk
2021-07-21 14:03 ` 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=c4d5cb39-420b-a9e3-0b9c-bee7e5d41a78@xen.org \
--to=julien@xen.org \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@citrix.com \
--cc=george.dunlap@citrix.com \
--cc=iwj@xenproject.org \
--cc=jgross@suse.com \
--cc=rosbrookn@ainfosec.com \
--cc=scott.davis@starlab.io \
--cc=scottwd@gmail.com \
--cc=wl@xen.org \
--cc=xen-devel@lists.xenproject.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.