On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > +
> > static void pvcalls_back_work(struct work_struct *work)
> > {
> > + struct pvcalls_back_priv *priv = container_of(work,
> > + struct pvcalls_back_priv, register_work);
> > +
On Fri, 26 May 2017, Boris Ostrovsky wrote:
> On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> > +
> > static void pvcalls_back_work(struct work_struct *work)
> > {
> > + struct pvcalls_back_priv *priv = container_of(work,
> > + struct pvcalls_back_priv, register_work);
> > +
On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> +
> static void pvcalls_back_work(struct work_struct *work)
> {
> + struct pvcalls_back_priv *priv = container_of(work,
> + struct pvcalls_back_priv, register_work);
> + int notify, notify_all = 0, more = 1;
> + struct
On 05/19/2017 07:22 PM, Stefano Stabellini wrote:
> +
> static void pvcalls_back_work(struct work_struct *work)
> {
> + struct pvcalls_back_priv *priv = container_of(work,
> + struct pvcalls_back_priv, register_work);
> + int notify, notify_all = 0, more = 1;
> + struct
When the other end notifies us that there are commands to be read
(pvcalls_back_event), wake up the backend thread to parse the command.
The command ring works like most other Xen rings, so use the usual
ring macros to read and write to it. The functions implementing the
commands are empty stubs
When the other end notifies us that there are commands to be read
(pvcalls_back_event), wake up the backend thread to parse the command.
The command ring works like most other Xen rings, so use the usual
ring macros to read and write to it. The functions implementing the
commands are empty stubs
6 matches
Mail list logo
