lkml.org 
[lkml]   [2011]   [Nov]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Subjectvirtio-pci new configuration proposal
From
Date
This is a proposal for a new layout of the virtio-pci config space.

We will separate the current configuration into two: A virtio-pci common
configuration and a device specific configuration. This allows more flexibility
with adding features and makes usage easier, specifically in cases like the
ones in virtio-net where device specific configurations depend on device
specific features.

The preferred location of the configuration will be a MMIO BAR, therefore
several size optimizations such as the queue selector which were useful
on a PIO BAR were removed and linked lists were introduced to add
flexibility to existing structures in attempt to keep their size and
offsets constant and not dependent on features.

While this is not a complete specification, it describes all the main
structures and should be enough to make sure the idea is solid before
going into implementation specifics.

A new virtio-pci capability structure will be introduced. This structure
will be used to describe the basics of a virtio-pci device. The
structure is actually a PCI capability structure which wraps the new virtio-pci
capability structure:

+------------++------------+------------+------------+--------------+-----------------
| Bits || 8 | 8 | 8 | 8 | Cap specific
+------------++------------+------------+------------+--------------+-----------------
| Read/Write || R | R | R | R | Cap specific
+------------++------------+------------+------------+--------------+-----------------
| Purpose || Capability | Capability | virtio-pci | virtio-pci | Cap specific
| || ID | Next PTR | Cap ID | Next Cap PTR |
+------------++------------+------------+------------+--------------+-----------------

Currently, only one virtio-pci capability is defined, and is the one that defines
the layout of the virtio-pci config space.

VIRTIO_PCI_C_LAYOUT:

+------------++---------------+---------------+-----------------+-----------------+
| Bits || 29 | 3 | 29 | 3 |
+------------++---------------+---------------+-----------------+-----------------+
| Read/Write || R | R | R | R |
+------------++---------------+---------------+-----------------+-----------------+
| Purpose || Common config | Common config | Device specific | Device specific |
| || Offset | BIR | Offset | BIR |
+------------++---------------+---------------+-----------------+-----------------+

The combination of the offset and the BIR will point to the common and device
specific configuration spaces. These spaces may be pointed to by the same, or
by different BARs and may sit in the same or different MMIO regions.

The BIR is a PCI concept which describes which BAR should be used:

"Indicates which one of a function’s Base Address registers, located beginning
at 10h in Configuration space, is used to map the function’s MSI-X Table into
memory space.

BIR Value Base Address register
0 10h
1 14h
2 18h
3 1Ch
4 20h
5 24h
6 Reserved
7 Reserved"

While the offset will provide a 32-bit aligned offset into the memory region
and will point to the appropriate config space.

First, we will look at the virtio-pci configuration space, which has been
simplified from the original.

virtio-pci header:

+------------++---------+--------+--------------+--------------+
| Bits || 8 | 8 | 16 | 16 |
+------------++---------+--------+--------------+--------------+
| Read/Write || R+W | R | R | R |
+------------++---------+--------+--------------+--------------+
| Purpose || Device | ISR | Queue | virtio-pci |
| || Status | Status | Table Ptr | Features Ptr |
+------------++---------+--------+--------------+--------------+

Device and ISR status are the same as in the original, and two new fields
have been added. Queue table ptr is an offset from the beginning of the
config space to a table which describes all virtio queues, and is defined
below.
Virtio-pci features ptr will point to virtio-pci features, such features
will be placed in a virtio-pci feature struct which is defined as follows:

virtio-pci features:

+------------++------------+------------+-------------------
| Bits || 8 | 16 | Feature specific
+------------++------------+------------+-------------------
| Read/Write || R | R | Feature specific
+------------++------------+------------+-------------------
| Purpose || Feature | Feature | Feature specific
| || ID | Next PTR |
+------------++------------+------------+-------------------

For example, the virtio-pci MSI-X feature will look as follows:

VIRTIO_PCI_F_MSIX:

+------------++----------------+
| Bits || 16 |
+------------++----------------+
| Read/Write || R+W |
+------------++----------------+
| Purpose || Configuration |
| || Vector |
+------------++----------------+

The queue table is the table which will hold the definition of all virtio
queues. The virtio queue selector has been dropped and instead the queues
are listed in a simple list:

Queue table:

+------------++-------------------+--------+---------+--------------+--------------
| Bits || 8 | 32 | 16 | 16 | 16 | More queues
+------------++-------------------+--------+---------+--------------+--------------
| Read/Write || R | R+W | R | R+W | R | More queues
+------------++-------------------+--------+---------+--------------+--------------
| Purpose || Queue | Queue | Queue | Queue | Queue | More queues
| || Count | Address | Size | Notify | Features Ptr |
+------------++-------------------+--------+---------+--------------+--------------

Besides the usual fields, each virtio queue will also have a feature ptr which
points to queue specific features. These features may be shared between queues
therefore it is not required to define a feature struct for each queue.

Queue features:

+------------++------------+------------+-------------------
| Bits || 8 | 16 | Feature specific
+------------++------------+------------+-------------------
| Read/Write || R | R | Feature specific
+------------++------------+------------+-------------------
| Purpose || Feature | Feature | Feature specific
| || ID | Next PTR |
+------------++------------+------------+-------------------

For example, the virtio queue MSI-X feature will look as follows and may be
shared between all virtio queues if we only have one vector for all queues.

VIRTIO_QUEUE_F_MSIX:

+------------++--------+
| Bits || 16 |
+------------++--------+
| Read/Write || R+W |
+------------++--------+
| Purpose || Queue |
| (MSI-X) || Vector |
+------------++--------+



The second part is the device specific configuration space. This is
basically a linked list of features which may be activated or
deactivated by setting the active flag in each feature.

Device specific features:

+------------++------------+------------+----------+---------
| Bits || 8 | 16 | 8 | Feature specific
+------------++------------+------------+----------+---------
| Read/Write || R | R | R+W | Feature specific
+------------++------------+------------+----------+---------
| Purpose || Feature | Feature | Feature | Feature specific
| || ID | Next PTR | Active |
+------------++------------+------------+----------+---------

For example, the virtio-net MAC feature will look as follows:

VIRTIO_NET_F_MAC:

+------------++------------+
| Bits || 48 |
+------------++------------+
| Read/Write || R |
+------------++------------+
| Purpose || virtio-net |
| || MAC |
+------------++------------+

--

Sasha.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2011-11-02 19:53    [W:0.087 / U:10.380 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site