From: dpdklab@iol.unh.edu
To: Test Report <test-report@dpdk.org>
Cc: dpdk-test-reports@iol.unh.edu
Subject: |SUCCESS| pw126857 [PATCH] dma/idxd: add support for multi-process when using VFIO
Date: Mon, 15 May 2023 15:20:28 -0700 (PDT) [thread overview]
Message-ID: <6462b02c.810a0220.1bbcc.1876SMTPIN_ADDED_MISSING@mx.google.com> (raw)
Test-Label: iol-aarch64-compile-testing
Test-Status: SUCCESS
http://dpdk.org/patch/126857
_Testing PASS_
Submitter: Bruce Richardson <bruce.richardson@intel.com>
Date: Monday, May 15 2023 16:29:07
DPDK git baseline: Repo:dpdk
Branch: master
CommitID:dbff181d62c997f128b75db2bbac9f42e8dd0f8f
126857 --> testing pass
Test environment and result as below:
+----------------------------------------+--------------------+
| Environment | dpdk_meson_compile |
+========================================+====================+
| Ubuntu 20.04 ARM GCC Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Native | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 aarch32 GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM SVE | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM Clang Cross Compile | PASS |
+----------------------------------------+--------------------+
| Ubuntu 20.04 ARM GCC Cross Compile | PASS |
+----------------------------------------+--------------------+
Ubuntu 20.04 ARM GCC Native
Kernel: 5.4.0-53-generic
Compiler: gcc 9.3
Ubuntu 20.04 ARM Clang Native
Kernel: 5.4.0-53-generic
Compiler: clang 10.0.0-4ubuntu1
Ubuntu 20.04 aarch32 GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: gcc 9.3.0
Ubuntu 20.04 ARM SVE
Kernel: 5.4.0-80-generic
Compiler: gcc 10.3.0 (Ubuntu 10.3.0-1ubuntu1~20.04)
Ubuntu 20.04 ARM Clang Cross Compile
Kernel: 5.4.0-72-generic
Compiler: clang version 10.0.0-4ubuntu1
Ubuntu 20.04 ARM GCC Cross Compile
Kernel: 5.4.0-72-generic
Compiler: aarch64-linux-gnu-gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
To view detailed results, visit:
https://lab.dpdk.org/results/dashboard/patchsets/26228/
UNH-IOL DPDK Community Lab
To manage your email subscriptions, visit:
https://lab.dpdk.org/results/dashboard/preferences/subscriptions/
next reply other threads:[~2023-05-15 22:20 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 22:20 dpdklab [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-05-16 14:31 dpdklab
2023-05-16 14:16 dpdklab
2023-05-16 14:10 dpdklab
2023-05-16 14:06 dpdklab
2023-05-16 14:03 dpdklab
2023-05-15 22:18 dpdklab
2023-05-15 22:11 dpdklab
2023-05-15 22:11 dpdklab
2023-05-15 22:03 dpdklab
2023-05-15 21:59 dpdklab
2023-05-15 21:59 dpdklab
2023-05-15 21:59 dpdklab
2023-05-15 21:54 dpdklab
2023-05-15 21:54 dpdklab
2023-05-15 21:50 dpdklab
2023-05-15 21:49 dpdklab
2023-05-15 21:48 dpdklab
2023-05-15 21:48 dpdklab
2023-05-15 21:47 dpdklab
2023-05-15 21:47 dpdklab
2023-05-15 21:36 dpdklab
2023-05-15 21:35 dpdklab
2023-05-15 21:35 dpdklab
2023-05-15 21:28 dpdklab
2023-05-15 21:28 dpdklab
2023-05-15 21:27 dpdklab
2023-05-15 21:27 dpdklab
2023-05-15 21:23 dpdklab
2023-05-15 21:20 dpdklab
[not found] <20230515162907.8456-1-bruce.richardson@intel.com>
2023-05-15 16:17 ` qemudev
2023-05-15 16:21 ` qemudev
2023-05-15 17:39 ` 0-day Robot
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=6462b02c.810a0220.1bbcc.1876SMTPIN_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).