qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as migration


From: Paolo Bonzini
Subject: Re: [Qemu-devel] [RFC] exec: eliminate ram naming issue as migration
Date: Mon, 5 Feb 2018 18:31:33 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2

On 05/02/2018 18:15, Igor Mammedov wrote:
>>>
>>> Then we would have both ram block named pc.ram:
>>>               Block Name    PSize
>>>                       pc.ram     4 KiB
>>>       /objects/pc.ram    2 MiB
>>>
>>> But I assume it's a corner case which not really happen.  
>> Yeah, you're right. :/  I hadn't thought of hotplug.  It can happen indeed.
>  
> perhaps we should fail object_add memory-backend-foo if it resulted
> in creating ramblock with duplicate id

Note that it would only be duplicated with Jianfeng's patch.  So I'm
worried that his patch is worse than what we have now, because it may
create conflicts with system RAMBlock names are not necessarily
predictable.  Right now, -object creates RAMBlock names that are nicely
constrained within /object/.

Paolo



reply via email to

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