Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Wu, Feng]

> -Original Message-
> From: Dario Faggioli [mailto:dario.faggi...@citrix.com]
> Sent: Friday, May 27, 2016 12:11 AM
> To: Wu, Feng <feng...@intel.com>; Wei Liu <wei.l...@citrix.com>
> Cc: Xen-devel <xen-de...@lists.xenproject.org>; Hao, Xudong
> <xudong....@intel.com>
> Subject: Re: [Xen-devel] [BUG] Xen panic with VT-d PI
> 
> On Thu, 2016-05-26 at 13:03 +, Wu, Feng wrote:
> > > On Thu, May 26, 2016 at 01:56:28AM +, Wu, Feng wrote:
> > > >
> > > > The patch fixing this issue has already been sent to upstream.
> > > >
> > > > " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu
> > > > blocking list "
> > > >
> > > > v2 will be sent out soon.
> > > >
> > > I just went through that thread. There are some open questions.
> > > Also Jan
> > > requested that you explore other possible options.
> > >
> > > My current plan is to not block the release for this -- we're very
> > > close
> > > to the anticipated release date, and posted-interrupt is either
> > > technical preview or experimental, so bugs there are expected.
> > >
> > > This issue will be listed as a known issue for PI. And you can
> > > continue
> > > to develop a fix for it. Your fix will be integrated with next
> > > version
> > > of Xen. Then you can request for backport to 4.7 if you want to.
> > >
> > > What do you think about this plan?
> > I am going to send out the next version of this series, let's see how
> > it is going on. But basically, I am fine with your release plan.
> >
> This does not have anything to do with Wei's plan (with which I also
> agree), but are you sure that the bug being reported here is related to
> and would be fixed by the patch you're mentioning?

Yes, this bug is caused by device hotplug, which is fixed in this patch
set.

> 
> Have you also seen it, and is that what led to the patch? If yes,
> please, add a bit more information (including excerpts of, or insights
> about the splat) in the patch changelog.

The bug leads to this patch, and I also saw issues beyond it, such as,
the domain destroy, pCPU hotplug cases. Sure, I will add some info
about it in the next version.

Thanks,
Feng

> 
> Regards,
> Dario
> --
> <> (Raistlin Majere)
> -
> Dario Faggioli, Ph.D, http://about.me/dario.faggioli
> Senior Software Engineer, Citrix Systems R Ltd., Cambridge (UK)

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Dario Faggioli]

On Thu, 2016-05-26 at 13:03 +, Wu, Feng wrote:
> > On Thu, May 26, 2016 at 01:56:28AM +, Wu, Feng wrote:
> > > 
> > > The patch fixing this issue has already been sent to upstream.
> > > 
> > > " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu
> > > blocking list "
> > > 
> > > v2 will be sent out soon.
> > > 
> > I just went through that thread. There are some open questions.
> > Also Jan
> > requested that you explore other possible options.
> > 
> > My current plan is to not block the release for this -- we're very
> > close
> > to the anticipated release date, and posted-interrupt is either
> > technical preview or experimental, so bugs there are expected.
> > 
> > This issue will be listed as a known issue for PI. And you can
> > continue
> > to develop a fix for it. Your fix will be integrated with next
> > version
> > of Xen. Then you can request for backport to 4.7 if you want to.
> > 
> > What do you think about this plan?
> I am going to send out the next version of this series, let's see how
> it is going on. But basically, I am fine with your release plan.
> 
This does not have anything to do with Wei's plan (with which I also
agree), but are you sure that the bug being reported here is related to
and would be fixed by the patch you're mentioning?

Have you also seen it, and is that what led to the patch? If yes,
please, add a bit more information (including excerpts of, or insights
about the splat) in the patch changelog.

Regards,
Dario
-- 
<> (Raistlin Majere)
-
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R Ltd., Cambridge (UK)



signature.asc
Description: This is a digitally signed message part
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Wei Liu]

