From: Laszlo Ersek <lersek@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>, edk2-devel@lists.01.org
Cc: Jordan Justen <jordan.l.justen@intel.com>,
Ard Biesheuvel <ard.biesheuvel@linaro.org>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH 4/5] OvmfPkg/VirtioNetDxe: map virtio-net transmit request buffer
Date: Wed, 6 Sep 2017 10:11:01 +0200 [thread overview]
Message-ID: <f6c7c268-42b1-793e-a2ac-c4946b27bc2b@redhat.com> (raw)
In-Reply-To: <09699a1f-9bc9-02d1-f7d0-99cd9d42051e@redhat.com>
On 09/05/17 14:41, Laszlo Ersek wrote:
> On 09/01/17 13:24, Brijesh Singh wrote:
>> When device is behind the IOMMU, driver is require to pass the device
>> address of transmit buffer for the bus master operations.
>>
>> The patch uses VirtioMapAllBytesInSharedBuffer() to map transmit buffer
>> system physical address to the device address.
>>
>> Since the transmit buffers are returned back to caller in
>> VirtioNetGetStatus() hence we use OrderCollection library interface to
>> save the host to device address mapping. After the buffer is succesfully
>> transmited we do reverse lookup in OrderCollection data structure to get
>> the host address for the transmitted device address.
>>
>> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
>> Cc: Jordan Justen <jordan.l.justen@intel.com>
>> Cc: Tom Lendacky <thomas.lendacky@amd.com>
>> Cc: Laszlo Ersek <lersek@redhat.com>
>> Contributed-under: TianoCore Contribution Agreement 1.1
>> Signed-off-by: Brijesh Singh <brijesh.singh@amd.com>
>> ---
>> OvmfPkg/VirtioNetDxe/VirtioNet.inf | 1 +
>> OvmfPkg/VirtioNetDxe/VirtioNet.h | 19 +++
>> OvmfPkg/VirtioNetDxe/SnpGetStatus.c | 30 +++-
>> OvmfPkg/VirtioNetDxe/SnpSharedHelpers.c | 157 ++++++++++++++++++++
>> OvmfPkg/VirtioNetDxe/SnpTransmit.c | 37 ++++-
>> 5 files changed, 232 insertions(+), 12 deletions(-)
> (7) We'll have to document the new model in "TechNotes.txt".
I've now re-read the final section of the text file, section
Virtio internals -- Tx
I propose the following updates.
(Here I'm providing a diff, not a desired "end status", like I did for
the diagram earlier. A diff is harder to interpret for a diagram, but
easy for plain text.)
Please verify that the proposed documentation updates match the logic
that you've implemented:
> diff --git a/OvmfPkg/VirtioNetDxe/TechNotes.txt b/OvmfPkg/VirtioNetDxe/TechNotes.txt
> index 9c1dfe6a773e..7a7b3071abba 100644
> --- a/OvmfPkg/VirtioNetDxe/TechNotes.txt
> +++ b/OvmfPkg/VirtioNetDxe/TechNotes.txt
> @@ -310,10 +310,14 @@ in the following:
> that is shared by all of the head descriptors. This virtio-net request header
> is never modified by the host.
>
> -- Each tail descriptor is re-pointed to the caller-supplied packet buffer
> - whenever VirtioNetTransmit places the corresponding head descriptor on the
> - Available Ring. The caller is responsible to hang on to the unmodified buffer
> - until it is reported transmitted by VirtioNetGetStatus.
> +- Each tail descriptor is re-pointed to the device-mapped address of the
> + caller-supplied packet buffer whenever VirtioNetTransmit places the
> + corresponding head descriptor on the Available Ring. A reverse mapping, from
> + the device-mapped address to the caller-supplied packet address, is saved in
> + an associative data structure that belongs to the driver instance.
> +
> +- Per spec, the caller is responsible to hang on to the unmodified packet
> + buffer until it is reported transmitted by VirtioNetGetStatus.
>
> Steps of packet transmission:
>
> @@ -336,9 +340,11 @@ Steps of packet transmission:
> - Client code calls VirtioNetGetStatus. In case the Used Ring is empty, the
> function reports no Tx completion. Otherwise, a head descriptor's index is
> consumed from the Used Ring and recycled to the private stack. The client
> - code's original packet buffer address is fetched from the tail descriptor
> - (where it has been stored at VirtioNetTransmit time) and returned to the
> - caller.
> + code's original packet buffer address is calculated by fetching the
> + device-mapped address from the tail descriptor (where it has been stored at
> + VirtioNetTransmit time), and by looking up the device-mapped address in the
> + associative data structure. The reverse-mapped packet buffer address is
> + returned to the caller.
>
> - The Len field of the Used Ring Element is not checked. The host is assumed to
> have transmitted the entire packet -- VirtioNetTransmit had forced it below
Thanks!
Laszlo
next prev parent reply other threads:[~2017-09-06 8:08 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-01 11:24 [PATCH 0/5] OvmfPkg/VirtioNetDxe: map host address to device address Brijesh Singh
2017-09-01 11:24 ` [PATCH 1/5] OvmfPkg/VirtioNetDxe: map VRING using VirtioRingMap() Brijesh Singh
2017-09-05 11:47 ` Laszlo Ersek
2017-09-05 18:57 ` Brijesh Singh
2017-09-05 20:17 ` Laszlo Ersek
2017-09-05 21:11 ` Ard Biesheuvel
2017-09-05 21:59 ` Laszlo Ersek
2017-09-05 22:18 ` Ard Biesheuvel
2017-09-05 22:37 ` Laszlo Ersek
2017-09-05 23:03 ` Ard Biesheuvel
2017-09-01 11:24 ` [PATCH 2/5] OvmfPkg/VirtioNetDxe: alloc RxBuf using AllocateSharedPages() Brijesh Singh
2017-09-05 15:06 ` Laszlo Ersek
2017-09-01 11:24 ` [PATCH 3/5] OvmfPkg/VirtioNetDxe: dynamically alloc transmit header Brijesh Singh
2017-09-06 9:11 ` Laszlo Ersek
2017-09-01 11:24 ` [PATCH 4/5] OvmfPkg/VirtioNetDxe: map virtio-net transmit request buffer Brijesh Singh
2017-09-05 12:41 ` Laszlo Ersek
2017-09-05 12:44 ` Laszlo Ersek
2017-09-06 8:11 ` Laszlo Ersek [this message]
2017-09-01 11:24 ` [PATCH 5/5] OvmfPkg/VirtioNetDxe: negotiate VIRTIO_F_IOMMU_PLATFORM Brijesh Singh
2017-09-06 7:33 ` Laszlo Ersek
2017-09-07 22:55 ` [PATCH 0/5] OvmfPkg/VirtioNetDxe: map host address to device address Laszlo Ersek
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-list 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=f6c7c268-42b1-793e-a2ac-c4946b27bc2b@redhat.com \
--to=devel@edk2.groups.io \
/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