Hi,
> BTW: what about OVMF and core boot, how would they know that there is more
> then 1Tb RAM?
They should look at fw_cfg too. Both have support for fw_cfg already,
but don't parse the e820 table today. Shouldn't be that hard to add
though.
cheers,
Gerd
On Fri, 11 Oct 2013 14:27:12 +0200
Gerd Hoffmann wrote:
> On Fr, 2013-10-11 at 13:20 +0200, Igor Mammedov wrote:
> > On Thu, 10 Oct 2013 14:54:29 +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 reserva
On Fr, 2013-10-11 at 13:20 +0200, Igor Mammedov wrote:
> On Thu, 10 Oct 2013 14:54:29 +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.
> >
On Thu, 10 Oct 2013 14:54:29 +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 firmware and i
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 firmware and it
will also allow to pass non-contignous memory ramges should we dec