On Thu, May 26, 2016 at 01:03:53PM +, Wu, Feng wrote:
> 
> 
> > -Original Message-
> > From: Wei Liu [mailto:wei.l...@citrix.com]
> > Sent: Thursday, May 26, 2016 6:27 PM
> > To: Wu, Feng 
> > Cc: Hao, Xudong ; Xen-devel  > de...@lists.xenproject.org>; Wei Liu 
> > Subject: Re: [BUG] Xen panic with VT-d PI
> > 
> > On Thu, May 26, 2016 at 01:56:28AM +, Wu, Feng wrote:
> > > The patch fixing this issue has already been sent to upstream.
> > >
> > > " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu blocking 
> > > list "
> > >
> > > v2 will be sent out soon.
> > >
> > 
> > I just went through that thread. There are some open questions. Also Jan
> > requested that you explore other possible options.
> > 
> > My current plan is to not block the release for this -- we're very close
> > to the anticipated release date, and posted-interrupt is either
> > technical preview or experimental, so bugs there are expected.
> > 
> > This issue will be listed as a known issue for PI. And you can continue
> > to develop a fix for it. Your fix will be integrated with next version
> > of Xen. Then you can request for backport to 4.7 if you want to.
> > 
> > What do you think about this plan?
> 
> I am going to send out the next version of this series, let's see how
> it is going on. But basically, I am fine with your release plan.
> 

Ack. Thanks for confirming.

Wei.

> Thanks,
> Feng
> 
> > 
> > Wei.
> > 
> > > Thanks,
> > > Feng

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Wu, Feng]

> -Original Message-
> From: Wei Liu [mailto:wei.l...@citrix.com]
> Sent: Thursday, May 26, 2016 6:27 PM
> To: Wu, Feng 
> Cc: Hao, Xudong ; Xen-devel  de...@lists.xenproject.org>; Wei Liu 
> Subject: Re: [BUG] Xen panic with VT-d PI
> 
> On Thu, May 26, 2016 at 01:56:28AM +, Wu, Feng wrote:
> > The patch fixing this issue has already been sent to upstream.
> >
> > " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu blocking list "
> >
> > v2 will be sent out soon.
> >
> 
> I just went through that thread. There are some open questions. Also Jan
> requested that you explore other possible options.
> 
> My current plan is to not block the release for this -- we're very close
> to the anticipated release date, and posted-interrupt is either
> technical preview or experimental, so bugs there are expected.
> 
> This issue will be listed as a known issue for PI. And you can continue
> to develop a fix for it. Your fix will be integrated with next version
> of Xen. Then you can request for backport to 4.7 if you want to.
> 
> What do you think about this plan?

I am going to send out the next version of this series, let's see how
it is going on. But basically, I am fine with your release plan.

Thanks,
Feng

> 
> Wei.
> 
> > Thanks,
> > Feng

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Wei Liu]

On Thu, May 26, 2016 at 01:56:28AM +, Wu, Feng wrote:
> The patch fixing this issue has already been sent to upstream.
> 
> " [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu blocking list "
> 
> v2 will be sent out soon.
> 

I just went through that thread. There are some open questions. Also Jan
requested that you explore other possible options.

My current plan is to not block the release for this -- we're very close
to the anticipated release date, and posted-interrupt is either
technical preview or experimental, so bugs there are expected.

This issue will be listed as a known issue for PI. And you can continue
to develop a fix for it. Your fix will be integrated with next version
of Xen. Then you can request for backport to 4.7 if you want to.

What do you think about this plan?

Wei.

> Thanks,
> Feng

___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: [Xen-devel] [BUG] Xen panic with VT-d PI

[Wu, Feng]

The patch fixing this issue has already been sent to upstream.

" [PATCH 0/3] VMX: Properly handle pi descriptor and per-cpu blocking list "

v2 will be sent out soon.

Thanks,
Feng

