From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Christian Zigotzky <chzigotzky@xenosoft.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>
Cc: "R.T.Dickinson" <rtd2@xtra.co.nz>,
hypexed@yahoo.com.au, mad skateman <madskateman@gmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [Linux PPC] KVM PR and KVM HV do not work if the kernel was compiled with PREEMPT
Date: Tue, 17 Feb 2026 14:33:01 +0530 [thread overview]
Message-ID: <709b864f-9daa-4a48-b3d6-39baedce63b2@linux.ibm.com> (raw)
In-Reply-To: <40154f6a-39da-959d-e039-5ab9ff62db3c@xenosoft.de>
On 2/17/26 2:22 PM, Christian Zigotzky wrote:
> Hi,
>
> Thank you for your patch. I tested the latest git kernel with your patch
> today. Unfortunately the system freezes while booting the VM with KVM HV.
>
> Cheers,
> Christian
>
>
Would it be possible to share the console log or boot log of KVM to the
point it freezes?
next prev parent reply other threads:[~2026-02-17 9:03 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-14 14:02 [Linux PPC] KVM PR and KVM HV do not work if the kernel was compiled with PREEMPT Christian Zigotzky
2026-02-17 5:02 ` Shrikanth Hegde
2026-02-17 8:52 ` Christian Zigotzky
2026-02-17 9:03 ` Shrikanth Hegde [this message]
2026-02-17 9:44 ` Christian Zigotzky
2026-02-17 10:17 ` Madhavan Srinivasan
2026-02-17 10:26 ` Christian Zigotzky
2026-02-17 11:34 ` Shrikanth Hegde
2026-02-21 5:30 ` Christian Zigotzky
2026-02-23 3:45 ` Shrikanth Hegde
2026-02-23 16:48 ` [Linux PPC] 7.0-rc1: e500_mmu.c:923:26: error: assignment to 'struct tlbe_priv *' from incompatible pointer type 'struct tlbe_ref *' Christian Zigotzky
2026-02-23 18:07 ` Christophe Leroy (CS GROUP)
2026-02-23 19:38 ` Christophe Leroy (CS GROUP)
2026-02-23 22:40 ` Kees Cook
2026-02-24 6:30 ` Christian Zigotzky
2026-02-24 7:18 ` Christophe Leroy (CS GROUP)
2026-02-25 5:54 ` [Linux PPC] Disable PREEMPT Christian Zigotzky
2026-02-25 6:23 ` Shrikanth Hegde
2026-02-25 7:16 ` Christophe Leroy (CS GROUP)
2026-02-25 11:36 ` Peter Zijlstra
2026-02-26 5:37 ` Christian Zigotzky
2026-02-26 13:24 ` Christophe Leroy (CS GROUP)
2026-09-03 9:53 ` Michal Suchánek
2026-09-03 10:56 ` Shrikanth Hegde
2026-09-03 11:25 ` Michal Suchánek
2026-09-03 11:31 ` Shrikanth Hegde
2026-09-03 11:40 ` Michal Suchánek
2026-09-03 12:04 ` Shrikanth Hegde
2026-09-03 12:25 ` Michal Suchánek
2026-09-03 12:36 ` Harsh Prateek Bora
2026-09-03 12:55 ` Michal Suchánek
2026-09-03 15:17 ` Amit Machhiwal
2026-09-03 13:28 ` Michal Suchánek
2026-09-04 7:39 ` Michal Suchánek
2026-09-03 17:22 ` Shrikanth Hegde
2026-09-04 7:35 ` Michal Suchánek
2026-09-04 9:04 ` Shrikanth Hegde
2026-09-10 8:59 ` Michal Suchánek
2026-09-10 10:41 ` Shrikanth Hegde
2026-09-10 11:29 ` Michal Suchánek
2026-09-10 12:16 ` Michal Suchánek
2026-09-11 17:09 ` Shrikanth Hegde
2026-09-04 8:55 ` Christian Zigotzky
2026-09-04 9:20 ` Christian Zigotzky
2026-09-04 9:24 ` Shrikanth Hegde
2026-09-04 9:34 ` Christian Zigotzky
2026-09-05 13:07 ` Christian Zigotzky
2026-09-07 8:50 ` Michal Suchánek
2026-09-07 11:32 ` Christian Zigotzky
2026-09-10 8:54 ` Michal Suchánek
2026-09-10 10:31 ` Michal Suchánek
2026-09-10 11:31 ` Michal Suchánek
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=709b864f-9daa-4a48-b3d6-39baedce63b2@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=chzigotzky@xenosoft.de \
--cc=hypexed@yahoo.com.au \
--cc=info@xenosoft.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=rtd2@xtra.co.nz \
/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.