From: BALATON Zoltan <balaton@eik.bme.hu>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
"list@suse.de:PowerPC" <qemu-ppc@nongnu.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2 12/20] ppc/ppc405: QOM'ify EBC
Date: Fri, 5 Aug 2022 14:55:01 +0200 (CEST) [thread overview]
Message-ID: <a992199c-b51d-6baa-b91b-4959ec4a46e8@eik.bme.hu> (raw)
In-Reply-To: <743ea55a-915e-5991-5d7c-ef00ee307ee9@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 4598 bytes --]
On Fri, 5 Aug 2022, Cédric Le Goater wrote:
> On 8/4/22 21:26, BALATON Zoltan wrote:
>> On Thu, 4 Aug 2022, Peter Maydell wrote:
>>> On Thu, 4 Aug 2022 at 19:03, BALATON Zoltan <balaton@eik.bme.hu> wrote:
>>>> I was trying to find out how to do it but I don't understand QOM enough
>>>> to
>>>> answer the simple question of how to get the cpu object from QOM. My
>>>> guesses are:
>>>>
>>>> object_resolve_path_type("/machine", TYPE_POWERPC_CPU, NULL)
>>
>> Out of curiosity would this work though to get the cpu or if not why not
>> and what would be a preferred way? I could not find this out from reading
>> the object.h comments, the docs/deve/qom.rst, nor searching the code.
>
> You could scan the object topology using object_child_foreach_recursive()
> and use object_dynamic_cast() to find a POWERPC CPU object. A link is
> much faster !
Yes that sounds a lot slower, I hoped there's simple easy way to get to
the cpu, then we could simplify this a bit.
One more idea, you've introduced the Ppc405MachineState which you can get
to casting current_machine and so it's a convenient place to store a cpu
pointer or even just use PPC405_MACHINE(current_machine)->soc.cpu. This
works for these 405 machines you've changed in this series but other
PPC4xx machines don't have this machine and soc states yet. Could these
Ppc405MachineState and Ppc405SoCState be more generic as
Ppc4xxMachineState and Ppc4xxSoCState considering that these chips are
quite similar or maybe we need an abstract PPC4xxSoC class but machine
state could be shared? (If you say this is too much cahnges for you now I
may try to look at this later once your series is merged but going that
way now could save some churn.) If we had a Ppc4xxMachineState that has a
cpu pointer then we could easily add that to bamboo and sam460ex now and
these QOMified devices could then use PPC4XX_MACHINE(current_machine)->cpu
instead of a link property. What do you think?
>> If this is the preferred way then so be it, I just don't like it because I
>> think this is too many boilerplate code that could be avoided. This series:
>>
>> 9 files changed, 894 insertions(+), 652 deletions(-)
>>
>> and that's including removing all of the taihu machine; the file where
>> the QOMification is done:
>>
>> hw/ppc/ppc405_uc.c | 799 +++++++++++++++++++-------------
>
> Yes. You should consider also that this code is > 15 years old and
> serious shortcuts have been taken to "make things work". I think QOM
> clarifies the models and represents better the HW topology. There is
> a price in being explicit.
I know this is a mess curently but QOM is full of boilerplate code which
is confusing for new people and makes it hard to undestand the code. So
cutting down the boilerplate and making things simpler would help people
who want to get started with QEMU development. If adding a property was
3-4 additional lines I wouldn't care but if it makes the code
significantly more complex and thus harder to understand at a glance then
I'd rather avoid it if possible and stick to simple terms. Verbosity is
good if it explains things better but bad if it's hiding the important
details between unneeded complexity due to having to use constructs that
are not obvious. Also the property needs to be set which is additional
lines and possibility for mistakes so if there's a way to avoid that I
think that's better.
>> Ideally introducing QOM should make it simpler not more complex. Four of
>> the QOMified devices only have a property defined at all because of this
>> cpu link that's only used once in the realize method to register DCRs. This
>> is about 10 lines of code each. If there was a simple way to get the cpu
>> object from these realize methods then we could get rid of all these
>> properties and save about 40-50 lines and make these simpler.
>
> I tried several approaches and found this one was the simplest and not
> too verbose really.
>
> The DCRs are accessed by software through the use of the mtdcr and mfdcr
> instructions. These are converted in transactions on a side band bus,
> the DCR bus, which connects the on-SoC devices to the CPU. The "cpu" link
> should be considered as modeling this little piece of HW logic connecting
> the device to the DCR bus.
I rather consider it an implementation detail and trying to find the
simplest way. If we don't find anything simpler I'm OK with link
properties but I'm not convinced yet there's no simpler solution to this
problem that could avoid some of the additional complexity.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2022-08-05 12:57 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 13:28 [PATCH v2 00/20] ppc: QOM'ify 405 board Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 01/20] ppc/ppc405: Remove taihu machine Cédric Le Goater
2022-08-03 17:16 ` Daniel Henrique Barboza
2022-08-03 13:28 ` [PATCH v2 02/20] ppc/ppc405: Introduce a PPC405 generic machine Cédric Le Goater
2022-08-03 17:03 ` BALATON Zoltan
2022-08-03 17:35 ` Daniel Henrique Barboza
2022-08-03 22:07 ` BALATON Zoltan
2022-08-04 5:40 ` Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 03/20] ppc/ppc405: Move devices under the ref405ep machine Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 04/20] ppc/ppc405: Introduce a PPC405 SoC Cédric Le Goater
2022-08-03 22:13 ` BALATON Zoltan
2022-08-03 13:28 ` [PATCH v2 05/20] ppc/ppc405: Start QOMification of the SoC Cédric Le Goater
2022-08-03 22:23 ` BALATON Zoltan
2022-08-04 6:00 ` Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 06/20] ppc/ppc405: QOM'ify CPU Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 07/20] ppc/ppc405: QOM'ify CPC Cédric Le Goater
2022-08-03 17:16 ` BALATON Zoltan
2022-08-04 5:09 ` Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 08/20] ppc/ppc405: QOM'ify GPT Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 09/20] ppc/ppc405: QOM'ify OCM Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 10/20] ppc/ppc405: QOM'ify GPIO Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 11/20] ppc/ppc405: QOM'ify DMA Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 12/20] ppc/ppc405: QOM'ify EBC Cédric Le Goater
2022-08-03 23:04 ` BALATON Zoltan
2022-08-04 7:55 ` Mark Cave-Ayland
2022-08-04 10:58 ` BALATON Zoltan
2022-08-03 23:36 ` Daniel Henrique Barboza
2022-08-04 5:14 ` Cédric Le Goater
2022-08-04 12:09 ` BALATON Zoltan
2022-08-04 16:21 ` Cédric Le Goater
[not found] ` <3b1bc6c5-a363-0a42-f0dc-eafc14376fe2@kaod.org>
[not found] ` <1e6be2f3-4c7a-2432-5034-fa012c662df@eik.bme.hu>
2022-08-04 16:31 ` Cédric Le Goater
2022-08-04 18:00 ` BALATON Zoltan
2022-08-04 18:18 ` Peter Maydell
2022-08-04 19:26 ` BALATON Zoltan
2022-08-05 7:07 ` Cédric Le Goater
2022-08-05 12:55 ` BALATON Zoltan [this message]
2022-08-05 13:16 ` Peter Maydell
2022-08-05 16:50 ` BALATON Zoltan
2022-08-05 16:55 ` Peter Maydell
2022-08-05 17:03 ` BALATON Zoltan
2022-08-05 19:15 ` BALATON Zoltan
2022-08-06 9:38 ` BALATON Zoltan
2022-08-08 6:42 ` Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 13/20] ppc/ppc405: QOM'ify OPBA Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 14/20] ppc/ppc405: QOM'ify POB Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 15/20] ppc/ppc405: QOM'ify PLB Cédric Le Goater
2022-08-03 23:38 ` Daniel Henrique Barboza
2022-08-03 13:28 ` [PATCH v2 16/20] ppc/ppc405: QOM'ify MAL Cédric Le Goater
2022-08-03 23:45 ` Daniel Henrique Barboza
2022-08-03 13:28 ` [PATCH v2 17/20] ppc/ppc405: QOM'ify FPGA Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 18/20] ppc/ppc405: QOM'ify UIC Cédric Le Goater
2022-08-03 23:26 ` BALATON Zoltan
2022-08-03 13:28 ` [PATCH v2 19/20] ppc/ppc405: QOM'ify I2C Cédric Le Goater
2022-08-03 23:31 ` BALATON Zoltan
2022-08-04 5:42 ` Cédric Le Goater
2022-08-04 11:21 ` BALATON Zoltan
2022-08-04 14:14 ` Cédric Le Goater
2022-08-03 13:28 ` [PATCH v2 20/20] ppc/ppc4xx: Fix sdram trace events Cédric Le Goater
2022-08-04 6:07 ` [PATCH v2 00/20] ppc: QOM'ify 405 board Cédric Le Goater
2022-08-04 10:07 ` Daniel Henrique Barboza
2022-08-04 12:26 ` 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=a992199c-b51d-6baa-b91b-4959ec4a46e8@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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 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.