[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-devel] Please revert / review 077fc1c04d70ef1748ac2daa6622b3320a1a004c
Matthias wrote on 2014-06-12: > Yes, I'm seeing the > (XEN) testing: enable log dirty mode > > in xl dmesg. I cannot understand why log dirty is used in AMD gfx passthrough. > > > Also, here are logs and additional information from a start with a xen > build up to the 077fc1c changeset. DomU Name is WORK. > > I haven't attached a xl dmesg log because it was only filled with this: It's better to attach the whole log since there are some debug messages which are useful. If the log buffer isn't enough, please add conring_size=xxM to Xen cmd line. > > domain = 0, device id = 0x98, fault address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x90, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x98, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x90, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x98, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x90, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x98, fault > address = 0xffffffc0, flags = 0 > (XEN) AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x90, fault > address = 0xffffffc0, flags = 0 This is really strange. The fault shows it is caused by dom0's activity. But the device have assigned to the guest. Are you sure the devices(00:13.0 and 00:12.0) are hidden and dom0 is not using it? BTW, what are the devices of 00:12.0 and 00:13.0? Best regards, Yang _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |