On Fri, Mar 5, 2021 at 11:44 AM Jason Wang <jasowang@xxxxxxxxxx> wrote: > > > On 2021/3/5 11:37 上午, Yongji Xie wrote: > > On Fri, Mar 5, 2021 at 11:11 AM Jason Wang <jasowang@xxxxxxxxxx> wrote: > >> > >> On 2021/3/4 4:19 下午, Yongji Xie wrote: > >>> On Thu, Mar 4, 2021 at 3:30 PM Jason Wang <jasowang@xxxxxxxxxx> wrote: > >>>> On 2021/2/23 7:50 下午, Xie Yongji wrote: > >>>>> Add a parameter for the ioctl VDUSE_INJECT_VQ_IRQ to support > >>>>> injecting virtqueue's interrupt to the specified cpu. > >>>> How userspace know which CPU is this irq for? It looks to me we need to > >>>> do it at different level. > >>>> > >>>> E.g introduce some API in sys to allow admin to tune for that. > >>>> > >>>> But I think we can do that in antoher patch on top of this series. > >>>> > >>> OK. I will think more about it. > >> > >> It should be soemthing like > >> /sys/class/vduse/$dev_name/vq/0/irq_affinity. Also need to make sure > >> eventfd could not be reused. > >> > > Looks like we doesn't use eventfd now. Do you mean we need to use > > eventfd in this case? > > > No, I meant if we're using eventfd, do we allow a single eventfd to be > used for injecting irq for more than one virtqueue? (If not, I guess it > should be ok). > OK, I see. I think we don't allow that now. Thanks, Yongji
