From: Stefan Hajnoczi <stefanha@redhat.com>
To: Christian Pinto <c.pinto@virtualopensystems.com>
Cc: virtio-dev@lists.oasis-open.org, qemu-devel@nongnu.org,
b.reynal@virtualopensystems.com, tech@virtualopensystems.com,
Claudio.Fontana@huawei.com, Jani.Kokkonen@huawei.com,
cornelia.huck@de.ibm.com
Subject: Re: [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification
Date: Thu, 14 Jul 2016 13:24:04 +0100 [thread overview]
Message-ID: <20160714122404.GC16535@stefanha-x1.localdomain> (raw)
In-Reply-To: <1467111824-11548-3-git-send-email-c.pinto@virtualopensystems.com>
[-- Attachment #1: Type: text/plain, Size: 1131 bytes --]
On Tue, Jun 28, 2016 at 01:03:44PM +0200, Christian Pinto wrote:
> +\begin{lstlisting}
> +struct virtio_sdm_config {
> + u8 master;
The next field has 16-bit alignment so there is a hole in this struct.
Three options:
1. Add an explicit u8 padding field.
2. Change master's type from u8 to u16.
3. Move master to the end of the struct.
> +\subsection{Device Initialization}\label{sec:Device Types / SDM Device /
> +evice Initialization}
> +
> +During initialization the \texttt{hg_vq} and \texttt{gh_vq} are identified and
> +the device is immediately operational. A master driver instance can access the
> +number of slaves registered at any time by reading the configuration space of
> +the device.
> +
> +During the initialization phase the device connects also to the communication
> +channel. It has to be noted that the behavior of the device is
> +independent from the communication channel used, that is a detail of each
> +specific implementation of the SDM device.
How are SDM devices identified? For example, if two SDM devices are
available, how does the driver know which one serves a particular
function?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2016-07-14 12:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 11:03 [Qemu-devel] [virtio-dev][RFC v2 0/2] Signal Distribution Module virtio device specification Christian Pinto
2016-06-28 11:03 ` [Qemu-devel] [virtio-dev][RFC v2 1/2] content: reserve virtio device ID Christian Pinto
2016-07-14 12:16 ` Stefan Hajnoczi
2016-07-14 12:22 ` Stefan Hajnoczi
2016-06-28 11:03 ` [Qemu-devel] [virtio-dev][RFC v2 2/2] virtio-sdm: new device specification Christian Pinto
2016-07-14 12:17 ` Stefan Hajnoczi
2016-07-19 7:47 ` Christian Pinto
2016-07-19 8:40 ` Stefan Hajnoczi
2016-07-22 16:18 ` Christian Pinto
2016-08-04 8:46 ` Stefan Hajnoczi
2016-08-08 8:00 ` Christian Pinto
2016-07-14 12:24 ` Stefan Hajnoczi [this message]
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=20160714122404.GC16535@stefanha-x1.localdomain \
--to=stefanha@redhat.com \
--cc=Claudio.Fontana@huawei.com \
--cc=Jani.Kokkonen@huawei.com \
--cc=b.reynal@virtualopensystems.com \
--cc=c.pinto@virtualopensystems.com \
--cc=cornelia.huck@de.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=tech@virtualopensystems.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;
as well as URLs for NNTP newsgroup(s).