From: Nicholas Piggin <npiggin@gmail.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>,
Christian Zigotzky <chzigotzky@xenosoft.de>,
"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, 17 May 2021 17:42:23 +1000 [thread overview]
Message-ID: <1621236734.xfc1uw04eb.astroid@bobo.none> (raw)
In-Reply-To: <199da427-9511-34fe-1a9e-08e24995ea85@xenosoft.de>
Excerpts from Christian Zigotzky's message of May 15, 2021 11:46 pm:
> On 15 May 2021 at 12:08pm Christophe Leroy wrote:
>>
>>
>> Le 15/05/2021 à 11:48, Christian Zigotzky a écrit :
>>> Hi All,
>>>
>>> I bisected today [1] and the bisecting itself was OK but the
>>> reverting of the bad commit doesn't solve the issue. Do you have an
>>> idea which commit could be resposible for this issue? Maybe the
>>> bisecting wasn't successful. I will look in the kernel git log. Maybe
>>> there is a commit that affected KVM HV on FSL P50x0 machines.
>>
>> If the uImage doesn't load, it may be because of the size of uImage.
>>
>> See https://github.com/linuxppc/issues/issues/208
>>
>> Is there a significant size difference with and without KVM HV ?
>>
>> Maybe you can try to remove another option to reduce the size of the
>> uImage.
> I tried it but it doesn't solve the issue. The uImage works without KVM
> HV in a virtual e5500 QEMU machine.
Any more progress with this? I would say that bisect might have just
been a bit unstable and maybe by chance some things did not crash so
it's pointing to the wrong patch.
Upstream merge of powerpc-5.13-1 was good and powerpc-5.13-2 was bad?
Between that looks like some KVM MMU rework. You could try the patch
before this one b1c5356e873c ("KVM: PPC: Convert to the gfn-based MMU
notifier callbacks"). That won't revert cleanly so just try run the
tree at that point. If it works, test the patch and see if it fails.
Thanks,
Nick
next prev parent reply other threads:[~2021-05-17 7:43 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 [this message]
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
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=1621236734.xfc1uw04eb.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=christophe.leroy@csgroup.eu \
--cc=chzigotzky@xenosoft.de \
--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=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).