From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E4F6EE14A5 for ; Wed, 6 Sep 2023 15:26:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241357AbjIFP0W (ORCPT ); Wed, 6 Sep 2023 11:26:22 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:47204 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230465AbjIFP0V (ORCPT ); Wed, 6 Sep 2023 11:26:21 -0400 Received: from muru.com (muru.com [72.249.23.125]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 42AA9E5C; Wed, 6 Sep 2023 08:26:18 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 897528050; Wed, 6 Sep 2023 15:26:17 +0000 (UTC) Date: Wed, 6 Sep 2023 18:26:16 +0300 From: Tony Lindgren To: Marc Haber Cc: Sean Christopherson , Bagas Sanjaya , linux-kernel@vger.kernel.org, Linux Regressions , Linux KVM , Paolo Bonzini Subject: Re: Linux 6.5 speed regression, boot VERY slow with anything systemd related Message-ID: <20230906152616.GE11676@atomide.com> References: <20230901122431.GU11676@atomide.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Marc Haber [230906 14:41]: > With my tools I have found out that it really seems to be related to the > CPU of the host. I have changed my VM definition to "copy host CPU > configuration to VM" in libvirt and have moved this very VM (image and > settings) to hosts with a "Ryzen 5 Pro 4650G" and to an "Intel Xeon > E3-1246" where they work flawlessly, while on both APUs I have available > ("AMD G-T40E" and "AMD GX-412TC SOC") the regression in 6.5 shows. And > if I boot other VMs on the APUs with 6.5 the issue comes up. It is a > clear regression since going back to 4.6's serial code solves the issue > on the APUs. Not sure why the CPU matters here.. One thing to check is if you have these in your .config: CONFIG_SERIAL_CORE=y CONFIG_SERIAL_CORE_CONSOLE=y Or do you maybe have CONFIG_SERIAL_CORE=m as loadable module? If you have CONFIG_SERIAL_CORE=m, maybe you need to modprobe serial_base if you have some minimal rootfs that does not automatically do it for you. Regards, Tony