qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH v3 00/10] Clock framework API.


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [PATCH v3 00/10] Clock framework API.
Date: Thu, 15 Jun 2017 16:49:29 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.0


On 15/06/2017 16:40, Peter Maydell wrote:
> On 14 June 2017 at 12:54, Paolo Bonzini <address@hidden> wrote:
>> I think the various bindings and rates could be refreshed as devices are
>> migrated.  This assumes that the device migration order is okay
>> according to the clock tree
> 
> Unfortunately we make no guarantees at all about migration order
> for devices as far as I'm aware, so devices have to cope regardless.

It's device realization order, so there are some guarantees.  A board
can realize devices in its preferred order (and realization will also
bind clocks and set rates IIUC, just like migration), and a qdev bus's
children will be visited after the bus owner.

> (There's also the possibility of an oddball bit of hardware which
> has a clocktree with loops in it.)

For these cases there is post_load, I guess.

Paolo



reply via email to

[Prev in Thread] Current Thread [Next in Thread]