[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/2] RFC: add -mem-shared option
From: |
Paolo Bonzini |
Subject: |
Re: [PATCH 0/2] RFC: add -mem-shared option |
Date: |
Fri, 29 Nov 2019 12:21:54 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
On 29/11/19 11:23, Igor Mammedov wrote:
> [...]
>> Therefore, I think instead of -mem-shared we should add a "-m
>> memdev=..." option. This option:
>>
>> * would be mutually exclusive with both -mem-path
>>
>> * would be handled from allocate_system_memory_nonnuma.
>>
>> * could be mutually exclusive "-numa node", or could just be mutually
>> exclusive with "-numa node,memdev=..." (the logical conclusion of that
>> however would be an undeprecation of "-numa node,mem=...", so that has
>> to be taken into account as well).
> the plan was/still is to have memdev for main ram and deprecate
> "-numa node,mem=..." for new machine types (can't be done for
> old ones due to migration breakages and old libvirt which uses
> it). So new machines will be forced to use "-numa memdev"
> For old machines '-m memdev' provided memory region will used to
> keep "-numa node,mem=..." working as it's now (however broken it is).
Ok, then "-m memdev=..." would only be mutually exclusive with
"-mem-path" and "-numa node,memdev=...".
Thanks!
Paolo
Re: [PATCH 0/2] RFC: add -mem-shared option, Eduardo Habkost, 2019/11/28
Re: [PATCH 0/2] RFC: add -mem-shared option, Dr. David Alan Gilbert, 2019/11/28
Re: [PATCH 0/2] RFC: add -mem-shared option, no-reply, 2019/11/28
Re: [PATCH 0/2] RFC: add -mem-shared option, no-reply, 2019/11/29
Re: [PATCH 0/2] RFC: add -mem-shared option, Gerd Hoffmann, 2019/11/29