From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Christian Zigotzky" <chzigotzky@xenosoft.de>,
<qemu-ppc@nongnu.org>, "mad skateman" <madskateman@gmail.com>,
"R.T.Dickinson" <rtd2@xtra.co.nz>,
"Christian Zigotzky" <info@xenosoft.de>,
"linuxppc-dev" <linuxppc-dev@lists.ozlabs.org>,
"Matthew Leaman" <matthew@a-eon.biz>,
"Darren Stevens" <darren@stevens-zone.net>
Subject: Re: [RFC PATCH] Disable Book-E KVM support?
Date: Tue, 06 Dec 2022 17:11:00 +1000 [thread overview]
Message-ID: <COUJPOA8V93O.3EB95FEH792PM@bobo> (raw)
In-Reply-To: <fc43f9eb-a60f-5c4a-a694-83029234a9c4@xenosoft.de>
On Sun Dec 4, 2022 at 9:33 PM AEST, Christian Zigotzky wrote:
> Hi All,
>
> We regularly use QEMU with KVM HV on our A-EON AmigaOne X5000 machines
> (book3e). It works fast and without any problems.
>
> Screenshot tour of QEMU/KVM HV on our AmigaOnes:
>
> - https://i.ibb.co/m4vgwNT/Kernel-6-1-rc3-Power-PC.png
> - https://i.ibb.co/Fwdjf7Z/Kernel-6-0-rc6-Power-PC.png
> - https://i.ibb.co/LYnJGdF/Kernel-5-19-rc5-Power-PC-2.png
> - https://i.ibb.co/vz1Wm5z/QEMU-with-9p-and-USB-sound.png
> - https://i.ibb.co/ScMjtp7/Kernel-5-17-alpha5-Power-PC.png
> - https://i.ibb.co/LQryFcK/Kernel-5-17-alpha4-Power-PC.png
> - https://i.ibb.co/kKLx9mf/Kernel-5-10-89-Power-PC.png
> - https://i.ibb.co/LRG1RDV/Kernel-5-10-89-Power-PC-2.png
> - https://i.ibb.co/NCFqY0k/QEMU-USB-Audio-on-Void-PPC.png
> - https://i.ibb.co/N1vL5Kd/Kernel-5-16-alpha3-Power-PC.png
> - https://i.ibb.co/SwjTyJk/Kernel-5-16-alpha1-Power-PC.png
> - https://i.ibb.co/LkpWNPx/Kernel-5-15-rc5-Power-PC.png
> - https://i.ibb.co/F8q1jDR/Kernel-5-15-rc4-Power-PC.png
> - https://i.ibb.co/zZxrbhV/Kernel-5-15-alpha6-Power-PC.png
> -
> https://i.pinimg.com/originals/a8/8b/42/a88b422870201887fc01ef44ddc1a235.png
> -
> https://i.pinimg.com/originals/57/d9/83/57d98324cd055b7ae00a87ad5a45a42f.png
> -
> https://i.pinimg.com/originals/f2/a5/e3/f2a5e34e2015381b0cb87cc51232a8bc.png
> -
> https://i.pinimg.com/originals/c5/0d/85/c50d85d7e8f20b4caa1a439faf751964.png
> -
> https://i.pinimg.com/originals/6e/3b/59/6e3b59fe10276c5644b15622a81f43f1.png
>
> We solved some issues:
>
> - https://forum.hyperion-entertainment.com/viewtopic.php?p=54357#p54357
> - https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-November/236307.html
> - https://lists.ozlabs.org/pipermail/linuxppc-dev/2022-September/249021.html
> - https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-May/229103.html
> - https://lists.ozlabs.org/pipermail/linuxppc-dev/2021-January/223342.html
> - https://lists.ozlabs.org/pipermail/linuxppc-dev/2020-August/216379.html
> -
> https://forum.hyperion-entertainment.com/viewtopic.php?f=58&t=4655&p=53393&hilit=KVM#p53393
> - https://forum.hyperion-entertainment.com/viewtopic.php?p=53209#p53209
>
> Please, do not remove KVM support from Book3e because it works without
> any problems and fast. We need it for our work.
Hey Christian,
I knew you do a lot of testing with BookE, I didn't know you used KVM
there. Good to know it's working for you. In that case I withdraw my
question.
BookE KVM has not been too much trouble, but some things come up that
really need testing before patching, so a QEMU HV implementation would
be good to have (I mean QEMU running the host). mpe has a hardware but
probably no time$ to do much testing (especially of other peoples'
untested patches). So having that would help keep kernel support going.
Thanks,
Nick
next prev parent reply other threads:[~2022-12-06 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-04 11:33 [RFC PATCH] Disable Book-E KVM support? Christian Zigotzky
2022-12-04 12:23 ` Christian Zigotzky
2022-12-06 7:11 ` Nicholas Piggin [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-28 4:36 Nicholas Piggin
2022-11-30 20:45 ` Crystal Wood
2022-12-01 6:06 ` Nicholas Piggin
2022-12-01 11:23 ` Bernhard Beschow
2022-12-02 11:04 ` Daniel Henrique Barboza
2022-12-02 11:38 ` Cédric Le Goater
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=COUJPOA8V93O.3EB95FEH792PM@bobo \
--to=npiggin@gmail.com \
--cc=chzigotzky@xenosoft.de \
--cc=darren@stevens-zone.net \
--cc=info@xenosoft.de \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madskateman@gmail.com \
--cc=matthew@a-eon.biz \
--cc=qemu-ppc@nongnu.org \
--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).