From: Aleksandar Markovic <aleksandar.qemu.devel@gmail.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: "Aleksandar Rikalo" <aleksandar.rikalo@syrmia.com>,
"Yunqiang Su" <ysu@wavecomp.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"Jiaxun Yang" <jiaxun.yang@flygoat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>
Subject: Re: [PATCH 0/7] hw/mips/malta: Rework to allow more than 2GB of RAM on 64-bit
Date: Tue, 30 Jun 2020 13:01:20 +0200 [thread overview]
Message-ID: <CAHiYmc59Ahpii2dvhVD8EPK4qzc8y2RNTwTbp4L1d2Mjun+Phg@mail.gmail.com> (raw)
In-Reply-To: <CAAdtpL7MObRjk77ZFsNF4Xoghdj33mwufZ9s3L8fAC3XxkJCqA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2868 bytes --]
уторак, 30. јун 2020., Philippe Mathieu-Daudé <f4bug@amsat.org> је
написао/ла:
> On Tue, Jun 30, 2020 at 12:52 PM Philippe Mathieu-Daudé <f4bug@amsat.org>
> wrote:
> >
> > On 6/30/20 12:48 PM, Aleksandar Markovic wrote:
> > >
> > >
> > > уторак, 30. јун 2020., Philippe Mathieu-Daudé <f4bug@amsat.org
> > > <mailto:f4bug@amsat.org>> је написао/ла:
> > >
> > > Hi,
> > >
> > > Following Jiaxun Yang's patch and discussion:
> > > https://patchwork.kernel.org/patch/11416915/
> > > <https://patchwork.kernel.org/patch/11416915/>
> > >
> > > - Rename the current machine as 'malta-virt' (keeping 'malta'
> aliased)
> > > Suggestions for better names are welcome, maybe 'malta-unreal' or
> > > 'malta-unleashed' instead?
> > > - Add 'malta-phys' which respects hardware restrictions (on RAM so
> far)
> > > - Unleash 'malta-virt' to allow more than 2GB on 64-bit
> > >
> > > Philippe Mathieu-Daudé (7):
> > > hw/mips/malta: Trivial code movement
> > > hw/mips/malta: Register the machine as a TypeInfo
> > > hw/mips/malta: Rename 'malta' machine as 'malta-virt'
> > > hw/mips/malta: Introduce MaltaMachineClass::max_ramsize
> > > hw/mips/malta: Introduce the 'malta-phys' machine
> > > hw/mips/malta: Verify malta-phys machine uses correct DIMM sizes
> > > hw/mips/malta: Allow more than 2GB on 64-bit malta-virt
> > >
> > > hw/mips/malta.c | 121 ++++++++++++++++++++++++++++++
> +++++++++---------
> > > 1 file changed, 99 insertions(+), 22 deletions(-)
> > >
> > > --
> > >
> > >
> > >
> > > Thank you, Philippe, for providing this series.
> > >
> > > However, in previous discussion on the patch you mention above, I
> > > already expressed serious reservations on the approach taken in that
> > > patch. These reservations stay today too.
> > >
> > > There is nothing qualitatively different between the original patch and
> > > this series. Naming and related stuff are just cosmetic issues.
> >
> > OK, what about considering all patches except the last one?
> > So we can run firmware on a real Malta board, not the QEMU
> > imaginary one (in the discussion you said QEMU should respect
> > real hardware, which I agree).
> >
> > >
> > > The good thing about this series is that one can apply it dowstream, if
> > > one finds it useful. However, it is not suitable for upstreaming
>
> IOW, what is missing to have this series (except the last patch)
> accepted upstream?
>
>
It is not what is missing, but was already is in the series that makes it
not suitable for upstreaming. The very concept of the series is problematic.
Regards,
Aleksandar
> > >
> > > Regards,
> > > Aleksandar
> > >
> > >
> > >
> > > 2.21.3
> > >
>
[-- Attachment #2: Type: text/html, Size: 4175 bytes --]
next prev parent reply other threads:[~2020-06-30 11:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 8:13 [PATCH 0/7] hw/mips/malta: Rework to allow more than 2GB of RAM on 64-bit Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 1/7] hw/mips/malta: Trivial code movement Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 2/7] hw/mips/malta: Register the machine as a TypeInfo Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 3/7] hw/mips/malta: Rename 'malta' machine as 'malta-virt' Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 4/7] hw/mips/malta: Introduce MaltaMachineClass::max_ramsize Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 5/7] hw/mips/malta: Introduce the 'malta-phys' machine Philippe Mathieu-Daudé
2020-06-30 8:54 ` Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 6/7] hw/mips/malta: Verify malta-phys machine uses correct DIMM sizes Philippe Mathieu-Daudé
2020-06-30 8:13 ` [PATCH 7/7] hw/mips/malta: Allow more than 2GB on 64-bit malta-virt Philippe Mathieu-Daudé
2020-06-30 10:48 ` [PATCH 0/7] hw/mips/malta: Rework to allow more than 2GB of RAM on 64-bit Aleksandar Markovic
2020-06-30 10:52 ` Philippe Mathieu-Daudé
2020-06-30 10:53 ` Philippe Mathieu-Daudé
2020-06-30 11:01 ` Aleksandar Markovic [this message]
2020-06-30 11:04 ` Philippe Mathieu-Daudé
2020-06-30 11:17 ` Aleksandar Markovic
2020-06-30 11:34 ` Philippe Mathieu-Daudé
2020-06-30 11:55 ` Aleksandar Markovic
2020-06-30 11:59 ` Philippe Mathieu-Daudé
2020-06-30 12:07 ` Aleksandar Markovic
2020-06-30 13:36 ` Thomas Huth
2020-06-30 13:45 ` Philippe Mathieu-Daudé
2020-06-30 10:54 ` Aleksandar Markovic
2020-06-30 10:58 ` Philippe Mathieu-Daudé
2020-06-30 11:05 ` Aleksandar Markovic
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=CAHiYmc59Ahpii2dvhVD8EPK4qzc8y2RNTwTbp4L1d2Mjun+Phg@mail.gmail.com \
--to=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=philmd@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).