[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 2/2] Add -mem-shared option
From: |
Paolo Bonzini |
Subject: |
Re: [PATCH 2/2] Add -mem-shared option |
Date: |
Fri, 29 Nov 2019 11:11:09 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.1.1 |
On 29/11/19 11:07, Igor Mammedov wrote:
>>> So user who wants something non trivial could override default
>>> non-numa behavior with
>>> -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
>>> -machine memdev=mem
>>> or use any other backend that suits theirs needs.
>> That's nice, but not as friendly as a simple -mem-shared.
> (I still do not like idea of convenience options but it won't
> get onto the way much if implemented as "global property" to memdev,
> so I won't object if there is real demand for it)
I agree with Igor, we should always think about the generic ("object
model") options and only then add convenience option.
It looks like the remaining point is to decide between "-m memdev" and
"-machine memdev".
Paolo
Re: [PATCH 0/2] RFC: add -mem-shared option, Eduardo Habkost, 2019/11/28