From: "Cédric Le Goater" <clg@kaod.org>
To: Greg Kurz <groug@kaod.org>, David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] pnv/psi: Consolidate some duplicated code in pnv_psi_realize()
Date: Wed, 8 Jan 2020 14:20:45 +0100 [thread overview]
Message-ID: <da8ae351-d4fe-061d-a9f3-d275d3ba456c@kaod.org> (raw)
In-Reply-To: <20200108115845.07f10453@bahia.lan>
On 1/8/20 11:58 AM, Greg Kurz wrote:
> On Wed, 8 Jan 2020 11:54:53 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
>> On Tue, Jan 07, 2020 at 07:32:03PM +0100, Philippe Mathieu-Daudé wrote:
>>> Hi Greg,
>>>
>>> On 1/7/20 5:32 PM, Greg Kurz wrote:
>>>> The proper way to do that would be to use device_class_set_parent_realize(),
>>>> but defining a Pnv8PsiClass and a Pnv9PsiClass types with a parent_realize
>>>> pointer adds a fair amount of code. Calling pnv_psi_realize() explicitely
>>>> is fine for now.
>>>>
>>>> This should probably be achieved with a device realize hook in the
>>>> PSI base class and device_class_set_parent_realize() in the children
>>>> classes.
>>>
>
> I realize that this last paragraph is a leftover. First paragraph already
> mentions device_class_set_parent_realize() as being the "proper way".
>
> David,
>
> Can you remove it in your tree ? No big deal if you can't.
>
>>> Can you add a note explaining why the POWER10 PSI doesn't need it?
>>
>> For now, POWER10 uses the Pnv9PsiClass, I believe, so the question
>> doesn't arise.
>>
>
> This is correct and also a bit confusing, as proves Philippe's remark.
> Maybe we should come up with a PnvXivePsiClass and specialize it for
> POWER9 and POWER10.
Yes. I think this is the way to go.
P8 has a PSI device using the XICS interrupt interface. P9 and P10 use
the XIVE interface.
C.
next prev parent reply other threads:[~2020-01-08 13:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 16:32 [PATCH 0/2] ppc/pnv: Reset handler registration cleanup Greg Kurz
2020-01-07 16:32 ` [PATCH 1/2] pnv/psi: Add device reset hook Greg Kurz
2020-01-07 18:28 ` Philippe Mathieu-Daudé
2020-01-08 0:07 ` David Gibson
2020-01-07 16:32 ` [PATCH 2/2] pnv/psi: Consolidate some duplicated code in pnv_psi_realize() Greg Kurz
2020-01-07 18:32 ` Philippe Mathieu-Daudé
2020-01-08 0:54 ` David Gibson
2020-01-08 10:58 ` Greg Kurz
2020-01-08 13:20 ` Cédric Le Goater [this message]
2020-01-09 1:33 ` David Gibson
2020-01-08 0:54 ` David Gibson
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=da8ae351-d4fe-061d-a9f3-d275d3ba456c@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=groug@kaod.org \
--cc=philmd@redhat.com \
--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).