On Fr, 2013-10-18 at 15:31 +0200, Andrea Arcangeli wrote:
> On Fri, Oct 18, 2013 at 10:55:12AM +0200, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > > The premise that "this will also allow to pass non-contiguous memory"
> > > > > is partly false, as you can't use the e820 API below 4g so there's no
>
On Fri, Oct 18, 2013 at 10:55:12AM +0200, Gerd Hoffmann wrote:
> Hi,
>
> > > > The premise that "this will also allow to pass non-contiguous memory"
> > > > is partly false, as you can't use the e820 API below 4g so there's no
> > > > way to create non contiguous memory with this mix-cmos-e820-A
Hi,
> > > The premise that "this will also allow to pass non-contiguous memory"
> > > is partly false, as you can't use the e820 API below 4g so there's no
> > > way to create non contiguous memory with this mix-cmos-e820-API.
> >
> > Sure you can. Why do you think you can't?
>
> How do you s
On Thu, Oct 17, 2013 at 04:30:27PM +0200, Gerd Hoffmann wrote:
> On Do, 2013-10-17 at 15:00 +0200, Andrea Arcangeli wrote:
> > Hi,
> >
> > On Thu, Oct 17, 2013 at 01:09:38PM +0200, Gerd Hoffmann wrote:
> > > We have a fw_cfg entry to pass e820 entries from qemu to the firmware.
> > > Today it's us
On Do, 2013-10-17 at 15:00 +0200, Andrea Arcangeli wrote:
> Hi,
>
> On Thu, Oct 17, 2013 at 01:09:38PM +0200, Gerd Hoffmann wrote:
> > We have a fw_cfg entry to pass e820 entries from qemu to the firmware.
> > Today it's used to pass reservations only. This patch makes qemu pass
> > entries for R
Hi,
On Thu, Oct 17, 2013 at 01:09:38PM +0200, Gerd Hoffmann wrote:
> We have a fw_cfg entry to pass e820 entries from qemu to the firmware.
> Today it's used to pass reservations only. This patch makes qemu pass
> entries for RAM too.
>
> This allows to pass RAM sizes larger than 1TB to the firm