Re: [PATCH v2 0/6] hw/mips/malta: Add the 'malta-strict' machine, matching Malta hardware

[Thomas Huth <thuth@redhat.com>]

On 30/06/2020 17.38, Aleksandar Markovic wrote:
> уто, 30. јун 2020. у 16:52 Philippe Mathieu-Daudé <f4bug@amsat.org> је
> написао/ла:
>>
>> Hi,
>>
>> This series add a new 'malta-strict' machine, that aims to properly
>> model the real hardware (which is not what the current 'malta'
>> machine models).
>>
>> As a bonus for Debian builders, a 'malta-unleashed' machine RFC
>> patch is included. This might start another endless discussion
>> upstream, but this is not the point of, so I still include it
>> for people to test. The rest of the series is candidate for merging
>> in mainstream QEMU.
>>
>> Philippe Mathieu-Daudé (6):
>>    hw/mips/malta: Trivial code movement
>>    hw/mips/malta: Register the machine as a TypeInfo
>>    hw/mips/malta: Introduce MaltaMachineClass::max_ramsize
>>    hw/mips/malta: Introduce the 'malta-strict' machine
>>    hw/mips/malta: Verify malta-strict machine uses correct DIMM sizes
>>    hw/mips/malta: Introduce the 'malta-unleashed' 64-bit machine
>>
>>   hw/mips/malta.c | 125 ++++++++++++++++++++++++++++++++++++++++++------
>>   1 file changed, 111 insertions(+), 14 deletions(-)
>>
>> --
> 
> This whole series is based on idea of emulating physically
> non-existing feature, and as such violates the fundamental principles
> of QEMU.
> 
> As such, not acceptable for upstreaming.

  Hi Aleksandar,

could you please point me to the spot where we declare this "fundamental 
principle" of QEMU? Sorry, but I must have missed this piece of 
information so far. And could you please enlighten me what we should do 
now with virtio, since most of these devices also are physically 
non-existent?

  Thanks,
   Thomas