kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215459] VM freezes starting with kernel 5.15
Date: Tue, 11 Jan 2022 08:29:00 +0000	[thread overview]
Message-ID: <bug-215459-28872-Wk1EQCQEdY@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215459-28872@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=215459

--- Comment #11 from th3voic3@mailbox.org ---
(In reply to mlevitsk from comment #10)
> On Mon, 2022-01-10 at 09:30 +0000, bugzilla-daemon@bugzilla.kernel.org wrote:
> > https://bugzilla.kernel.org/show_bug.cgi?id=215459
> > 
> > --- Comment #9 from th3voic3@mailbox.org ---
> > I've compiled the 5.16 kernel now and so far it's looking very good. APICv
> > and
> > tdp_mmu are both enabled. Also thanks to dynamic PREEMPT I no longer need
> to
> > recompile to enable voluntary preemption to cut down my VMs boot time.
> > 
> Great to hear that.
>  
> I am just curious, with what PREEMPT setting, the boot is slow?
> With full preemption? I also noticed that long ago, before I joined redhat,
> back when I was just a VFIO fan, that booting with large amounts of ram
> (32 back then I think), forced preemption and passed-through GPU makes
> The VM hang for about like 1/2 of a minute before it shows the bios splash
> screen.
>  
> Best regards,
>       Maxim Levitsky

Yeah it used to be like that.
I just compared the two though (full vs voluntary PREEMPT) and it doesn't seem
to make a difference anymore. Full preemption is now just as fast as voluntary
preemption, so I'm just sticking with full preemption since it's my distros
default.

Best regards

Nico

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2022-01-11  8:29 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 11:03 [Bug 215459] New: VM freezes starting with kernel 5.15 bugzilla-daemon
2022-01-06 11:18 ` Maxim Levitsky
2022-01-06 11:18 ` [Bug 215459] " bugzilla-daemon
2022-01-06 13:12 ` bugzilla-daemon
2022-01-06 13:43   ` Maxim Levitsky
2022-01-06 13:43 ` bugzilla-daemon
2022-01-06 18:52 ` bugzilla-daemon
2022-01-06 20:42   ` Maxim Levitsky
2022-01-06 20:42 ` bugzilla-daemon
2022-01-06 21:12 ` bugzilla-daemon
2022-01-07  8:52 ` bugzilla-daemon
2022-01-07 10:08 ` bugzilla-daemon
2022-01-10  9:30 ` bugzilla-daemon
2022-01-10 22:29   ` Maxim Levitsky
2022-01-10 22:29 ` bugzilla-daemon
2022-01-11  8:29 ` bugzilla-daemon [this message]
2023-01-27 13:11 ` bugzilla-daemon

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=bug-215459-28872-Wk1EQCQEdY@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=kvm@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).