All of lore.kernel.org
 help / color / mirror / Atom feed
From: Aurelien Jarno <aurelien@aurel32.net>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: Paul Burton <pburton@wavecomp.com>,
	Peter Maydell <peter.maydell@linaro.org>,
	Yunqiang Su <ysu@wavecomp.com>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Jiaxun Yang <jiaxun.yang@flygoat.com>,
	Paul Burton <paul.burton@mips.com>,
	Aleksandar Markovic <amarkovic@wavecomp.com>,
	Igor Mammedov <imammedo@redhat.com>,
	Aleksandar Markovic <aleksandar.m.mail@gmail.com>
Subject: Re: [PATCH v1] mips/mips_malta: Allow more than 2G RAM
Date: Mon, 23 Mar 2020 17:35:45 +0100	[thread overview]
Message-ID: <20200323163545.GA19598@aurel32.net> (raw)
In-Reply-To: <d9f08408-9c1e-36d9-869b-bac250c6f027@redhat.com>

Hi,

Sorry for the delay, I just want to give some more details about the
Debian.

On 2020-03-14 10:09, Philippe Mathieu-Daudé wrote:
> IIUC today all distributions supporting MIPS ports are building their MIPS
> packages on QEMU instances because it is faster than the native MIPS
> hardware they have.

Actually Debian requires that packages are built on real hardware. We
have a mix of Loongson 3 and Octeon 3 based build daemons. They all have
8GiB of RAM.

> Since one (or two?) years, some binaries (Linux kernel? QEMU?) are failing
> to link because the amount of guest memory is restricted to 2GB (probably
> advance of linker techniques, now linkers use more memory).

The problem happens with big packages (e.g. ceph which is a dependency
of QEMU). The problem is not the physical memory issue, but the virtual
address space, which is limited to 2GB for 32-bit processes. That's why
we do not have the issue for the 64-bit ports.

> YunQiang, is this why you suggested this change?
> 
> See:
> - https://www.mail-archive.com/debian-mips@lists.debian.org/msg10912.html
> - https://alioth-lists.debian.net/pipermail/pkg-rust-maintainers/2019-January/004844.html
> 
> I believe most of the QEMU Malta board users don't care it is a Malta board,
> they only care it is a fast emulated MIPS machine.
> Unfortunately it is the default board.
> 
> However 32-bit MIPS port is being dropped on Debian:
> https://lists.debian.org/debian-mips/2019/07/msg00010.html

The 32-bit big endian port has been dropped after the Buster (10)
release and won't be available for the Bullseye release (11). The
32-bit little endian port is still available, but it's difficult to keep
it alive given the 2GB limit.

> Maybe we can sync with the Malta users, ask them to switch to the Boston
> machines to build 64-bit packages, then later reduce the Malta board to 1GB.
> (The Boston board is more recent, but was not available at the time users
> started to use QEMU to build 64-bit packages).
> 
> Might it be easier starting introducing a malta-5.0 machine restricted to
> 1GB?

In any case having an easy way to simulate machines with more than 2GB
of RAM in QEMU would be great.

Cheers,
Aurelien

-- 
Aurelien Jarno                          GPG: 4096R/1DDD8C9B
aurelien@aurel32.net                 http://www.aurel32.net


  parent reply	other threads:[~2020-03-23 16:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28  3:26 [PATCH] mips/mips_malta: Allow more than 2G RAM Jiaxun Yang
2020-03-02 21:22 ` [EXTERNAL][PATCH] " Aleksandar Markovic
2020-03-02 23:59   ` Philippe Mathieu-Daudé
2020-03-03  7:57     ` Igor Mammedov
2020-03-03  0:41 ` [PATCH v1] " Jiaxun Yang
2020-03-05 10:18   ` Philippe Mathieu-Daudé
2020-03-14  3:25     ` Aleksandar Markovic
2020-03-14  9:09       ` Philippe Mathieu-Daudé
2020-03-14 12:24         ` Jiaxun Yang
2020-03-14 16:50           ` Aleksandar Markovic
2020-03-23 16:35         ` Aurelien Jarno [this message]
2020-03-23 16:41           ` Philippe Mathieu-Daudé
2020-03-24 20:00           ` 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=20200323163545.GA19598@aurel32.net \
    --to=aurelien@aurel32.net \
    --cc=aleksandar.m.mail@gmail.com \
    --cc=amarkovic@wavecomp.com \
    --cc=imammedo@redhat.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=paul.burton@mips.com \
    --cc=pburton@wavecomp.com \
    --cc=peter.maydell@linaro.org \
    --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 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.