According to Takao Indoh's testing, seems adding flush after loading old
irte and updating old irte does not fix the dmar faults.
According to Takao Indoh's log and your log, the faults happens while
and after driver is loaded. Maybe I am using incorrect code in 08/10.
On 01/06/2015 02:37 P
Hi Zhenhua,
I just tested your patchset based on 3.19.0-rc2+, and found several dmar
fault and intr-remap fault, it seems not the same as Takao's, please
check the attachment.
Thanks
Baoquan
[root@dhcp-16-105 ~]# kdumpctl restart
kexec: failed to unloaded kdump kernel
Stopping kdump: [FAILED]
+
Thank you very much for your help.
I have found there are several places need flush, and I will send a new
version
of this patchset with the flush functions.
Regards
Zhenhua
On 01/06/2015 08:18 AM, Takao Indoh wrote:
> On 2014/12/29 12:15, Li, ZhenHua wrote:
>> Hi Takao Indoh,
>>
>> Happy New Ye
On 2014/12/29 12:15, Li, ZhenHua wrote:
> Hi Takao Indoh,
>
> Happy New Year, and thank you very much for you help. The flush is quite
Happy new year!
> a problem, as there are several places the flush function should be called,
> I think the flush should be placed in functions like __iommu_
Hi Takao Indoh,
Happy New Year, and thank you very much for you help. The flush is quite
a problem, as there are several places the flush function should be called,
I think the flush should be placed in functions like __iommu_update_old_*.
Created a small patch for this, it is attached.
A
On 2014/12/26 15:46, Li, ZhenHua wrote:
> Hi Takao Indoh,
>
> Thank you very much for your testing. I will add your update in next
> version.
> Also I think a flush for __iommu_update_old_root_entry is also necessary.
>
> Currently I have no idea about your fault, does it happen before or
> durin
Hi Takao Indoh,
Thank you very much for your testing. I will add your update in next
version.
Also I think a flush for __iommu_update_old_root_entry is also necessary.
Currently I have no idea about your fault, does it happen before or
during its loading? Could you send me your full kernel log as
Hi Zhen-Hua,
I tested your patch and found two problems.
[1]
Kenel panic occurs during 2nd kernel boot.
..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1
Kernel panic - not syncing: timer doesn't work through Interrupt-remapped
IO-APIC
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.18.0 #25
Har
This version works for 3.19.0-rc1.
Zhenhua
On 12/22/2014 05:15 PM, Li, Zhen-Hua wrote:
This patchset is an update of Bill Sumner's patchset, implements a fix for:
If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
when a panic happens, the kdump kernel will boot with the
This patchset is an update of Bill Sumner's patchset, implements a fix for:
If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
when a panic happens, the kdump kernel will boot with these faults:
dmar: DRHD: handling fault status reg 102
dmar: DMAR:[DMA Read] Reque
This patchset is an update of Bill Sumner's patchset, implements a fix for:
If a kernel boots with intel_iommu=on on a system that supports intel vt-d,
when a panic happens, the kdump kernel will boot with these faults:
dmar: DRHD: handling fault status reg 102
dmar: DMAR:[DMA Read] Reque
11 matches
Mail list logo