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

Re: Xen C-state Issues

  • To: Elliott Mitchell <ehem+xen@xxxxxxx>
  • From: Jan Beulich <jbeulich@xxxxxxxx>
  • Date: Tue, 24 Aug 2021 08:14:41 +0200
  • 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-SenderADCheck; bh=SedVO7fKHJffm8XxMC1S+DrN/iYMpNZxWPJq3WwUt4k=; b=ISBKKIzOfPoJk/3FiHqBEmRMys5HJLH4C8U/YbjGY7KAOxKZvvisD16RKc6em7OCXYUiDREpcOERgySZ7pFnIclmXLYzveGR7M+zSwmSRgz2b2UPAPXHvLp4MJEZ+myeX3p4lhjIl7pk+/VJ7UaUFYnx5rm4LLQW9prsWlElHkLkgMyWG/1UPLNBFh3aMvHvmOC/5ThyENhtod7JZN9pPlcWR9tV9yin6Ak/7Ck+TKvi43u+i2CE6Eg73CJovDU0QuqTDgeGPtqno6y1DF+lp/NHpANAvNAZLl2jBqOMcRXt06AHNsMDtpW7XBLcIejC7Hq+BfLYe8azwA6lZIvHDw==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=mUa1Be5BEtNPhmWcSUwQBY1f5yd3vCk13v6PUZRsko82fJ63h8OpCJUHcU+s7lanJhfztbyTrHHXEN0ztksHGifTHi31jFzvJSeVTFiJytepOdz1LX9CSualVOnNqiCOxfEE0escXs/y6iOjkA8ukGTB1qBiCeZKX3jEGcKk07hyJKApLSw6g6JK2rAKcs6Bc/gOgjrszbwGh6NGQiYIFcquzylq7wgJh7EIsH8v4rITMIXhc+MOJqZ7uE/tJnd5vGnoUpqmMrQd0WIUOkX2vmVI1yvA9x64YYoSxAy3+EJRCpIoYuaR8T15ZXhSb9Lkb/2rl05LSDn4GZgwLrFTMw==
  • Authentication-results: lists.xenproject.org; dkim=none (message not signed) header.d=none;lists.xenproject.org; dmarc=none action=none header.from=suse.com;
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • Delivery-date: Tue, 24 Aug 2021 06:14:50 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On 24.08.2021 07:37, Elliott Mitchell wrote:
> On Mon, Aug 23, 2021 at 09:12:52AM +0200, Jan Beulich wrote:
>> On 21.08.2021 18:25, Elliott Mitchell wrote:
>>> ACPI C-state support might not see too much use, but it does see some.
>>> With Xen 4.11 and Linux kernel 4.19, I found higher C-states only got
>>> enabled for physical cores for which Domain 0 had a corresponding vCPU.
>>> On a machine where Domain 0 has 5 vCPUs, but 8 reported cores, the
>>> additional C-states would only be enabled on cores 0-4.
>>> This can be worked around by giving Domain 0 vCPUs equal to cores, but
>>> then offlining the extra vCPUs.  I'm guessing this is a bug with the
>>> Linux 4.19 xen_acpi_processor module.
>>> Appears Xen 4.14 doesn't work at all with Linux kernel 4.19's ACPI
>>> C-state support.  This combination is unable to enable higher C-states
>>> on any core.  Since Xen 4.14 and Linux 4.19 are *both* *presently*
>>> supported it seems patch(es) are needed somewhere for this combination.
>> Hmm, having had observed the same quite some time ago, I thought I had
>> dealt with these problems. Albeit surely not in Xen 4.11 or Linux 4.19.
>> Any chance you could check up-to-date versions of both Xen and Linux
>> (together)?
> I can believe you got this fixed, but the Linux fixes never got
> backported.
> Of the two, higher C-states working with Linux 4.19 and Xen 4.11, but
> not Linux 4.19 and Xen 4.14 is more concerning to me.

I'm afraid without you providing detail (full verbosity logs) and
ideally checking with 4.15 or yet better -unstable it's going to be
hard to judge whether that's a bug, and if so where it might sit.




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