Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-25 Thread Jan Beulich
>>> On 25.03.15 at 06:10, wrote: > Do you think it is good for you guys to continue the review if I send out > a RFC patch for this feature? Yes, I think this would make sense. Jan ___ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.o

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-24 Thread Wu, Feng
Hi Jan & other maintainers, Do you think it is good for you guys to continue the review if I send out a RFC patch for this feature? Thanks, Feng > -Original Message- > From: Wu, Feng > Sent: Wednesday, March 18, 2015 8:44 PM > To: xen-devel@lists.xen.org > Cc: Keir Fraser (k...@xen.org);

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Wu, Feng
> -Original Message- > From: Tian, Kevin > Sent: Tuesday, March 24, 2015 11:06 AM > To: Wu, Feng; Jan Beulich > Cc: Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser (k...@xen.org) > Subject: RE: (v2) VT-d Posted-interrupt (PI) design for XEN > > > From: Wu, Feng > > Sent: Monday, Marc

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Tian, Kevin
> From: Wu, Feng > Sent: Monday, March 23, 2015 5:19 PM > > > > > -Original Message- > > From: Jan Beulich [mailto:jbeul...@suse.com] > > Sent: Monday, March 23, 2015 5:08 PM > > To: Wu, Feng > > Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser > > (k...@xen.org) > >

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Wu, Feng
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Monday, March 23, 2015 5:08 PM > To: Wu, Feng > Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser > (k...@xen.org) > Subject: RE: (v2) VT-d Posted-interrupt (PI) design for XEN > > >>> On 23.03

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Jan Beulich
>>> On 23.03.15 at 09:49, wrote: > >> -Original Message- >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: Monday, March 23, 2015 4:26 PM >> To: Wu, Feng >> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser >> (k...@xen.org) >> Subject: RE: (v2) VT-d Posted-inte

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Wu, Feng
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Monday, March 23, 2015 4:26 PM > To: Wu, Feng > Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser > (k...@xen.org) > Subject: RE: (v2) VT-d Posted-interrupt (PI) design for XEN > > >>> On 23.03

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Jan Beulich
>>> On 23.03.15 at 09:14, wrote: >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: Thursday, March 19, 2015 5:57 PM >> >>> On 18.03.15 at 13:44, wrote: >> > Here are what we do for the blocked vCPU: >> > 1. Define a per-cpu list 'blocked_vcpu_on_cpu', which stored the blocked >> > vCPU on

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Wu, Feng
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: Thursday, March 19, 2015 5:57 PM > To: Wu, Feng > Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org; Keir Fraser > (k...@xen.org) > Subject: Re: (v2) VT-d Posted-interrupt (PI) design for XEN > > >>> On 18.

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-23 Thread Wu, Feng
gt; > > Sent: Thursday, March 19, 2015 12:10 AM > > > To: Wu, Feng > > > Cc: xen-devel@lists.xen.org; Zhang, Yang Z; Tian, Kevin; Keir Fraser > > > (k...@xen.org); Jan Beulich (jbeul...@suse.com) > > > Subject: Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) de

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-19 Thread Konrad Rzeszutek Wilk
l@lists.xen.org; Zhang, Yang Z; Tian, Kevin; Keir Fraser > > (k...@xen.org); Jan Beulich (jbeul...@suse.com) > > Subject: Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN > > > > On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote: > >

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-19 Thread Jan Beulich
>>> On 18.03.15 at 13:44, wrote: > Here are what we do for the blocked vCPU: > 1. Define a per-cpu list 'blocked_vcpu_on_cpu', which stored the blocked > vCPU on the pCPU. > 2. When the vCPU's state is changed to RUNSTATE_blocked, insert the vCPU > to the per-cpu list belonging to the pCPU it was

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-18 Thread Wu, Feng
(jbeul...@suse.com) > Subject: Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN > > On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote: > > VT-d Posted-interrupt (PI) design for XEN > > > > Background > > == > > With the deve

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-18 Thread Zhang, Yang Z
Konrad Rzeszutek Wilk wrote on 2015-03-19: > On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote: >> VT-d Posted-interrupt (PI) design for XEN >> >> Background >> == >> With the development of virtualization, there are more and more >> device assignment requirements. However, today wh

Re: [Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-18 Thread Konrad Rzeszutek Wilk
On Wed, Mar 18, 2015 at 12:44:21PM +, Wu, Feng wrote: > VT-d Posted-interrupt (PI) design for XEN > > Background > == > With the development of virtualization, there are more and more device > assignment requirements. However, today when a VM is running with > assigned devices (such as

[Xen-devel] (v2) VT-d Posted-interrupt (PI) design for XEN

2015-03-18 Thread Wu, Feng
VT-d Posted-interrupt (PI) design for XEN Background == With the development of virtualization, there are more and more device assignment requirements. However, today when a VM is running with assigned devices (such as, NIC), external interrupt handling for the assigned devices always need