> -----Original Message-----
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: 05 October 2018 17:04
> To: Paul Durrant <paul.durr...@citrix.com>
> Cc: xen-devel@lists.xenproject.org; Stefano Stabellini
> <sstabell...@kernel.org>; Jun Nakajima <jun.nakaj...@intel.com>; George
> Dunlap <george.dun...@citrix.com>; Andrew Cooper
> <andrew.coop...@citrix.com>; Jan Beulich <jbeul...@suse.com>; Wei Liu
> <wei.l...@citrix.com>
> Subject: Re: [Xen-devel] [PATCH v14 8/9] mm / iommu: include need_iommu()
> test in iommu_use_hap_pt()
> 
> This patch has broken my PVH Dom0 setup.

Hmm. This is probably a bug in the need_iommu() setting for dom0. Do you still 
see the problem with the subsequent patch " mm / iommu: split need_iommu() into 
has_iommu_pt()..." applied too?

  Paul 

> 
> [    2.515159] igb 0000:02:00.1: added PHC on eth1
> [    2.519539] igb 0000:02:00.1: Intel(R) Gigabit Ethernet Network
> Connection
> [    2.526469] igb 0000:02:00.1: eth1: (PCIe:5.0Gb/s:Width x4)
> 0c:c4:7a:e7:b6:53
> [    2.533733] igb 0000:02:00.1: eth1: PBA No: 010A00-000
> [    2.538860] igb 0000:02:00.1: Using MSI-X interrupts. 8 rx queue(s), 8
> tx queue(s)
> [    2.649191] ata8: SATA link down (SStatus 0 SControl 300)
> [    2.654467] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    2.660730] ata7: SATA link down (SStatus 0 SControl 300)
> [    2.666166] ata5: SATA link down (SStatus 0 SControl 300)
> [    2.671619] ata3: SATA link down (SStatus 0 SControl 300)
> [    2.677073] ata6: SATA link down (SStatus 0 SControl 300)
> [    2.682538] ata2: SATA link down (SStatus 0 SControl 300)
> [    2.687988] ata4: SATA link down (SStatus 0 SControl 300)
> [    2.694632] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> [    8.215728] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [    8.222945] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> [    8.229052] ata1: limiting SATA link speed to 1.5 Gbps
> [   13.590991] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
> [   13.597142] ata1.00: failed to IDENTIFY (I/O error, err_mask=0x100)
> 
> Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

Reply via email to