[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

> -----Original Message-----
> From: Jan Beulich [mailto:JBeulich@xxxxxxxx]
> Sent: Thursday, March 19, 2015 5:57 PM
> To: Wu, Feng
> Cc: Tian, Kevin; Zhang, Yang Z; xen-devel@xxxxxxxxxxxxx; Keir Fraser
> (keir@xxxxxxx)
> Subject: Re: (v2) VT-d Posted-interrupt (PI) design for XEN
> >>> On 18.03.15 at 13:44, <feng.wu@xxxxxxxxx> 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 running.
> > 3. When the vCPU is unblocked, remove the vCPU from the related pCPU list.
> And this works transparently not only with the generic scheduler
> code moving the vCPU to another pCPU, but also with some of the
> individual scheduler implementations doing such re-assignments?

I cannot quite understand this, could you please elaborate a bit more. Thanks a 


> Jan

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.