From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Please revert / review 077fc1c04d70ef1748ac2daa6622b3320a1a004c Date: Mon, 16 Jun 2014 09:08:40 +0100 Message-ID: <539EC228020000780001A7FC@mail.emea.novell.com> References: <5399828D02000078000B63B7@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Matthias , Yang Z Zhang Cc: "tim@xen.org" , "xen-devel@lists.xen.org" List-Id: xen-devel@lists.xenproject.org >>> On 16.06.14 at 09:47, wrote: > Matthias wrote on 2014-06-12: >> 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? It's not just that which is odd. The fault address is suspicious too; I only ever saw such along with discovering what led to 6b4d71d0 ("AMD IOMMU: don't free page table prematurely". Matthias - it certainly wouldn't hurt if you included that fix in whatever you build your hypervisor from (backports are already available in older trees). Jan Jan