From: Gerd Hoffmann <kraxel@suse.de>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, Jan Beulich <jbeulich@novell.com>
Subject: Re: is_initial_xendomain()
Date: Fri, 18 Aug 2006 10:09:32 +0200 [thread overview]
Message-ID: <44E575BC.5080502@suse.de> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D572465@liverpoolst.ad.cl.cam.ac.uk>
Ian Pratt wrote:
>> #ifdef CONFIG_XEN_PRIVILEGED_GUEST
>> #define is_initial_xendomain() (xen_start_info->flags &
> SIF_INITDOMAIN)
>> #else
>> #define is_initial_xendomain() 0
>> #endif
>>
>> If that is acceptable, I'm ready to create a respective patch
>> (but I'd like to avoid spending time on it if there are objections).
>
> Personally, I'd like to see CONFIG_XEN_PRIVILEGED_GUEST disappear
> altogether. The code size saving is small, and most people use the -xen
> kernel rather than -xen0/-xenU anyway.
For development it's handy to have a separate xenU kernel, for both
build time and size. Most size savings come from dropping all the
drivers though, not CONFIG_XEN_PRIVILEGED_GUEST. And gcc should be
clever enougth to optimize away "if (0) { code block }", so you get the
size savings even with CONFIG_XEN_PRIVILEGED_GUEST being hidden in some
header file as listed above.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
http://www.suse.de/~kraxel/julika-dora.jpeg
next prev parent reply other threads:[~2006-08-18 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-18 7:56 is_initial_xendomain() Ian Pratt
2006-08-18 8:09 ` Gerd Hoffmann [this message]
2006-08-18 8:57 ` is_initial_xendomain() Keir Fraser
2006-08-18 12:15 ` is_initial_xendomain() Jan Beulich
2006-08-22 10:35 ` is_initial_xendomain() Ian Campbell
-- strict thread matches above, loose matches on Subject: below --
2006-08-18 7:12 is_initial_xendomain() Jan Beulich
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=44E575BC.5080502@suse.de \
--to=kraxel@suse.de \
--cc=jbeulich@novell.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.