4 Commits

Author	SHA1	Message	Date
Yin Fengwei	8787b65fde	dm: fix the issue when guest tries to disable memory range access ... According to PCI spec 3.0 section 6.2.2 "Device Control", guest could write the command register to control device response to io/mem access. The origial code register/unregister the memory range which is not suitable because it can't handle the sequence: 1. disble the device response to specific memory range 2. reboot guest (DM will try to free the memory range which was freed in step 1 already) Tracked-On: #1277 Signed-off-by: Yin Fengwei <fengwei.yin@intel.com> Acked-by: Yu Wang <yu1.wang@intel.com>	2018-10-08 12:57:00 +08:00
Yonghua Huang	61cd6946d0	DM: Remove 'strictio' from UOS bootargs' options ... - UOS will boot fail if 'strictio' is enabled ('-e' option), in this case (with '-e'), device model will block all PIO accesses whose handlers were not registered, after that, device model program will exit, hence UOS boot fail. actually, such kind of accesses exist, e.g. UOS would program PIT registers (port address: 0x43) if hpet is disabled. - For debug, we can trap unexpected PIO access in 'default_inout()' Signed-off-by: Yonghua Huang <yonghua.huang@intel.com>	2018-07-02 12:33:52 +08:00
Yin Fengwei	c8585a22e3	DM: add deinit function for bvmcons ... Move the bvmcons enable flag from main.c to consport.c. So we don't need the flag in main.c for bvmcons. Signed-off-by: Yin Fengwei <fengwei.yin@intel.com> Acked-by: Anthony Xu <anthony.xu@intel.com>	2018-05-15 17:25:55 +08:00
Anthony Xu	bd31b1c53e	initial import ... internal commit: 0ab1ea615e5cfbb0687a9d593a86a7b774386076 Signed-off-by: Anthony Xu <anthony.xu@intel.com>	2018-05-11 14:44:28 +08:00