qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
	"Daniel Henrique Barboza" <danielhb413@gmail.com>
Cc: peter.maydell@linaro.org, groug@kaod.org, qemu-devel@nongnu.org,
	Luis Fernando Fujita Pires <luis.pires@eldorado.org.br>,
	qemu-ppc@nongnu.org, matheus.ferst@eldorado.org.br,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH] target/ppc, hw/ppc: Change maintainers
Date: Sat, 6 Nov 2021 17:55:28 +0100	[thread overview]
Message-ID: <aa8ad81f-db92-009c-e4f4-8d54455a098e@kaod.org> (raw)
In-Reply-To: <bb0f4cb9-1c95-c45c-8eb9-b5504787fb1b@amsat.org>

>> What we are going do will depend on inputs really. We have pseries
>> and KVM in focus because there is still business using the software
>> stack. TCG is extremely useful for pseries and powernv. We clearly
>> want to keep that running and improve it. Some parts have been barely
>> touched (and probably used) in the last 15 years. I think we should
>> drop some support to modernize the useful parts and ease maintenance.
> 
> Here let me recommend the ant work approach I'm doing for MIPS. Instead
> of dropping ISA extensions, I'm splitting them in various compile units,
> that way 1/ we can chose to build without them and 2/ sub-maintainers
> can maintain them separately. Having a finer grained MAINTAINERS
> entries allow to filter-out/in and reduce reviewers pressure.

OK. Yes, the goal is to ease maintenance, not to remove platforms or
CPUs. QEMU is the perfect project for legacy systems.

I am very willing to go in that direction and take the risk to break
a few things. We have been through such an episode when HV mode was
added for the PowerNV machine and we managed to fix all regressions,
down to OpenBIOS. Ben and his ppc32 knowledge helped a lot of course.

Untangling some parts won't be easy. Exception modeling for instance.
The instruction implementation shouldn't be too hard and it's being
modernized by Luis and Matheus. I guess we should improve our
testsuite to catch early any issues. An acceptance test for each
machine is a minimum.

Thanks,

C.



  reply	other threads:[~2021-11-06 16:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-05  3:46 [PATCH] target/ppc, hw/ppc: Change maintainers David Gibson
2021-11-05  9:48 ` Daniel Henrique Barboza
2021-11-05 19:16   ` Philippe Mathieu-Daudé
2021-11-05 20:05     ` Daniel Henrique Barboza
2021-11-06  4:20       ` David Gibson
2021-11-06  8:28         ` Cédric Le Goater
2021-11-06  8:53           ` David Gibson
2021-11-07 20:15             ` Greg Kurz
2021-11-06  9:18       ` Philippe Mathieu-Daudé
2021-11-05 23:00     ` Cédric Le Goater
2021-11-06  9:22       ` Philippe Mathieu-Daudé
2021-11-06 16:55         ` Cédric Le Goater [this message]
2021-11-05 13:54 ` 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=aa8ad81f-db92-009c-e4f4-8d54455a098e@kaod.org \
    --to=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=f4bug@amsat.org \
    --cc=groug@kaod.org \
    --cc=luis.pires@eldorado.org.br \
    --cc=matheus.ferst@eldorado.org.br \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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).