From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw137318 [PATCH] net/virtio-user: support IOVA as PA mode
Date: Tue, 27 Feb 2024 19:46:35 -0800 (PST) [thread overview]
Message-ID: <65deac9b.050a0220.6a7af.0b21SMTPIN_ADDED_MISSING@mx.google.com> (raw)
In-Reply-To: <20240227055635.2135782-1-schalla@marvell.com>
Test-Label: iol-intel-Functional
Test-Status: SUCCESS
http://dpdk.org/patch/137318
_Functional Testing PASS_
Submitter: Srujana Challa <schalla@marvell.com>
Date: Tuesday, February 27 2024 05:56:35
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:2176806a4052a28bce70fe1767d8a56c6d7e904e
137318 --> functional testing pass
Test environment and result as below:
Ubuntu 20.04 ARM
Kernel: 4.15.0-132-generic
Compiler: gcc 7.5
NIC: Arm Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/2
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter XL710-QDA2 40000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
Ubuntu 20.04
Kernel: 4.15.0-generic
Compiler: gcc 7.4
NIC: Intel Corporation Ethernet Converged Network Adapter 82599ES 10000 Mbps
Target: x86_64-native-linuxapp-gcc
Fail/Total: 0/3
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/29275/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next prev parent reply other threads:[~2024-02-28 3:46 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240227055635.2135782-1-schalla@marvell.com>
2024-02-27 5:34 ` |SUCCESS| pw137318 [PATCH] net/virtio-user: support IOVA as PA mode for vDPA backend qemudev
2024-02-27 5:38 ` qemudev
2024-02-27 5:57 ` checkpatch
2024-02-27 6:45 ` 0-day Robot
2024-02-28 3:02 ` |SUCCESS| pw137318 [PATCH] net/virtio-user: support IOVA as PA mode dpdklab
2024-02-28 3:46 ` dpdklab [this message]
2024-02-29 7:20 ` dpdklab
2024-02-29 7:25 ` dpdklab
2024-02-29 7:42 ` dpdklab
2024-02-29 7:44 ` dpdklab
2024-02-27 11:12 dpdklab
2024-02-27 11:18 dpdklab
2024-02-27 11:19 dpdklab
2024-02-27 11:27 dpdklab
2024-02-27 11:28 dpdklab
2024-02-27 11:28 dpdklab
2024-02-27 11:45 dpdklab
2024-02-27 11:45 dpdklab
2024-02-27 11:45 dpdklab
2024-02-27 11:46 dpdklab
2024-02-27 11:46 dpdklab
2024-02-27 11:46 dpdklab
2024-02-27 11:47 dpdklab
2024-02-27 11:49 dpdklab
2024-02-27 11:49 dpdklab
2024-02-27 13:10 dpdklab
2024-02-27 13:11 dpdklab
2024-02-27 13:12 dpdklab
2024-02-27 13:12 dpdklab
2024-02-27 13:14 dpdklab
2024-02-27 13:14 dpdklab
2024-02-27 13:14 dpdklab
2024-02-27 13:16 dpdklab
2024-02-27 13:20 dpdklab
2024-02-27 13:25 dpdklab
2024-02-27 13:28 dpdklab
2024-02-27 13:28 dpdklab
2024-02-27 13:29 dpdklab
2024-02-27 13:30 dpdklab
2024-02-27 13:31 dpdklab
2024-02-27 13:32 dpdklab
2024-02-27 13:35 dpdklab
2024-02-27 13:35 dpdklab
2024-02-27 13:36 dpdklab
2024-02-27 13:36 dpdklab
2024-02-27 13:37 dpdklab
2024-02-27 13:37 dpdklab
2024-02-27 13:37 dpdklab
2024-02-27 13:41 dpdklab
2024-02-27 13:45 dpdklab
2024-02-27 13:45 dpdklab
2024-02-27 13:46 dpdklab
2024-02-27 13:46 dpdklab
2024-02-27 13:47 dpdklab
2024-02-27 13:52 dpdklab
2024-02-27 13:53 dpdklab
2024-02-27 13:53 dpdklab
2024-02-27 13:54 dpdklab
2024-02-27 13:54 dpdklab
2024-02-27 13:55 dpdklab
2024-02-27 13:55 dpdklab
2024-02-27 13:55 dpdklab
2024-02-27 13:56 dpdklab
2024-02-27 13:56 dpdklab
2024-02-27 14:01 dpdklab
2024-02-27 14:05 dpdklab
2024-02-27 14:17 dpdklab
2024-02-27 14:18 dpdklab
2024-02-27 14:25 dpdklab
2024-02-27 14:26 dpdklab
2024-02-27 17:08 dpdklab
2024-02-27 17:54 dpdklab
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=65deac9b.050a0220.6a7af.0b21SMTPIN_ADDED_MISSING@mx.google.com \
--to=dpdklab@iol.unh.edu \
--cc=dpdk-test-reports@iol.unh.edu \
--cc=test-report@dpdk.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).