From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
Cc: "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Yunqiang Su" <ysu@wavecomp.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"Igor Mammedov" <imammedo@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH v2 0/6] hw/mips/malta: Add the 'malta-strict' machine, matching Malta hardware
Date: Wed, 1 Jul 2020 11:49:06 +0100 [thread overview]
Message-ID: <20200701104906.GF1427561@redhat.com> (raw)
In-Reply-To: <CAHiYmc4=pmzEyhVTHaqxBnCotE8V+vaptMFincyurvAyDHNn6g@mail.gmail.com>
On Tue, Jun 30, 2020 at 05:38:25PM +0200, 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.
On x86 we model a i440fx from 1995. Max RAM in 1995 was on the order
of 10's of MB, but we run it with *multi-TB* of RAM in QEMU. There's
examples of this all over QEMU.
> As such, not acceptable for upstreaming.
I think this is quite unreasonable, especially considering this series is
addressing a real world problem that users of QEMU malta are facing with
insufficient RAM. QEMU exists to help users get their work done
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2020-07-01 10:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 14:52 [PATCH v2 0/6] hw/mips/malta: Add the 'malta-strict' machine, matching Malta hardware Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 1/6] hw/mips/malta: Trivial code movement Philippe Mathieu-Daudé
2020-06-30 14:52 ` Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 2/6] hw/mips/malta: Register the machine as a TypeInfo Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 3/6] hw/mips/malta: Introduce MaltaMachineClass::max_ramsize Philippe Mathieu-Daudé
2020-06-30 17:17 ` Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 4/6] hw/mips/malta: Introduce the 'malta-strict' machine Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 5/6] hw/mips/malta: Verify malta-strict machine uses correct DIMM sizes Philippe Mathieu-Daudé
2020-06-30 14:52 ` [PATCH v2 6/6] hw/mips/malta: Introduce the 'malta-unleashed' 64-bit machine Philippe Mathieu-Daudé
2020-07-01 10:59 ` Daniel P. Berrangé
2020-06-30 15:38 ` [PATCH v2 0/6] hw/mips/malta: Add the 'malta-strict' machine, matching Malta hardware Aleksandar Markovic
2020-06-30 16:46 ` Philippe Mathieu-Daudé
2020-06-30 16:55 ` Aleksandar Markovic
2020-06-30 17:16 ` Philippe Mathieu-Daudé
2020-06-30 17:28 ` Aleksandar Markovic
2020-06-30 19:51 ` Philippe Mathieu-Daudé
2020-06-30 20:36 ` Richard Henderson
2020-06-30 20:19 ` Thomas Huth
2020-07-01 10:49 ` Daniel P. Berrangé [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200701104906.GF1427561@redhat.com \
--to=berrange@redhat.com \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=aleksandar.rikalo@syrmia.com \
--cc=aurelien@aurel32.net \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=jiaxun.yang@flygoat.com \
--cc=qemu-devel@nongnu.org \
--cc=ysu@wavecomp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.