[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2] firmware/shim: UNSUPPORTED=n
- To: Jan Beulich <jbeulich@xxxxxxxx>
- From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
- Date: Wed, 26 May 2021 10:27:27 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9ANPmPHPRboAcTnkBdlnMdcKLJEVmTCBN0wk/OrYMX0=; b=AH7XWmBn0KbfWsjMtdfW6tUAAW4SiDXbN5UsKldAQnQFvaE3UNbcdtQv9Zz9dapa1JWRtu9GvlyaTkGhSgtOH+apJ5/SbIW6uJmEBVTpWte75KJNLLyyFrTGHnnRldo8OzZbvG1+FtiE3po5SDoCHdj+nSkIHmff0elPh6LigDP9COatkZCbJwdMaF1Qr6/mk6NugbheOOa/ZhdtQKoeoN0+TJiOhf0S90qJhUMwtScDa//2I6e86kPZxxSE/yxy/K+S5me7lCgtQbksI+q+NN/8mmeLlmnjZ1s3ilwNK+8guoWDRQnKGL7ApHTyMbA43+YeIC4q7W5A/jVrCFFoxg==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZcteRxCq5hxo3kCyCVsSPme5Zaem37qLMrQMKZmgcR/H+tFOhxAx0DD74eLFIajlnaS0cBEgGt1IUCsedmTkgWsFgOvI7Ic9fQKDSiP2HAAOt+slUECKTrl+uxHOdahyu48kMNqEWIor19l68hnL3vrrsMWTZpYCTwR57NOnki+DIVU058STv7KOKiEf1ZztObdY9hbktjEbB7MdiAqSQe5d3RIeStg1CEEDLkrY2TGZa+i6JC2qwtyF5Br7bjLaDxly8pvibOko6B3RO72NaNh0QPVkkeb91ilU/z0cXNKzRNnBc69e7Ac2sjUOi1EaYpH9dyVVzXPoxWxpFkTEqA==
- Authentication-results: esa1.hc3370-68.iphmx.com; dkim=pass (signature verified) header.i=@citrix.onmicrosoft.com
- Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Wei Liu <wl@xxxxxxx>, George Dunlap <george.dunlap@xxxxxxxxxx>, Dario Faggioli <dfaggioli@xxxxxxxx>
- Delivery-date: Wed, 26 May 2021 08:27:43 +0000
- Ironport-hdrordr: A9a23:WhXEZ6iD15l1HIgAWsx/2FcqF3BQX9x13DAbv31ZSRFFG/FwyP rAoB1L73PJYWgqNU3I+ergBEGBKUmskqKdxbNhR4tKOzOWxVdATbsSlrcKpgePJ8SQzJ8+6U 4NSdkaNDS0NykHsS+Y2njJLz9D+qj/zEnAv463pB0MPGIaGZ2IrT0JcjpzencGNTWubqBJcq Z0iPA3wwZJLh8sH7qG7zQ+LqT+T7KhruOoXTc2QzocrCWehzKh77D3VzKC2A0Fbj9JybA+tU DYjg3Q/MyYwrGG4y6Z81WWw4VdmdPnxNcGLteLkNIpJjLljRvtTJh9WoeFoCs+rIiUmRcXee H30lUd1vlImjbsljnfm2qo5+Cg6kdh15ba8y7avZO5yvaJAw7TYqF69PFkmhiw0TtqgDgz6t MM44o136Aney8opx6Nk+QgYSsa3nZckUBS5NL7sEYvJrf2SIUh57D3r3klXavpIkrBmcka+b 5Vfb7hDbBtAAqnU0w=
- Ironport-sdr: vNrsMMYosXSQaAOWmuugwV85jqyjm8YIygs891IubqenHmPBnLsJFgF1KMluCxduRjUXKA9jAJ PC0s/u9wlKdaEf9BgW824FmXiMHOuALPok3+ApCWrNRBBABlF3gx4clJcH8p0T53yWFaJWqsWC nvPTQHW8ApoEdCdh6H42BSOC5/5ZOrXHUmBuFUSKsY3OrCu6fb1WgA2t1a4oyKPTv2uOFrOyFM ZrxrEi8vYkWXzpIsqTxZ8/GJvFQGC/nk0VYTcn4rWMWsEuhMUlz2llXghxMYbm3kWzhZtUNYpN Xpw=
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
On Wed, May 26, 2021 at 09:37:37AM +0200, Jan Beulich wrote:
> We shouldn't default to include any unsupported code in the shim. Mark
> the setting as off, replacing the ARGO specification. This points out
> anomalies with the scheduler configuration: Unsupported schedulers
> better don't default to Y in release builds (like is already the case
> for ARINC653). Without at least the SCHED_NULL adjustments, the shim
> would suddenly build with RTDS as its default scheduler.
>
> As a result, the SCHED_NULL setting can also be dropped from defconfig.
>
> Clearly with the shim defaulting to it, SCHED_NULL must be supported at
> least there.
>
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
> Acked-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
> ---
> v2: Also drop SCHED_NULL setting from defconfig. Make SCHED_NULL the
> default when PV_SHIM_EXCLUSIVE.
> ---
> I'm certainly open to consider alterations on the sched/Kconfig
> adjustments, but _something_ needs to be done there. In particular I
> was puzzled to find the NULL scheduler marked unsupported. Clearly with
> the shim defaulting to it, it must be supported at least there.
>
> In a PV_SHIM (but perhaps !PV_SHIM_EXCLUSIVE) build with the build-time
> default not being SCHED_NULL, when actually running as shim I can't seem
> to see how the null scheduler would get chosen as the default
> nevertheless. Shouldn't this happen (in the absence of a command line
> override)?
I wondered the same yesterday and got to the conclusion that it's
then the duty of the user to add pvshim_extra="sched=null" to the
config file.
I think it would indeed be useful to select the null scheduler at
runtime if booting in shim mode and null is present, but then we would
be ignoring the default scheduler selection made in Kconfig, which
could be confusing.
It's also confusing that the scheduler that gets set as the default
when shim exclusive is selected is not available to enable/disable:
[*] Credit scheduler support (NEW)
[*] Credit2 scheduler support (NEW)
Default Scheduler? (Null Scheduler) --->
Thanks, Roger.
|
