qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementatio


From: Eric Auger
Subject: Re: [Qemu-devel] dynamic sysbus instantiation and load_dtb implementation
Date: Thu, 23 Oct 2014 14:41:10 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0

On 10/23/2014 01:41 PM, Eric Auger wrote:
> Hi,
> 
> Thanks everyone for entering the thread & reading my long email.
> 
> Alex, I indeed can register the notifier in the machine file after 
s/after/before
Eric
the
> platform bus instantiation. This indeed guarantees the notifiers are
> called in the right order ...

> 
> Thanks
> 
> Best Regards
> 
> Eric
> 
> On 10/23/2014 01:26 PM, Alexander Graf wrote:
>>
>>
>> On 23.10.14 13:24, Peter Maydell wrote:
>>> On 23 October 2014 12:23, Alexander Graf <address@hidden> wrote:
>>>> On 23.10.14 12:19, Ard Biesheuvel wrote:
>>>>> The reason for this change was that, before, the DTB would only be
>>>>> generated once, and after a reset, the machine would go through the
>>>>> kernel boot protocol as before but the DTB pointer would point to
>>>>> garbage. Any idea how ppc deals with this? Do they recreate the device
>>>>> tree after each reset?
>>>>
>>>> Yes, we regenerate the device tree on each reset.
>>>
>>> Any particular reason? Surely it's always the same...
>>
>> We have the code in place anyway, it's not a performance critical code
>> path and putting it into a rom would be a waste of RAM, as it'd keep yet
>> another copy of something we can easily regenerate.
>>
>> It's a matter of personal preference I guess.
>>
>>
>> Alex
>>
> 




reply via email to

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