> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Monday, March 09, 2015 7:46 PM
> To: Tim Deegan; Wu, Feng
> Cc: Zhang, Yang Z; Tian, Kevin; Jan Beulich; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VT-d Posted-interrupt (
> -Original Message-
> From: Tian, Kevin
> Sent: Tuesday, March 10, 2015 10:22 AM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Jan Beulich; Zhang, Yang Z
> Subject: RE: VT-d Posted-interrupt (PI) design for XEN
>
> > From: Wu, Feng
> > Sent: Wednesday, March 04, 2015 9:30 PM
> >
> > VT-
> -Original Message-
> From: Tian, Kevin
> Sent: Tuesday, March 10, 2015 10:01 AM
> To: Andrew Cooper; Tim Deegan; Wu, Feng
> Cc: Zhang, Yang Z; Jan Beulich; xen-devel@lists.xen.org
> Subject: RE: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
>
&g
> From: Wu, Feng
> Sent: Wednesday, March 04, 2015 9:30 PM
>
> 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 (suc
Tim Deegan [mailto:t...@xen.org]
> >>> Sent: Friday, March 06, 2015 5:44 PM
> >>> To: Wu, Feng
> >>> Cc: Jan Beulich; Zhang, Yang Z; Tian, Kevin; xen-devel@lists.xen.org
> >>> Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
&g
Cc: Jan Beulich; Zhang, Yang Z; Tian, Kevin; xen-devel@lists.xen.org
>>> Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
>>>
>>> At 02:07 + on 06 Mar (1425604054), Wu, Feng wrote:
>>>>> From: Tim Deegan [mailto:t...@xen.org]
>>>>>
.org
> > Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
> >
> > At 02:07 + on 06 Mar (1425604054), Wu, Feng wrote:
> > > > From: Tim Deegan [mailto:t...@xen.org]
> > > > But I don't understand why we would need a new global vecto
> -Original Message-
> From: Tim Deegan [mailto:t...@xen.org]
> Sent: Friday, March 06, 2015 5:44 PM
> To: Wu, Feng
> Cc: Jan Beulich; Zhang, Yang Z; Tian, Kevin; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
>
>
At 02:07 + on 06 Mar (1425604054), Wu, Feng wrote:
> > From: Tim Deegan [mailto:t...@xen.org]
> > But I don't understand why we would need a new global vector for
> > RUNSTATE_blocked rather than suppressing the posted interrupts as you
> > suggest for RUNSTATE_runnable. (Or conversely why not
> -Original Message-
> From: Tim Deegan [mailto:t...@xen.org]
> Sent: Thursday, March 05, 2015 8:03 PM
> To: Jan Beulich
> Cc: Wu, Feng; Zhang, Yang Z; Tian, Kevin; xen-devel@lists.xen.org
> Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for XEN
>
>
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, March 05, 2015 6:15 PM
> To: Wu, Feng
> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org
> Subject: RE: VT-d Posted-interrupt (PI) design for XEN
>
> >>> On 05.03.15 at 10:07, wrote:
> >> From:
Hi,
At 08:52 + on 05 Mar (1425541947), Jan Beulich wrote:
> >>> On 05.03.15 at 09:29, wrote:
> >> From: Jan Beulich [mailto:jbeul...@suse.com]
> >> Sent: Thursday, March 05, 2015 3:13 PM
> >> And if it can know, why couldn't the handler for
> >> posted_intr_vector not know either (i.e. after
>>> On 05.03.15 at 10:07, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, March 05, 2015 4:52 PM
>> And how would this be different with your separate new vector? I
>> feel I'm missing something, but I'm afraid I have to rely on you to
>> point out what it is. Just again
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, March 05, 2015 4:52 PM
> To: Wu, Feng
> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org
> Subject: RE: VT-d Posted-interrupt (PI) design for XEN
>
> >>> On 05.03.15 at 09:29, wrote:
> >> From:
>>> On 05.03.15 at 09:29, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Thursday, March 05, 2015 3:13 PM
>> And if it can know, why couldn't the handler for
>> posted_intr_vector not know either (i.e. after introducing a specific
>> handler for it in place of the currently used e
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Thursday, March 05, 2015 3:13 PM
> To: Wu, Feng
> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org
> Subject: RE: VT-d Posted-interrupt (PI) design for XEN
>
> >>> On 05.03.15 at 06:04, wrote:
> >> From:
>>> On 05.03.15 at 06:04, wrote:
>> From: Jan Beulich [mailto:jbeul...@suse.com]
>> Sent: Wednesday, March 04, 2015 11:19 PM
>> >>> On 04.03.15 at 14:30, wrote:
>> > - Introduce a new global vector which is used to wake up the HLT'ed vCPU.
>> > Currently, there is a global vector 'posted_intr_vec
> -Original Message-
> From: Andrew Cooper [mailto:andrew.coop...@citrix.com]
> Sent: Thursday, March 05, 2015 2:48 AM
> To: Wu, Feng; xen-devel@lists.xen.org
> Cc: Zhang, Yang Z; Tian, Kevin; Jan Beulich
> Subject: Re: [Xen-devel] VT-d Posted-interrupt (PI) design for
> -Original Message-
> From: Jan Beulich [mailto:jbeul...@suse.com]
> Sent: Wednesday, March 04, 2015 11:19 PM
> To: Wu, Feng
> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@lists.xen.org
> Subject: Re: VT-d Posted-interrupt (PI) design for XEN
>
> >>> On 04.03.15 at 14:30, wrote:
> > - Int
On 04/03/15 13:30, Wu, Feng wrote:
> VT-d Posted-interrupt (PI) design for XEN
Thankyou very much for this!
>
> Background
> ==
> With the development of virtualization, there are more and more device
> assignment requirements. However, today when a VM is running with
> assigned devices (
>>> On 04.03.15 at 14:30, wrote:
> - Introduce a new global vector which is used to wake up the HLT'ed vCPU.
> Currently, there is a global vector 'posted_intr_vector', which is used as
> the
> global notification vector for all vCPUs in the system. This vector is
> stored in
> VMCS and CPU cons
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
22 matches
Mail list logo
