[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACycT3vqdfm2KpF+JD_8oZouGfeK1nPc004isnNBUzXkVwSWww@mail.gmail.com>
Date: Fri, 17 Mar 2023 15:01:11 +0800
From: Yongji Xie <xieyongji@...edance.com>
To: Jason Wang <jasowang@...hat.com>
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
Thomas Gleixner <tglx@...utronix.de>,
Christoph Hellwig <hch@....de>,
virtualization <virtualization@...ts.linux-foundation.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v3 09/11] vduse: Signal interrupt's eventfd directly in
vhost-vdpa case
On Thu, Mar 16, 2023 at 5:31 PM Jason Wang <jasowang@...hat.com> wrote:
>
> On Tue, Feb 28, 2023 at 5:42 PM Xie Yongji <xieyongji@...edance.com> wrote:
> >
> > Now the vdpa callback will associate an eventfd in
> > vhost-vdpa case.
>
> I'd suggest avoiding mentioning drivers since vDPA parents should not
> know which vDPA driver is bound.
>
> We could say "signal vq trigger eventfd directly if possible"?
>
It makes sense to me.
Thanks,
Yongji
Powered by blists - more mailing lists