Re: [PATCH 05/11] doorbells: Introduce doorbells

[Alex BennÃe <alex.bennee@linaro.org>]

Nikos Dragazis <ndragazis@arrikto.com> writes:

> Introduce doorbells as a new virtio device resource.
>
> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
> ---
>  content.tex   |  2 ++
>  doorbells.tex | 12 ++++++++++++
>  2 files changed, 14 insertions(+)
>  create mode 100644 doorbells.tex
>
> diff --git a/content.tex b/content.tex
> index 94a3693..38ed709 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -373,6 +373,8 @@ \section{Driver Notifications} \label{sec:Virtqueues / Driver notifications}
>  
>  \input{shared-mem.tex}
>  
> +\input{doorbells.tex}
> +
>  \chapter{General Initialization And Device Operation}\label{sec:General Initialization And Device Operation}
>  
>  We start with an overview of device initialization, then expand on the
> diff --git a/doorbells.tex b/doorbells.tex
> new file mode 100644
> index 0000000..e917536
> --- /dev/null
> +++ b/doorbells.tex
> @@ -0,0 +1,12 @@
> +\section{Doorbells}\label{sec:Basic Facilities of a Virtio device / Doorbells}
> +
> +A doorbell is a device register that triggers a notification to the
> +device when accessed by the driver.
> +
> +Doorbells are an additional facility available to devices that need to
> +support receiving driver notifications for events other than virtqueue
> +activity (i.e., notifications that are device-specific).
> +
> +A device may be exporting multiple doorbells to the driver.
> +
> +The location of doorbells is found in a transport-specific way.

I just realised we don't specify anything about delivery. Should we say
something about lack of acknowledgement or guarantee that the
notification is delivered here? 

-- 
Alex BennÃe