On 2012-01-31 13:51, Avi Kivity wrote: > On 01/31/2012 02:45 PM, Jan Kiszka wrote: >> On 2012-01-31 13:40, Avi Kivity wrote: >>> On 01/28/2012 04:21 PM, Alex Williamson wrote: >>>> To date we've only exposed BARs as 32bit even if the device >>>> physically supports 64bit BARs. Enable 64bit BARs to be >>>> exposed as such in the guest, which may free up MMIO below >>>> 4G should the guest choose to use it. >>>> >>>> This adds a new mem64= option to pci-assign, with the >>>> default being off for testing and enablement. The goal >>>> is to eventually make this enabled by default. >>>> >>> >>> Seems fine, but do we really need the option? If it doesn't work we >>> should treat it as an ordinary but and fix it. >> >> So far it's against the architecture of the emulated system: our current >> chipset predates 64 bit PCI. >> > > Then it should be enabled/disabled at the chipset level. Makes me wonder if we already do some filtering if the device supports 64 bit but the next bridge does not. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
