Hi, > > > But RamSizeOver4G still doesn't allow correctly place PCI window if large > > > amount of memory present/reserved. > > BTW: I don't think it's good practice to change semantics of an old > > interface > > in general. It's less confusing to leave old interface as is (obsoleting it > > eventually) and use a new one.
> I agree. The RamSizeOver4G (as passed via three cmos bytes) is ugly - > lets not make it more complex. Also it would mix up two different (although related) things: Actual memory and reserving address space for memory (which then might be hotplugged). > Any new info can be passed via fw_cfg. Plan is to extend the existing e820 table passed from qemu. Today it carries reservations only. We can stick ram ranges in there too. cheers, Gerd
