summaryrefslogtreecommitdiff
path: root/virtio-v1.0-wd01-part1-specification.txt
diff options
context:
space:
mode:
Diffstat (limited to 'virtio-v1.0-wd01-part1-specification.txt')
-rw-r--r--virtio-v1.0-wd01-part1-specification.txt10
1 files changed, 5 insertions, 5 deletions
diff --git a/virtio-v1.0-wd01-part1-specification.txt b/virtio-v1.0-wd01-part1-specification.txt
index 9e63e0e..79731ef 100644
--- a/virtio-v1.0-wd01-part1-specification.txt
+++ b/virtio-v1.0-wd01-part1-specification.txt
@@ -876,7 +876,7 @@ configuration space. The following list presents their layout:
to (HostFeaturesSel*32)+31, eg. feature bits 0 to 31 if
HostFeaturesSel is set to 0 and features bits 32 to 63 if
- HostFeaturesSel is set to 1. Also see [sub:Feature-Bits]
+ HostFeaturesSel is set to 1. Also see "2.1.2. Feature Bits".
• 0x014 | W | HostFeaturesSel
Device (Host) features word selection.
@@ -893,7 +893,7 @@ configuration space. The following list presents their layout:
register. Access to this register sets bits GuestFeaturesSel*32
to (GuestFeaturesSel*32)+31, eg. feature bits 0 to 31 if
GuestFeaturesSel is set to 0 and features bits 32 to 63 if
- GuestFeaturesSel is set to 1. Also see [sub:Feature-Bits]
+ GuestFeaturesSel is set to 1. Also see "2.1.2. Feature Bits".
• 0x024 | W | GuestFeaturesSel
Activated (Guest) features word selection.
@@ -983,7 +983,7 @@ Reading from this register returns a bit mask of interrupts
Writing non-zero values to this register sets the status flags,
indicating the Guest progress. Writing zero (0x0) to this
register triggers a device reset.
- Also see [sub:Device-Initialization-Sequence]
+ Also see "2.2.1. Device Initialization".
• 0x100+ | RW | Config
Device-specific configuration space starts at an offset 0x100
@@ -1338,8 +1338,8 @@ least the size of the struct virtio_net_hdr.
When a packet is copied into a buffer in the receiveq, the
optimal path is to disable further interrupts for the receiveq
-(see [sub:Receiving-Used-Buffers]) and process packets until no
-more are found, then re-enable them.
+(see 2.2.2.2. Receiving Used Buffers From The Device) and process
+packets until no more are found, then re-enable them.
Processing packet involves: