All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: James McKenzie <james.mckenzie@bromium.com>,
	robin.randhawa@arm.com, Wei Liu <wei.liu2@citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Daniel Smith <dpsmith@apertussolutions.com>,
	Doug Goldstein <cardoe@cardoe.com>,
	Christopher Clark <christopher.w.clark@gmail.com>,
	Marek Marczykowski <marmarek@invisiblethingslab.com>,
	"Daniel P.Smith" <dpsmith.dev@gmail.com>,
	Lars Kurth <lars.kurth.xen@gmail.com>,
	Paul Durrant <paul.durrant@citrix.com>,
	committers@xenproject.org,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Stewart Hildebrand <Stewart.Hildebrand@dornerworks.com>,
	Xen-devel <xen-devel@lists.xen.org>
Subject: Re: Enhancing Xen's Kconfig infrastructure to support tailored solutions
Date: Fri, 15 Feb 2019 01:52:14 -0700	[thread overview]
Message-ID: <5C667DBE0200007800216E51@prv1-mh.provo.novell.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1902140938160.5641@sstabellini-ThinkPad-X260>

>>> On 14.02.19 at 19:32, <sstabellini@kernel.org> wrote:
> Do you have any other suggestions about things that could be removed to
> reach down to 100K LOC, in addition to what you have already written
> above (Intel/AMD, shadow)?

If you mean ones we already have Kconfig options for, then you
could drop TBOOT, which in turn drops CRYPTO, which together
is about 3k LOC. Turning off XENOPROF would yield another 2k.
I assume you've already restricted yourself to just the null
scheduler? But that's about it, I think, without actual code (or at
least Kconfig) changes.

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  parent reply	other threads:[~2019-02-15  8:52 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-13  2:34 Enhancing Xen's Kconfig infrastructure to support tailored solutions Daniel P. Smith
2019-02-13 11:13 ` Jan Beulich
2019-02-13 18:25 ` Wei Liu
2019-02-13 19:11   ` Stefano Stabellini
2019-02-14  9:53     ` Jan Beulich
2019-02-14 18:32       ` Stefano Stabellini
2019-02-14 18:57         ` Andrew Cooper
2019-02-15  8:43           ` Jan Beulich
2019-02-14 21:03         ` Lars Kurth
2019-02-15 11:08           ` Wei Liu
2019-02-15 19:08             ` Stefano Stabellini
2019-02-18 11:12               ` Wei Liu
2019-02-18 11:17                 ` Lars Kurth
2019-02-18 11:23                   ` Wei Liu
2019-02-18 11:30                     ` George Dunlap
2019-02-18 11:53                       ` Lars Kurth
2019-02-18 11:57                         ` Wei Liu
2019-02-18 12:00                           ` Lars Kurth
2019-02-18 12:01                           ` Andrew Cooper
2019-02-18 12:11                             ` Lars Kurth
2019-02-18 12:11                             ` George Dunlap
2019-02-18 12:16                               ` George Dunlap
2019-02-18 12:54                                 ` Lars Kurth
2019-02-19 19:13                                   ` Stefano Stabellini
2019-02-19 21:05                                     ` P S
2019-02-15  8:52         ` Jan Beulich [this message]
2019-02-15 17:27           ` Stefano Stabellini
2019-02-15 10:58         ` Wei Liu
2019-02-14 18:52       ` Andrew Cooper
2019-02-15  9:35     ` George Dunlap
2019-02-15 11:10       ` Lars Kurth
2019-02-15 17:36       ` Stefano Stabellini
2019-02-15 17:55         ` George Dunlap
2019-02-15 18:27           ` Stefano Stabellini
2019-02-24 14:52       ` Daniel P. Smith

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=5C667DBE0200007800216E51@prv1-mh.provo.novell.com \
    --to=jbeulich@suse.com \
    --cc=Stewart.Hildebrand@dornerworks.com \
    --cc=cardoe@cardoe.com \
    --cc=christopher.w.clark@gmail.com \
    --cc=committers@xenproject.org \
    --cc=dpsmith.dev@gmail.com \
    --cc=dpsmith@apertussolutions.com \
    --cc=james.mckenzie@bromium.com \
    --cc=jun.nakajima@intel.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=marmarek@invisiblethingslab.com \
    --cc=paul.durrant@citrix.com \
    --cc=robin.randhawa@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=wei.liu2@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 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.