From: Cornelia Huck <cohuck@redhat.com>
To: "Ricardo Cañuelo" <ricardo.canuelo@collabora.com>,
linux-doc@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org, mst@redhat.com,
jasowang@redhat.com, kernel@collabora.com, bagasdotme@gmail.com
Subject: Re: [PATCH v2 2/2] docs: driver-api: virtio: virtio on Linux
Date: Tue, 09 Aug 2022 16:28:40 +0200 [thread overview]
Message-ID: <87wnbhcwyv.fsf@redhat.com> (raw)
In-Reply-To: <87iln1r2hv.fsf@rcn-XPS-13-9305.i-did-not-set--mail-host-address--so-tickle-me>
On Tue, Aug 09 2022, Ricardo Cañuelo <ricardo.canuelo@collabora.com> wrote:
> How about this as an introduction?
>
> Virtio is an open standard that defines a protocol to communicate
> drivers and devices of different types, see Chapter 5 ("Device
"...that defines a protocol for communication between drivers and
devices of different device types, see..."
> Types") of the virtio spec `[1]`_. Originally developed as a
> standard for paravirtualized devices implemented by a hypervisor, it
> can be used to interface any compliant device (real or emulated)
> with a driver.
>
> For illustrative purposes, this document will focus on the common
> case of a Linux kernel running in a virtual machine and using
> paravirtualized devices provided by the hypervisor, which exposes
> them as virtio devices via standard mechanisms such as PCI.
Sounds good to me.
(...)
> Ok, I'll simplify the intro to this:
>
> This document serves as a basic guideline for driver programmers
> that need to hack a new virtio driver or understand the essentials
> of the existing ones. See :ref:`Virtio on Linux <virtio>` for a
> general overview of virtio.
Ok.
prev parent reply other threads:[~2022-08-09 14:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-04 10:59 [PATCH v2 0/2] docs: driver-api: virtio: virtio on Linux Ricardo Cañuelo
2022-08-04 10:59 ` [PATCH v2 1/2] virtio: kerneldocs fixes and enhancements Ricardo Cañuelo
2022-08-08 12:14 ` Cornelia Huck
2022-08-08 12:52 ` Ricardo Cañuelo
2022-08-04 10:59 ` [PATCH v2 2/2] docs: driver-api: virtio: virtio on Linux Ricardo Cañuelo
2022-08-06 7:58 ` Bagas Sanjaya
2022-08-08 9:06 ` Ricardo Cañuelo
2022-08-08 12:31 ` Bagas Sanjaya
2022-08-08 13:47 ` Cornelia Huck
2022-08-09 13:05 ` Ricardo Cañuelo
2022-08-09 14:28 ` Cornelia Huck [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=87wnbhcwyv.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=jasowang@redhat.com \
--cc=kernel@collabora.com \
--cc=linux-doc@vger.kernel.org \
--cc=mst@redhat.com \
--cc=ricardo.canuelo@collabora.com \
--cc=virtualization@lists.linux-foundation.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).