From: Laszlo Ersek <lersek@redhat.com>
To: Brijesh Singh <brijesh.singh@amd.com>
Cc: edk2-devel@lists.01.org
Subject: Re: [PATCH v4 0/8] OvmfPkg/VirtioNetDxe: map host address to device address
Date: Fri, 15 Sep 2017 02:14:26 +0200 [thread overview]
Message-ID: <1e4267dc-0133-e833-f805-8381ef82c52e@redhat.com> (raw)
In-Reply-To: <581a568d-b0ce-34a1-8e52-95adf14c03e0@redhat.com>
On 09/15/17 02:10, Laszlo Ersek wrote:
> On 09/14/17 23:22, Brijesh Singh wrote:
>> Repo: https://github.com/codomania/edk2
>> Branch: virtionet-4
>>
>> Changes since v3:
>> * changes to address v3 feedback
>>
>> Brijesh Singh (8):
>> OvmfPkg/VirtioNetDxe: add helper VirtioNetUninitRing()
>> OvmfPkg/VirtioNetDxe: map VRINGs using VirtioRingMap()
>> OvmfPkg/VirtioNetDxe: alloc RxBuf using AllocateSharedPages()
>> OvmfPkg/VirtioNetDxe: dynamically alloc transmit header
>> OvmfPkg/VirtioNetDxe: update TechNotes
>> OvmfPkg/VirtioNetDxe: add Tx packet map/unmap helper functions
>> OvmfPkg/VirtioNetDxe: map caller-supplied Tx packet to device-address
>> OvmfPkg/VirtioNetDxe: negotiate VIRTIO_F_IOMMU_PLATFORM
>>
>> OvmfPkg/VirtioNetDxe/VirtioNet.inf | 1 +
>> OvmfPkg/VirtioNetDxe/VirtioNet.h | 57 ++++-
>> OvmfPkg/VirtioNetDxe/SnpGetStatus.c | 43 +++-
>> OvmfPkg/VirtioNetDxe/SnpInitialize.c | 213 +++++++++++++---
>> OvmfPkg/VirtioNetDxe/SnpReceive.c | 5 +-
>> OvmfPkg/VirtioNetDxe/SnpSharedHelpers.c | 258 +++++++++++++++++++-
>> OvmfPkg/VirtioNetDxe/SnpShutdown.c | 4 +-
>> OvmfPkg/VirtioNetDxe/SnpTransmit.c | 27 +-
>> OvmfPkg/VirtioNetDxe/TechNotes.txt | 28 ++-
>> 9 files changed, 566 insertions(+), 70 deletions(-)
>>
>
> I've done the following tests:
>
> arch virtio transport SEV driver model test [1] PXE boot test [2]
> ------- ---------------- --- --------------------- -----------------
> IA32 legacy PCI - PASS PASS [3]
> IA32 modern PCI - PASS PASS [3]
> X64 legacy PCI - PASS PASS
> X64 modern PCI no PASS PASS
> AARCH64 virtio-mmio - PASS PASS
> X64 modern PCI yes PASS [4] PASS
>
> [1] driver model test:
> - ifconfig/dhcp, ping
> - shell disconnect / connect
> - ifconfig/dhcp, ping
>
> [2] PXE boot test:
> - OVMF -> shim -> grub -> kernel
I shouldn't forget the initrd's here either; those were also loaded, of
course.
Thanks
Laszlo
> - see kernel messages
>
> [3] I didn't have a 32-bit shim.efi, so I only verified the first (i.e.,
> OVMF -> shim) download
>
> [4] I repeated this test separately with verbose debug messages enabled.
> It was amazing to watch the log while running several pings after
> each other. After pinging, I booted the OS and verified from the log
> that all areas were re-encrypted.
>
> Regression-tested-by: Laszlo Ersek <lersek@redhat.com>
> Tested-by: Laszlo Ersek <lersek@redhat.com>
>
> Series pushed as commit range b30abe7df464..f60ed5ab7fb3.
>
> Thank you!
> Laszlo
>
prev parent reply other threads:[~2017-09-15 0:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 21:22 [PATCH v4 0/8] OvmfPkg/VirtioNetDxe: map host address to device address Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 1/8] OvmfPkg/VirtioNetDxe: add helper VirtioNetUninitRing() Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 2/8] OvmfPkg/VirtioNetDxe: map VRINGs using VirtioRingMap() Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 3/8] OvmfPkg/VirtioNetDxe: alloc RxBuf using AllocateSharedPages() Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 4/8] OvmfPkg/VirtioNetDxe: dynamically alloc transmit header Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 5/8] OvmfPkg/VirtioNetDxe: update TechNotes Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 6/8] OvmfPkg/VirtioNetDxe: add Tx packet map/unmap helper functions Brijesh Singh
2017-09-14 21:22 ` [PATCH v4 7/8] OvmfPkg/VirtioNetDxe: map caller-supplied Tx packet to device-address Brijesh Singh
2017-09-14 21:49 ` Laszlo Ersek
2017-09-14 21:22 ` [PATCH v4 8/8] OvmfPkg/VirtioNetDxe: negotiate VIRTIO_F_IOMMU_PLATFORM Brijesh Singh
2017-09-15 0:10 ` [PATCH v4 0/8] OvmfPkg/VirtioNetDxe: map host address to device address Laszlo Ersek
2017-09-15 0:14 ` Laszlo Ersek [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-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=1e4267dc-0133-e833-f805-8381ef82c52e@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