[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PULL 59/68] aspeed: Add an AST2600 eval board
From: |
Joel Stanley |
Subject: |
Re: [PULL 59/68] aspeed: Add an AST2600 eval board |
Date: |
Wed, 16 Oct 2019 11:28:35 +0000 |
On Tue, 15 Oct 2019 at 17:55, Peter Maydell <address@hidden> wrote:
>
> On Tue, 15 Oct 2019 at 18:43, Cédric Le Goater <address@hidden> wrote:
> > On 15/10/2019 19:03, Peter Maydell wrote:
> > > On Mon, 14 Oct 2019 at 17:05, Peter Maydell <address@hidden> wrote:
> > > (armhf)pmaydell@mustang-maydell:~/qemu$
> > > ./build/all-a32/arm-softmmu/qemu-system-arm -M ast2600-evb
> > > qemu-system-arm: at most 2047 MB RAM can be simulated
> > >
> > > It's also a pretty rudely large amount of RAM to allocate
> > > by default: it caused 'make check' to fail on my OSX
> > > box, which is 64-bits but doesn't have huge swathes
> > > of free RAM.
> > >
> > > I'm going to drop this patch from my queue and redo
> > > the pullreq.
> >
> > ok. We do have such a board.
> >
> > What do you suggest ? We can lower the RAM to 1G for QEMU.
>
> 1GB is OK -- we have several machines that set default_ram_size to that.
>
> If we want to handle more generally boards which have a
> larger ram size by default then we probably need to
> work on the 'make check' infrastructure -- right now we
> have a generic test that just checks "can we instantiate
> every machine model", which is what's falling over.
I hit this when bumping the RAM size for the powernv machine too. In
that case it was a convenient size given the memory layout we have, so
changing to be less than 2GB was not making the model less accurate.
For the ast2600evb machine, the board actually has 2GB of RAM, and
it's useful for guests to test in this environment. I'd not had any
reports of it failing to launch due to a failed memory allocation,
which I guess is indicative of the systems people who use the model
have.
Peter, did you have any thoughts on how to exclude such guests from
testing in environments where memory is limited?
Cheers,
Joel
- [PULL 52/68] aspeed/smc: Add AST2600 support, (continued)
- [PULL 52/68] aspeed/smc: Add AST2600 support, Peter Maydell, 2019/10/14
- [PULL 51/68] aspeed/smc: Introduce segment operations, Peter Maydell, 2019/10/14
- [PULL 53/68] hw/gpio: Add in AST2600 specific implementation, Peter Maydell, 2019/10/14
- [PULL 55/68] aspeed/i2c: Add AST2600 support, Peter Maydell, 2019/10/14
- [PULL 54/68] aspeed/i2c: Introduce an object class per SoC, Peter Maydell, 2019/10/14
- [PULL 58/68] m25p80: Add support for w25q512jv, Peter Maydell, 2019/10/14
- [PULL 59/68] aspeed: Add an AST2600 eval board, Peter Maydell, 2019/10/14
- Re: [PULL 59/68] aspeed: Add an AST2600 eval board, Philippe Mathieu-Daudé, 2019/10/16
- Re: [PULL 59/68] aspeed: Add an AST2600 eval board, Cédric Le Goater, 2019/10/16
- Re: [PULL 59/68] aspeed: Add an AST2600 eval board, Philippe Mathieu-Daudé, 2019/10/16
[PULL 56/68] aspeed: Introduce an object class per SoC, Peter Maydell, 2019/10/14
[PULL 57/68] aspeed/soc: Add AST2600 support, Peter Maydell, 2019/10/14
[PULL 60/68] aspeed: Parameterise number of MACs, Peter Maydell, 2019/10/14
[PULL 61/68] aspeed: add support for the Aspeed MII controller of the AST2600, Peter Maydell, 2019/10/14
[PULL 62/68] aspeed/soc: Add ASPEED Video stub, Peter Maydell, 2019/10/14
[PULL 63/68] hw/arm/raspi: Use the IEC binary prefix definitions, Peter Maydell, 2019/10/14
[PULL 64/68] hw/arm/bcm2835_peripherals: Improve logging, Peter Maydell, 2019/10/14