> -Original Message-
> From: Hao, Xudong
> Sent: Thursday, May 26, 2016 9:45 AM
> To: Xen-devel 
> Cc: Wu, Feng ; Wei Liu 
> Subject: [BUG] Xen panic with VT-d PI
> 
> Xen 4.7 RC3 enabled VT-d PI(iommu=on,intpost), and created HVM guest with VF
> NIC assigned repeatedly, it will cause Xen panic(maybe 2 times ,5 times ,10
> times).
> It's not a RC3 regression, at least this Xen commit 1bd52e1f got failure as 
> well.
> 
> HW: Intel Broadwell server, Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz.
> Xen: Xen 4.7.0 RC3
> Dom0: Linux 4.4.4
> VF: Intel 82599 NIC
> 
> ...
> (XEN) irq.c:275: Dom8 PCI link 3 changed 5 -> 0
> [ 1319.177226] ixgbe :05:00.0 eth30: VF Reset msg received from vf 1
> [ 1321.949952] ixgbe :05:00.0 eth30: 1 Spoofed packets detected
> (XEN) [ Xen-4.7-unstable  x86_64  debug=y  Tainted:C ]
> (XEN) CPU:3
> (XEN) RIP:e008:[] vmx.c#pi_wakeup_interrupt+0xcf/0x15b
> (XEN) RFLAGS: 00010002   CONTEXT: hypervisor
> (XEN) rax: 830078a71760   rbx: 01001001000fff60   rcx: 0003
> (XEN) rdx: 0100100100100100   rsi: 0046   rdi: 830078a715c0
> (XEN) rbp: 83043c477d18   rsp: 83043c477ce8   r8:  0003
> (XEN) r9:  830425ae2710   r10: 830425ae28e0   r11: 01354d22b2fb
> (XEN) r12: 83043c47dde0   r13: 83043c47ddf0   r14: 0100100100100100
> (XEN) r15: 0200200200200200   cr0: 8005003b   cr4:
> 003526e0
> (XEN) cr3: 000424276000   cr2: 003abfaaca80
> (XEN) ds:    es:    fs:    gs:    ss:    cs: e008
> (XEN) Xen code around 
> (vmx.c#pi_wakeup_interrupt+0xcf/0x15b):
> (XEN)  00 5a 48 8b 97 a0 01 00 <48> 3b 42 08 74 04 0f 0b eb fe 48 8b 8f a8 01 
> 00
> (XEN) Xen stack trace from rsp=83043c477ce8:
> (XEN)83043c477d08 00f5 83043c477db8
> 00f5
> (XEN)83043c47f788  83043c477da8 82d080171c7a
> (XEN)  deadbeefdeadf00d
> 8300782fe000
> (XEN)0003 830422e7 
> 80003c477d90
> (XEN)82d0801949fa 8c7adb3d0002 83043c477e18
> 0135394f6d83
> (XEN)83043c47f6d0 82d080807280 83043c47f788 
> (XEN)7cfbc3b88227 82d08023feb2  83043c47f788
> (XEN)82d080807280 83043c47f6d0 83043c477ee0
> 0135394f6d83
> (XEN)01354d22b2fb 830425ae28e0 830425ae2710
> 0001
> (XEN)0008 20c49ba5e353f7cf 83043c47
> 0135394f6d83
> (XEN)83043c47f700 00f5 82d0801ba6d2
> e008
> (XEN)0286 83043c477e60 
> 00080020
> (XEN)013534e2391b  830078a71000 81c17dc0
> (XEN)83043c477f08  
> 82d080832980
> (XEN)1eba6a07  83043c477f18 82d080807280
> (XEN)83043c477f18 830078a71000 83043c423000 83043c477f10
> (XEN)82d0801660fd 81df8000 8300782fe000 0003
> (XEN)830422e7 83043c477d78 81df8000 
> (XEN) 81c17dc0 81a03ea8
> 
> (XEN) 0002d788742b 
> 
> (XEN) Xen call trace:
> (XEN)[] vmx.c#pi_wakeup_interrupt+0xcf/0x15b
> (XEN)[] do_IRQ+0x9d/0x65e
> (XEN)[] common_interrupt+0x62/0x70
> (XEN)[] mwait-idle.c#mwait_idle+0x2b3/0x30a
> (XEN)[] domain.c#idle_loop+0x6c/0x89
> (XEN)
> (XEN)
> (XEN) 
> (XEN) Panic on CPU 3:
> (XEN) GENERAL PROTECTION FAULT
> (XEN) [error_code=]
> (XEN) 
> (XEN)
> (XEN) Reboot in five seconds...
> 
> 
> Best Regards,
> Xudong


___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

[Xen-devel] [BUG] Xen panic with VT-d PI

[Hao, Xudong]

Xen 4.7 RC3 enabled VT-d PI(iommu=on,intpost), and created HVM guest with VF 
NIC assigned repeatedly, it will cause Xen panic(maybe 2 times ,5 times ,10 
times).
It's not a RC3 regression, at least this Xen commit 1bd52e1f got failure as 
well.

HW: Intel Broadwell server, Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz. 
Xen: Xen 4.7.0 RC3
Dom0: Linux 4.4.4
VF: Intel 82599 NIC

...
(XEN) irq.c:275: Dom8 PCI link 3 changed 5 -> 0
[ 1319.177226] ixgbe :05:00.0 eth30: VF Reset msg received from vf 1
[ 1321.949952] ixgbe :05:00.0 eth30: 1 Spoofed packets detected
(XEN) [ Xen-4.7-unstable  x86_64  debug=y  Tainted:C ]
(XEN) CPU:3
(XEN) RIP:e008:[] vmx.c#pi_wakeup_interrupt+0xcf/0x15b
(XEN) RFLAGS: 00010002   CONTEXT: hypervisor
(XEN) rax: 830078a71760   rbx: 01001001000fff60   rcx: 0003
(XEN) rdx: 0100100100100100   rsi: 0046   rdi: 830078a715c0
(XEN) rbp: 83043c477d18   rsp: 83043c477ce8   r8:  0003
(XEN) r9:  830425ae2710   r10: 830425ae28e0   r11: 01354d22b2fb
(XEN) r12: 83043c47dde0   r13: 83043c47ddf0   r14: 0100100100100100
(XEN) r15: 0200200200200200   cr0: 8005003b   cr4: 003526e0
(XEN) cr3: 000424276000   cr2: 003abfaaca80
(XEN) ds:    es:    fs:    gs:    ss:    cs: e008
(XEN) Xen code around  (vmx.c#pi_wakeup_interrupt+0xcf/0x15b):
(XEN)  00 5a 48 8b 97 a0 01 00 <48> 3b 42 08 74 04 0f 0b eb fe 48 8b 8f a8 01 00
(XEN) Xen stack trace from rsp=83043c477ce8:
(XEN)83043c477d08 00f5 83043c477db8 00f5
(XEN)83043c47f788  83043c477da8 82d080171c7a
(XEN)  deadbeefdeadf00d 8300782fe000
(XEN)0003 830422e7  80003c477d90
(XEN)82d0801949fa 8c7adb3d0002 83043c477e18 0135394f6d83
(XEN)83043c47f6d0 82d080807280 83043c47f788 
(XEN)7cfbc3b88227 82d08023feb2  83043c47f788
(XEN)82d080807280 83043c47f6d0 83043c477ee0 0135394f6d83
(XEN)01354d22b2fb 830425ae28e0 830425ae2710 0001
(XEN)0008 20c49ba5e353f7cf 83043c47 0135394f6d83
(XEN)83043c47f700 00f5 82d0801ba6d2 e008
(XEN)0286 83043c477e60  00080020
(XEN)013534e2391b  830078a71000 81c17dc0
(XEN)83043c477f08   82d080832980
(XEN)1eba6a07  83043c477f18 82d080807280
(XEN)83043c477f18 830078a71000 83043c423000 83043c477f10
(XEN)82d0801660fd 81df8000 8300782fe000 0003
(XEN)830422e7 83043c477d78 81df8000 
(XEN) 81c17dc0 81a03ea8 
(XEN) 0002d788742b  
(XEN) Xen call trace:
(XEN)[] vmx.c#pi_wakeup_interrupt+0xcf/0x15b
(XEN)[] do_IRQ+0x9d/0x65e
(XEN)[] common_interrupt+0x62/0x70
(XEN)[] mwait-idle.c#mwait_idle+0x2b3/0x30a
(XEN)[] domain.c#idle_loop+0x6c/0x89
(XEN)
(XEN)
(XEN) 
(XEN) Panic on CPU 3:
(XEN) GENERAL PROTECTION FAULT
(XEN) [error_code=]
(XEN) 
(XEN)
(XEN) Reboot in five seconds...


Best Regards,
Xudong



config.vmxvtd_ass_02
Description: config.vmxvtd_ass_02
___
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel