[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Purpose of QOM properties registered at realize time?
From: |
Peter Maydell |
Subject: |
Re: Purpose of QOM properties registered at realize time? |
Date: |
Thu, 8 Oct 2020 16:41:37 +0100 |
On Thu, 8 Oct 2020 at 16:15, Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> On Thu, Oct 08, 2020 at 11:45:08AM +0200, Markus Armbruster wrote:
> > A first class static array property, where the size of the array is part
> > of the value could perhaps cover this case.
>
> This is an interesting idea, I think we should explore that.
>
> qdev_pass_gpios() would become unnecessary and could be replaced
> by a single (static) alias property.
At least in the current implementation, aliasing properties
is not the only thing qdev_pass_gpios() does -- it also
updates the NamedGPIOList data structures. It might be
possible to reimplement it so that we really are just
aliasing properties, though.
thanks
-- PMM
- Re: Purpose of QOM properties registered at realize time?, (continued)
- Re: Purpose of QOM properties registered at realize time?, Paolo Bonzini, 2020/10/07
- Re: Purpose of QOM properties registered at realize time?, Eduardo Habkost, 2020/10/07
- Re: Purpose of QOM properties registered at realize time?, Paolo Bonzini, 2020/10/07
- Re: Purpose of QOM properties registered at realize time?, Eduardo Habkost, 2020/10/07
- Re: Purpose of QOM properties registered at realize time?, Peter Maydell, 2020/10/07
Re: Purpose of QOM properties registered at realize time?, Peter Maydell, 2020/10/07
Re: Purpose of QOM properties registered at realize time?, Mark Cave-Ayland, 2020/10/12