1. 22 6月, 2011 1 次提交
  2. 21 6月, 2011 1 次提交
  3. 20 6月, 2011 4 次提交
  4. 19 6月, 2011 1 次提交
  5. 18 6月, 2011 1 次提交
  6. 17 6月, 2011 1 次提交
    • K
      xen/setup: Fix for incorrect xen_extra_mem_start. · acd049c6
      Konrad Rzeszutek Wilk 提交于
      The earlier attempts (24bdb0b6)
      at fixing this problem caused other problems to surface (PV guests
      with no PCI passthrough would have SWIOTLB turned on - which meant
      64MB of precious contingous DMA32 memory being eaten up per guest).
      The problem was: "on xen we add an extra memory region at the end of
      the e820, and on this particular machine this extra memory region
      would start below 4g and cross over the 4g boundary:
      
      [0xfee01000-0x192655000)
      
      Unfortunately e820_end_of_low_ram_pfn does not expect an
      e820 layout like that so it returns 4g, therefore initial_memory_mapping
      will map [0 - 0x100000000), that is a memory range that includes some
      reserved memory regions."
      
      The memory range was the IOAPIC regions, and with the 1-1 mapping
      turned on, it would map them as RAM, not as MMIO regions. This caused
      the hypervisor to complain. Fortunately this is experienced only under
      the initial domain so we guard for it.
      Acked-by: NStefano Stabellini <stefano.stabellini@eu.citrix.com>
      Signed-off-by: NKonrad Rzeszutek Wilk <konrad.wilk@oracle.com>
      acd049c6
  7. 16 6月, 2011 7 次提交
  8. 15 6月, 2011 2 次提交
  9. 14 6月, 2011 16 次提交
  10. 13 6月, 2011 1 次提交
  11. 12 6月, 2011 1 次提交
  12. 11 6月, 2011 3 次提交
  13. 10 6月, 2011 1 次提交