All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Andrew Cooper <andrew.cooper3@citrix.com>,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	Jonathan Creekmore <jonathan.creekmore@gmail.com>
Cc: George Dunlap <george.dunlap@eu.citrix.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v3 2/5] build: Hook the schedulers into Kconfig
Date: Fri, 8 Jan 2016 16:59:15 +0100	[thread overview]
Message-ID: <1452268755.22760.49.camel@citrix.com> (raw)
In-Reply-To: <568FDBBA.8050103@citrix.com>


[-- Attachment #1.1: Type: text/plain, Size: 1311 bytes --]

On Fri, 2016-01-08 at 15:54 +0000, Andrew Cooper wrote:
> On 08/01/16 15:47, Konrad Rzeszutek Wilk wrote:
> > 
> > And the hypervisor did build with:
> > 
> > [konrad@char xen]$ nm --defined xen-syms |grep schedulers
> > ffff82d080290d58 D __end_schedulers_array
> > ffff82d080290d58 D __start_schedulers_array
> > 
> > :-)
> > 
> > Not exactly sure if there is some way to make us _not_ shoot
> > ourselves in the foot by mistake.
> > 
> > Perhaps the build should complain if the size of the
> > __schedulers_array is zero?
> 
> Hmm yes - an ASSERT() at the bottom of the linker file would be a
> very
> good defensive measure.
> 
+1

> A hypervisor without any schedulers compiled in will be rather sad.
> 
Well, it depends on how many pCPUs the host you want to run the
hypervisor on has: if it has 0 of them, no scheduler at all is the
perfect solution... not to mention that the combination of these things
(0 CPUs and no scheduling), would make a lot of issues just instantly
disappear! :-D

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)


[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2016-01-08 15:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-07 17:29 [PATCH v3 0/5] Allow schedulers to be selectable through Kconfig Jonathan Creekmore
2016-01-07 17:29 ` [PATCH v3 1/5] build: Env var to enable expert config options Jonathan Creekmore
2016-01-08 15:43   ` Konrad Rzeszutek Wilk
2016-01-07 17:29 ` [PATCH v3 2/5] build: Hook the schedulers into Kconfig Jonathan Creekmore
2016-01-08 15:47   ` Konrad Rzeszutek Wilk
2016-01-08 15:54     ` Andrew Cooper
2016-01-08 15:59       ` Dario Faggioli [this message]
2016-01-08 16:02       ` Jonathan Creekmore
2016-01-08 16:13         ` Juergen Gross
2016-01-08 16:30           ` Jonathan Creekmore
2016-01-08 16:49             ` Jan Beulich
2016-01-08 16:58               ` Doug Goldstein
2016-01-08 17:04                 ` Jonathan Creekmore
2016-01-08 17:13                   ` Andrew Cooper
2016-01-08 17:18                   ` Konrad Rzeszutek Wilk
2016-01-11  9:06                 ` Jan Beulich
2016-01-08 16:30           ` Jan Beulich
2016-01-07 17:29 ` [PATCH v3 3/5] build: Alloc space for sched list in the link file Jonathan Creekmore
2016-01-08 15:48   ` Konrad Rzeszutek Wilk
2016-01-07 17:29 ` [PATCH v3 4/5] sched: Register the schedulers into the list Jonathan Creekmore
2016-01-08 15:48   ` Konrad Rzeszutek Wilk
2016-01-07 17:29 ` [PATCH v3 5/5] sched: Use the auto-generated list of schedulers Jonathan Creekmore

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=1452268755.22760.49.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jonathan.creekmore@gmail.com \
    --cc=konrad.wilk@oracle.com \
    --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.