Discussion of the implementations of VIRTIO specification
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: Nikos Dragazis <ndragazis@arrikto.com>
Cc: virtio-dev@lists.oasis-open.org,
	Stefan Hajnoczi <stefanha@redhat.com>,
	"Michael S . Tsirkin" <mst@redhat.com>
Subject: [virtio-dev] Re: [PATCH 03/11] content: Update list of virtio cfg structures
Date: Thu, 17 Sep 2020 17:34:05 +0100	[thread overview]
Message-ID: <87k0wsxszm.fsf@linaro.org> (raw)
In-Reply-To: <20200824143708.5664-4-ndragazis@arrikto.com>


Nikos Dragazis <ndragazis@arrikto.com> writes:

> Shared memory and vendor-specific configuration structures have been
> introduced in previous commits.
>
> Update the list of virtio configuration structures so that it includes
> the shared memory and vendor-specific configuration structures.
>
> Signed-off-by: Nikos Dragazis <ndragazis@arrikto.com>
> ---
>  content.tex | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/content.tex b/content.tex
> index 3ce768c..b5b2f79 100644
> --- a/content.tex
> +++ b/content.tex
> @@ -634,6 +634,8 @@ \subsection{Virtio Structure PCI Capabilities}\label{sec:Virtio Transport Option
>  \item ISR Status
>  \item Device-specific configuration (optional)
>  \item PCI configuration access
> +\item Shared memory regions (optional)
> +\item Vendor-specific data (optional)

Are we talking about "Vendor data capability" here? Maybe we should call
it that?

>  \end{itemize}
>  
>  Each structure can be mapped by a Base Address register (BAR) belonging to


-- 
Alex Bennée

---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org


  reply	other threads:[~2020-09-17 16:34 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-24 14:36 [virtio-dev] [PATCH 00/11] Additional virtio device resources Nikos Dragazis
2020-08-24 14:36 ` [virtio-dev] [PATCH 01/11] content: Remove duplicate content Nikos Dragazis
2020-09-17 15:48   ` [virtio-dev] " Alex Bennée
2020-08-24 14:36 ` [virtio-dev] [PATCH 02/11] content: Minor fix Nikos Dragazis
2020-09-17 16:16   ` [virtio-dev] " Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 03/11] content: Update list of virtio cfg structures Nikos Dragazis
2020-09-17 16:34   ` Alex Bennée [this message]
2020-09-18 20:24     ` [virtio-dev] " Nikos Dragazis
2020-09-20 14:55       ` Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 04/11] content: Minor layout fix Nikos Dragazis
2020-09-17 16:38   ` [virtio-dev] " Alex Bennée
2020-08-24 14:37 ` [virtio-dev] [PATCH 05/11] doorbells: Introduce doorbells Nikos Dragazis
2020-09-17 14:58   ` [virtio-dev] " Alex Bennée
2020-09-17 16:59   ` Alex Bennée
2020-09-17 17:01   ` Alex Bennée
2020-09-18 21:24     ` Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 06/11] content: Introduce Doorbell cfg type for PCI Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 07/11] content: Introduce Doorbell register for MMIO Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 08/11] notifications: Introduce device-specific notifications Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 09/11] content: Introduce device-specific notification cfg type for PCI Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 10/11] content: Fix typo Nikos Dragazis
2020-08-24 14:37 ` [virtio-dev] [PATCH 11/11] content: Introduce device-specific notifications for MMIO Nikos Dragazis
2020-09-17 10:19 ` [virtio-dev] Re: [PATCH 00/11] Additional virtio device resources Nikos Dragazis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k0wsxszm.fsf@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=mst@redhat.com \
    --cc=ndragazis@arrikto.com \
    --cc=stefanha@redhat.com \
    --cc=virtio-dev@lists.oasis-open.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox