From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: qemu-devel@nongnu.org
Cc: Aniket Sahu <asahu1x@linux.ibm.com>,
Thomas Huth <thuth@redhat.com>,
Amit Machhiwal <amachhiw@linux.ibm.com>,
Aditya Gupta <adityag@linux.ibm.com>
Subject: [PULL 3/6] tests/functional/ppc64: extend ppc64 powernv net device tests
Date: Wed, 28 Oct 2026 10:50:21 +0530 [thread overview]
Message-ID: <20261028052024.38377-4-harshpb@linux.ibm.com> (raw)
In-Reply-To: <20261028052024.38377-1-harshpb@linux.ibm.com>
From: Aniket Sahu <asahu1x@linux.ibm.com>
Added console checks as the probe log lines will appear before the
S14Silence-console init scripts.
Signed-off-by: Aniket Sahu <asahu1x@linux.ibm.com>
Reviewed-by: Thomas Huth <thuth@redhat.com>
Reviewed-by: Amit Machhiwal <amachhiw@linux.ibm.com>
Reviewed-by: Aditya Gupta <adityag@linux.ibm.com>
Link: https://lore.kernel.org/qemu-devel/20260921081010.31778-3-asahu1x@linux.ibm.com
Signed-off-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
---
tests/functional/ppc64/test_powernv.py | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tests/functional/ppc64/test_powernv.py b/tests/functional/ppc64/test_powernv.py
index f3e05e4d38..200fd2c894 100755
--- a/tests/functional/ppc64/test_powernv.py
+++ b/tests/functional/ppc64/test_powernv.py
@@ -201,9 +201,12 @@ def do_test_ppc64_powernv(self, proc):
self.wait_for_console_pattern("CPU: " + proc + " generation processor")
self.wait_for_console_pattern("INIT: Starting kernel at ")
+ # NVMe, e1000e, and xHCI are probed synchronously by the kernel
+ # during PCI enumeration, after OPAL hands off to Linux.
+ self.wait_for_console_pattern("nvme nvme0")
+ self.wait_for_console_pattern("e1000e")
+ self.wait_for_console_pattern("xhci_hcd")
self.wait_for_console_pattern("Run /sbin/init as init process")
- # Device detection output driven by udev probing is sometimes cut off
- # from console output, suspect S14silence-console init script.
def test_ppc64_powernv_external_dtb(self):
self.set_machine('powernv11')
--
2.52.0
next prev parent reply other threads:[~2026-10-28 5:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-28 5:20 [PULL 0/6] ppc queue for 2026-10-28 Harsh Prateek Bora
2026-10-28 5:20 ` [PULL 1/6] hw/pci-host/pnv_phb4: fix guest-triggerable abort on 8-byte config access Harsh Prateek Bora
2026-10-28 5:20 ` [PULL 2/6] tests/functional/ppc64: extend pseries migration tests Harsh Prateek Bora
2026-10-28 5:20 ` Harsh Prateek Bora [this message]
2026-10-28 5:20 ` [PULL 4/6] hw/net/spapr_llan: validate RxBufPool fields on migration load Harsh Prateek Bora
2026-10-28 5:20 ` [PULL 5/6] hw/ppc/spapr: Add the "rtas-version" property to /rtas Harsh Prateek Bora
2026-10-28 5:20 ` [PULL 6/6] spapr-vscsi: clamp adapter info DMA write length to struct size Harsh Prateek Bora
2026-10-28 11:20 ` [PULL 0/6] ppc queue for 2026-10-28 Richard Henderson
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=20261028052024.38377-4-harshpb@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=adityag@linux.ibm.com \
--cc=amachhiw@linux.ibm.com \
--cc=asahu1x@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.