From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Nicholas Piggin <npiggin@gmail.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
"kvm-ppc@vger.kernel.org" <kvm-ppc@vger.kernel.org>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Cc: Darren Stevens <darren@stevens-zone.net>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
mad skateman <madskateman@gmail.com>,
Christian Zigotzky <info@xenosoft.de>
Subject: Re: [FSL P50x0] KVM HV doesn't work anymore
Date: Mon, 7 Jun 2021 09:21:58 +0200 [thread overview]
Message-ID: <b3821ab6-f3b4-ee51-93a2-064c09bc4278@xenosoft.de> (raw)
In-Reply-To: <f437d727-8bc7-6467-6134-4e84942628f1@xenosoft.de>
On 02 June 2021 at 01:26pm, Christian Zigotzky wrote:
> On 20 May 2021 at 01:07am, Nicholas Piggin wrote:
>> Hmm, okay that probably rules out those notifier changes then.
>> Can you remind me were you able to rule these out as suspects?
>>
>> 8f6cc75a97d1 powerpc: move norestart trap flag to bit 0
>> 8dc7f0229b78 powerpc: remove partial register save logic
>> c45ba4f44f6b powerpc: clean up do_page_fault
>> d738ee8d56de powerpc/64e/interrupt: handle bad_page_fault in C
>> ceff77efa4f8 powerpc/64e/interrupt: Use new interrupt context
>> tracking scheme
>> 097157e16cf8 powerpc/64e/interrupt: reconcile irq soft-mask state in C
>> 3db8aa10de9a powerpc/64e/interrupt: NMI save irq soft-mask state in C
>> 0c2472de23ae powerpc/64e/interrupt: use new interrupt return
>> dc6231821a14 powerpc/interrupt: update common interrupt code for
>> 4228b2c3d20e powerpc/64e/interrupt: always save nvgprs on interrupt
>> 5a5a893c4ad8 powerpc/syscall: switch user_exit_irqoff and
>> trace_hardirqs_off order
>>
>> Thanks,
>> Nick
> Hi Nick,
>
> I tested these commits above today and all works with -smp 4. [1]
>
> Smp 4 still doesn't work with the RC4 of kernel 5.13 on quad core
> e5500 CPUs with KVM HV. I use -smp 3 currently.
>
> What shall I test next?
>
> Thanks,
> Christian
>
> [1] https://forum.hyperion-entertainment.com/viewtopic.php?p=53367#p53367
Hi All,
I tested the RC5 of kernel 5.13 today. Unfortunately the KVM HV issue
still exists.
I also figured out, that '-smp 2' doesn't work either.
Summary:
-smp 1 -> works
-smp 2 -> doesn't work
-smp 3 -> works
-smp 4 -> doesn't work
Cheers,
Christian
next prev parent reply other threads:[~2021-06-07 7:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-14 8:10 [FSL P50x0] KVM HV doesn't work anymore Christian Zigotzky
2021-05-15 9:48 ` Christian Zigotzky
2021-05-15 10:08 ` Christophe Leroy
2021-05-15 13:46 ` Christian Zigotzky
2021-05-17 7:42 ` Nicholas Piggin
2021-05-17 9:42 ` Christian Zigotzky
2021-05-18 6:33 ` Christian Zigotzky
2021-05-19 7:57 ` Nicholas Piggin
2021-05-19 11:52 ` Christian Zigotzky
2021-05-19 23:07 ` Nicholas Piggin
2021-05-30 6:49 ` Christian Zigotzky
2021-06-02 11:26 ` Christian Zigotzky
2021-06-07 7:21 ` Christian Zigotzky [this message]
2021-06-11 2:24 ` Nicholas Piggin
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=b3821ab6-f3b4-ee51-93a2-064c09bc4278@xenosoft.de \
--to=chzigotzky@xenosoft.de \
--cc=christophe.leroy@csgroup.eu \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=kvm-ppc@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=npiggin@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 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).