From: Sean Christopherson <seanjc@google.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: Bagas Sanjaya <bagasdotme@gmail.com>,
linux-kernel@vger.kernel.org,
Linux Regressions <regressions@lists.linux.dev>,
Linux KVM <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Tony Lindgren <tony@atomide.com>
Subject: Re: Linux 6.5 speed regression, boot VERY slow with anything systemd related
Date: Tue, 29 Aug 2023 08:42:04 -0700 [thread overview]
Message-ID: <ZO4RzCr/Ugwi70bZ@google.com> (raw)
In-Reply-To: <ZO4JCfnzRRL1RIZt@torres.zugschlus.de>
On Tue, Aug 29, 2023, Marc Haber wrote:
> On Tue, Aug 29, 2023 at 07:53:45AM -0700, Sean Christopherson wrote:
> > What is different between the bad host(s) and the good host(s)? E.g. kernel, QEMU,
>
> The bad host is an APU ("AMD GX-412TC SOC") with 4 GB of RAM, one of the
> good hosts is a "Xeon(R) CPU E3-1246 v3" with 32 GB of RAM.
I don't expect it to help, but can you try booting the bad host with
"spec_rstack_overflow=off"?
> system configuration is from the same ansible playbook, but of course there
> are differences.
Can you capture the QEMU command lines for the good and bad hosts? KVM doesn't
get directly involved in serial port emulation; if the blamed commit in 6.5 is
triggering unexpected behavior then QEMU is a better starting point than KVM.
next prev parent reply other threads:[~2023-08-29 15:42 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:35 Linux 6.5 speed regression, boot VERY slow with anything systemd related Marc Haber
2023-08-29 8:17 ` Bagas Sanjaya
2023-08-29 13:00 ` Marc Haber
2023-08-29 14:53 ` Sean Christopherson
2023-08-29 15:04 ` Marc Haber
2023-08-29 15:42 ` Sean Christopherson [this message]
2023-08-29 16:09 ` Marc Haber
2023-08-29 17:14 ` Sean Christopherson
2023-08-29 20:00 ` Marc Haber
2023-08-31 22:07 ` Sean Christopherson
2023-09-01 12:24 ` Tony Lindgren
2023-09-06 14:41 ` Marc Haber
2023-09-06 15:21 ` Tony Lindgren
2023-09-07 10:14 ` Marc Haber
2023-09-07 10:51 ` Tony Lindgren
2023-09-08 4:41 ` Tony Lindgren
2023-09-09 20:08 ` Marc Haber
2023-09-11 12:53 ` Tony Lindgren
2023-09-12 6:53 ` Marc Haber
2023-09-06 15:26 ` Tony Lindgren
2023-09-06 20:18 ` Marc Haber
2023-08-30 6:44 ` Marc Haber
2023-08-29 15:24 ` Marc Haber
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=ZO4RzCr/Ugwi70bZ@google.com \
--to=seanjc@google.com \
--cc=bagasdotme@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
--cc=pbonzini@redhat.com \
--cc=regressions@lists.linux.dev \
--cc=tony@atomide.com \
/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.