xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Wang <wei.wang2@amd.com>
To: Sander Eikelenboom <linux@eikelenboom.it>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	Jan Beulich <JBeulich@suse.com>
Subject: Re: [PATCH] amd iommu: Dump flags of IO page faults
Date: Thu, 6 Sep 2012 15:32:51 +0200	[thread overview]
Message-ID: <5048A603.3070207@amd.com> (raw)
In-Reply-To: <326589347.20120906005936@eikelenboom.it>

On 09/06/2012 12:59 AM, Sander Eikelenboom wrote:
>
> Wednesday, September 5, 2012, 4:42:42 PM, you wrote:
>
>> Hi Jan,
>> Attached patch dumps io page fault flags. The flags show the reason of
>> the fault and tell us if this is an unmapped interrupt fault or a DMA fault.
>
>> Thanks,
>> Wei
>
>> signed-off-by: Wei Wang<wei.wang2@amd.com>
>
>
> I have applied the patch and the flags seem to differ between the faults:
>
> AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0a06, fault address = 0xc2c2c2c0, flags = 0x000
> (XEN) [2012-09-05 20:54:16] AMD-Vi: IO_PAGE_FAULT: domain = 0, device id = 0x0a06, fault address = 0xc2c2c2c0, flags = 0x000
> (XEN) [2012-09-05 20:54:16] AMD-Vi: IO_PAGE_FAULT: domain = 14, device id = 0x0700, fault address = 0xa8d339e0, flags = 0x020
> (XEN) [2012-09-05 20:54:16] AMD-Vi: IO_PAGE_FAULT: domain = 14, device id = 0x0700, fault address = 0xa8d33a40, flags = 0x020

OK, so they are not interrupt requests. I guess further information from 
your system would be helpful to debug this issue:
1) xl info
2) xl list
3) lscpi -vvv (NOTE: not in dom0 but in your guest)
4) cat /proc/iomem (in both dom0 and your hvm guest)

* I would also like to know the symptoms of device 0x0700 when IO_PF 
happened. Did it stop working?

(BTW: I copied a few options from your boot cmd line and it worked with 
my RD890 system

dom0_mem=1024M,max:1024M loglvl=all loglvl_guest=all console_timestamps 
cpuidle cpufreq=xen noreboot debug lapic=debug apic_verbosity=debug 
apic=debug iommu=on,verbose,debug,no-sharept

* so, what OEM board you have?)

Also from your log, these lines looks very strange:

(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xd5, mfn=0xa4a11
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xd7, mfn=0xa4a0f
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xd9, mfn=0xa4a0d
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xdb, mfn=0xa4a0b
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xdd, mfn=0xa4a09
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xdf, mfn=0xa4a07
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xe1, mfn=0xa4a05
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xe3, mfn=0xa4a03
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xe5, mfn=0xa4a01
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xe7, mfn=0xa463f
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xe9, mfn=0xa463d
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xeb, mfn=0xa463b
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xed, mfn=0xa4639
(XEN) [2012-09-04 15:54:35] hvm.c:2435:d15 guest attempted write to 
read-only memory page. gfn=0xef, mfn=0xa4637
(XEN) [2012-09-04 16:13:56] AMD-Vi: IO_PAGE_FAULT: domain = 0, device id 
= 0x0a06, fault address = 0xc2c2c2c0
(XEN) [2012-09-04 16:13:56] AMD-Vi: IO_PAGE_FAULT: domain = 14, device 
id = 0x0700, fault address = 0xa90f8300
(XEN) [2012-09-04 16:13:56] AMD-Vi: IO_PAGE_FAULT: domain = 14, device 
id = 0x0700, fault address = 0xa90f8340
(XEN) [2012-09-04 16:13:56] AMD-Vi: IO_PAGE_FAULT: domain = 14, device 
id = 0x0700, fault address = 0xa90f8380
(XEN) [2012-09-04 16:13:56] AMD-Vi: IO_PAGE_FAULT: domain = 14, device 
id = 0x0700, fault address = 0xa90f83c0

* they are just followed by the IO PAGE fault. Do you know where are 
they from? Your video card driver maybe?

Thanks,
Wei


> Complete xl dmesg and lspci -vvvknn attached.
>
> Thx
>
> --
> Sander

  reply	other threads:[~2012-09-06 13:32 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-05 14:42 [PATCH] amd iommu: Dump flags of IO page faults Wei Wang
2012-09-05 22:59 ` Sander Eikelenboom
2012-09-06 13:32   ` Wei Wang [this message]
2012-09-06 13:50     ` Sander Eikelenboom
2012-09-06 15:03       ` Wei Wang
2012-09-06 15:08         ` Sander Eikelenboom
2012-09-07  7:32         ` Sander Eikelenboom
2012-09-07  8:54           ` Wei Wang
2012-09-07 10:01             ` Sander Eikelenboom
2012-09-07 11:29               ` Jan Beulich
2012-09-07 20:51               ` Konrad Rzeszutek Wilk
2012-09-24  8:38             ` Sander Eikelenboom
2012-09-24 12:24               ` Wei Wang
     [not found]             ` <74647167 <506050F0.7020703@amd.com>
     [not found]               ` <74647167<506050F0.7020703@amd.com>
2012-09-24 12:27                 ` Sander Eikelenboom
2012-09-24 21:08                 ` Sander Eikelenboom
2012-10-01 15:02                 ` Sander Eikelenboom
2012-09-07  9:17           ` [PATCH] amd iommu: Dump flags of IO page faults (off topic - pci devices) Andrew Cooper
2012-09-07  9:53           ` [PATCH] amd iommu: Dump flags of IO page faults Jan Beulich
2012-09-07 10:00             ` Sander Eikelenboom
2012-09-07 10:06               ` Jan Beulich
2012-09-07 10:15                 ` Sander Eikelenboom
2012-09-07 11:17                   ` Jan Beulich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5048A603.3070207@amd.com \
    --to=wei.wang2@amd.com \
    --cc=JBeulich@suse.com \
    --cc=linux@eikelenboom.it \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).