[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM
From: |
Daniel P . Berrangé |
Subject: |
Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM |
Date: |
Mon, 3 Feb 2025 14:33:21 +0000 |
User-agent: |
Mutt/2.2.13 (2024-03-09) |
On Mon, Feb 03, 2025 at 02:29:49PM +0000, Alex Bennée wrote:
> Peter Maydell <peter.maydell@linaro.org> writes:
>
> > On Sat, 1 Feb 2025 at 12:57, BALATON Zoltan <balaton@eik.bme.hu> wrote:
> >>
> >> On Sat, 1 Feb 2025, Philippe Mathieu-Daudé wrote:
> >> > - Deprecate the 'raspi4b' machine name, renaming it as
> >> > 'raspi4b-1g' on 32-bit hosts, 'raspi4b-2g' otherwise.
> >> > - Add the 'raspi4b-4g' and 'raspi4b-8g' machines, with
> >> > respectively 4GB and 8GB of DRAM.
> >>
> >> IMHO (meaning you can ignore it, just my opinion) if the only difference
> >> is the memory size -machine raspi4b -memory 4g would be better user
> >> experience than having a lot of different machines.
> >
> > Yes, I think I agree. We have a way for users to specify
> > how much memory they want, and I think it makes more sense
> > to use that than to have lots of different machine types.
>
> I guess for the Pi we should validate the -memory supplied is on of the
> supported grid of devices rather than an arbitrary value?
If the user wants to create a rpi4 with 6 GB RAM why should we stop
them ? It is their choice if they want to precisely replicate RAM
size from a physical model, or use something different when virtualized.
With 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 :|
- [PATCH 2/7] hw/arm/raspi4b: Introduce abstract raspi4-base machine type, (continued)
- [PATCH 2/7] hw/arm/raspi4b: Introduce abstract raspi4-base machine type, Philippe Mathieu-Daudé, 2025/02/01
- [PATCH 3/7] hw/arm/raspi4b: Split raspi4b_machine_class_init() in two (1g and 2g), Philippe Mathieu-Daudé, 2025/02/01
- [PATCH 4/7] hw/arm/raspi4b: Rename as raspi4b-1g / raspi4b-2g, deprecating old name, Philippe Mathieu-Daudé, 2025/02/01
- [PATCH 5/7] hw/arm/raspi4b: Expose the raspi4b-1g machine on 64-bit hosts, Philippe Mathieu-Daudé, 2025/02/01
- [PATCH 6/7] hw/arm/raspi4b: Add the raspi4b-4g machine, Philippe Mathieu-Daudé, 2025/02/01
- [PATCH 7/7] hw/arm/raspi4b: Add the raspi4b-8g machine, Philippe Mathieu-Daudé, 2025/02/01
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, BALATON Zoltan, 2025/02/01
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Peter Maydell, 2025/02/01
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Alex Bennée, 2025/02/03
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM,
Daniel P . Berrangé <=
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Peter Maydell, 2025/02/03
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Daniel P . Berrangé, 2025/02/03
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Peter Maydell, 2025/02/03
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, Philippe Mathieu-Daudé, 2025/02/03
- Re: [PATCH 0/7] hw/arm/raspi4b: Add models with 4GB and 8GB of DRAM, BALATON Zoltan, 2025/02/03