[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Kconfig: defaults for UNSUPPORTED


  • To: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 1 Mar 2022 09:24:20 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.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-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=9XJQN78ib1MVXdwfiKUllDBBg5cOZ43xtTpNhJqfgz8=; b=RilcchYAZLDZ6w5zkGzKcUW7XVN+AyuA2mwvhVC0wVLwiaWRv4+LnGGClVmoAvF8WV/i5C0pcljW+qBLTwsSRCejbwHgjQpkTqkaJD6hHMnJKj0T3ypmky4+yVWNAi2jJT9qTdbhwqMIc/pmHtCEvbMU2X+I3RSW+QF4Lb9wGND1kzE7/n+Cpd9NM3VC381OZM+YPwI2zf+ROUdzQE9ucTUL8nd7gR7QytYbjpsV4y3fGpI/QuP8f26oV0VRJXFQWo5ZLh2ERxnQG4rlZWaSRLoernxOcP4AaaVPq/fxQUhtGOuCOayjhptrFZegCZrXtbpypCyiEJzcecaxBftekA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=UQTbS3IwUmDf7klkO5J9m2mCq5QSsiZzoYG+8m5zx9nzlB0UH+VndbGkbGRare+HQ/6jLraJwPt/bbwtm7UYImZxWtV6hESGSGXRLFV5Kc9blNm6MhbGsnGVVyKZ1whKHk7FIF63ah7oUdr9hAcARH7m9LjdpCYbpR4w6SbpdCWfCVdJQwL5Xs8w/3EhYrPMyES5j5pGOF62pa81TpSLMiqtAZB7uqF46N/BCAVdo/9wQTncyb9U+LGbqvATWAhLT1OvELSVS2F+TNYZjlUzIw6y/nif0Q/MHV9TRPUPUH3rYzyRSgrdbeIWhZyAqQQk6Sdt2J3RZmNiFZttuhKnPA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
  • Delivery-date: Tue, 01 Mar 2022 08:24:34 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

Hello,

when commit d96e5e6c1214 added UNSUPPORTED, it left x86'es TBOOT
default untouched. This means we default-enable an unsupported
setting, which doesn't look to be what's generally wanted. I can
see defaulting to DEBUG as reasonable, and SCHED_NULL's defaulting
to enabled when PV_SHIM can imo also be justified (there it's
rather that UNSUPPORTED is inapplicable for the shim case, and the
adjustment was also done subsequent to the named commit).

Shouldn't we therefore have a rule of thumb that UNSUPPORTED
entries only ever have no "default" (implying "n") or default to
no more than DEBUG?

Thanks for opinions,
Jan




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.