Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1977744iog; Sun, 26 Jun 2022 03:32:16 -0700 (PDT) X-Google-Smtp-Source: AGRyM1v5RrFH2jD859rVEdrbeOKDRH6gWV+76ZL6HmjUBrSufp4mWOlJp3kB6kva553KoLuPRcfs X-Received: by 2002:aa7:c38d:0:b0:435:9257:99a5 with SMTP id k13-20020aa7c38d000000b00435925799a5mr10145507edq.204.1656239536474; Sun, 26 Jun 2022 03:32:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656239536; cv=none; d=google.com; s=arc-20160816; b=kmezPHAUe/OxBJQ7/HiNYg63PlBZodFLBfsWGPbHIQ4BFaNUbNY2SZDWHhZYnAFf8+ ga4jYVo4zj1NNOScQV6K2RudSyjRBqGxKh+iA5whGbwtrDMzZEwHd8tAZDcWZMbKNy2H I81sB+gNLsEIaR8Sa5/z0qAvorYJoyRxwM4q4qcXGbCttxMA9/zUlNoLJuiKPZ0aEjB7 0TlqXbehNiB2Iwp3v5fXv/RO1EaEYG6LNGIKdN9iUp0qyXMhKZaOdzm0a4nJMSddcaV1 g2SHNJJA8zD2rsdnpaoXiMLOvDGasPYDyKpXagoB6ks4cD3UYD1qmpwKCqq31qbzfdQA oSYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:from:subject:mime-version:message-id:date :dkim-signature; bh=A6ULT6qt3Y8m7tER4ibPrZPKIE4ZaUO512mygVxvB7M=; b=oGmbkCEVDK1lYLhhmw0/nhNwpAg2dTjpkV5eEvFVGZoZ/0AGPZkPmxy6qjO8/u7Cy8 A8u+WLTPBhYgAiKJIzKrgW3ahnuG9yWkYobQuDPZtwpJEAp8jpGg5luRY51XPalZjyLc mBYfaJxbihiIiWkMoUWmyMd4h8bciJRurGYSe1esLWolm/8mjMSOVPpEMFZySD3/0CON jPA1fUZDXjToRB9jb585OTK9OZitt1XPLm2wxF6S+L9pqNLBjo7f9Bpd4nInYs16KWpZ 645SiL8MZ/21dHQfxyG1LNn5W0rTJ+g5TNrJSHKtgxzAZUwMAG5YdadnA4gVjdpYGRCf D1hQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=EWyKT6lV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id ji22-20020a170907981600b006e8bbf3d88fsi9370493ejc.15.2022.06.26.03.31.51; Sun, 26 Jun 2022 03:32:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=EWyKT6lV; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233081AbiFZKQC (ORCPT + 99 others); Sun, 26 Jun 2022 06:16:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51658 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229565AbiFZKQB (ORCPT ); Sun, 26 Jun 2022 06:16:01 -0400 Received: from mail-yw1-x1149.google.com (mail-yw1-x1149.google.com [IPv6:2607:f8b0:4864:20::1149]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id B1180120B2 for ; Sun, 26 Jun 2022 03:15:59 -0700 (PDT) Received: by mail-yw1-x1149.google.com with SMTP id 00721157ae682-317ab78a345so56542487b3.10 for ; Sun, 26 Jun 2022 03:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:message-id:mime-version:subject:from:to:cc; bh=A6ULT6qt3Y8m7tER4ibPrZPKIE4ZaUO512mygVxvB7M=; b=EWyKT6lVXQco7x0/YZIBkhh6XaHBmrYABXmXYWxpobNTufTvVuAh6R/hGaomB0gbk9 MoDhbR6pLqoqhC0NtIrOylctzuk6nPlCi1SMitw8nT9b8tSsOKzQkzZCf6y9QyjNGyXf 71YVbB+DiRPc7Rl/6UOPfPcl3n5D2XcNWbSEoNL+j9fL8ToVqSd77/n1ioORc/bfKoiv 2ud53+X8DXDdazBwA7IHj7f6E+V5D21cZhmhRR0IWPkZ/FLATABE8cPEtJ7J/Ngp/NJz Lf66maTxduZrOD6INDIZqgVwS/MOeXOMPx/FNSfvlDXT6OOJXSHseDvPC63ceiCvfyrP HY6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:message-id:mime-version:subject:from:to:cc; bh=A6ULT6qt3Y8m7tER4ibPrZPKIE4ZaUO512mygVxvB7M=; b=q5kctxhyHHpD5s9jSPVVuIdH1lu7TOLTmY+LRt0RGznr5MjWKQ1XeDRZZN87x3VbNw CAyGH6yk68kJxAS4hNUFn6ket9kK5PFZpWe+d+vCgvOAk4pszL2QNl4gQIkEAAVKHvBv PUgV07k+dzw5fO0lwhdqky43bPzrQFvk7zh6+ctpiq4eFa0IXCChg70gqdTSO+T6omKO hYL1eqPOU7XW9gE+3zHo2aW99mo7CypsF2fdbFSaF/BUk2xpHe0uMniQgfCXGvYN1Saw N41IZMUuwmlDu9ZcCrSYfY6JlwGSwWfz7SEbeH7OdXOxvSs+iqVm3kqzDn6vSEruhpZy KO1w== X-Gm-Message-State: AJIora8tG4eUEKxOCInGu6wBZKSeBwmDrV/jaPTwumDgjwR2GrpQHFya W/sbsfQnldKZ7W0pCIjzsKDf9ydcNb1TOg== X-Received: from slicestar.c.googlers.com ([fda3:e722:ac3:cc00:4f:4b78:c0a8:20a1]) (user=davidgow job=sendgmr) by 2002:a25:a08c:0:b0:66a:a7c3:d5a with SMTP id y12-20020a25a08c000000b0066aa7c30d5amr8229590ybh.82.1656238559009; Sun, 26 Jun 2022 03:15:59 -0700 (PDT) Date: Sun, 26 Jun 2022 18:15:53 +0800 Message-Id: <20220626101553.1885428-1-davidgow@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.37.0.rc0.161.g10f37bed90-goog Subject: [PATCH] Documentation: kunit: Cleanup run_wrapper, fix x-ref From: David Gow To: Daniel Latypov , Brendan Higgins , Shuah Khan Cc: David Gow , kunit-dev@googlegroups.com, linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org, Linux Doc Mailing List , Mauro Carvalho Chehab , Jonathan Corbet Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-9.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The "Run Tests on qemu" section of run_wrapper.rst had a few issues left over from the last big documentation refactor[1]: - It referenced a run_uml.rst page, which was integrated into the other pages (including run_wrapper.rst). - It skimmed over the use of --arch= and --cross_compile= in favour of using a custom --qemu_config. Since most users will want to use the former, let's give examples. Remove the reference to the non-existant page, and add a couple of examples to encourage the use of --arch= and --cross_compile=. With this change, there should be no more broken references in the KUnit documentation (i.e., the one mentioned in [2] is gone). [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=46201d47d6c4be594c1d57b7f3251c371626a9c4 [2]: https://lore.kernel.org/linux-doc/cover.1656234456.git.mchehab@kernel.org/ Signed-off-by: David Gow --- Thanks, Mauro, for noticing this in [2]: for whatever reason my version of Sphinx wasn't warning on it. Unless anyone objects, I'll add this to the list of things to be taken in via the kunit/kunit-fixes tree. Cheers, -- David --- Documentation/dev-tools/kunit/run_wrapper.rst | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/Documentation/dev-tools/kunit/run_wrapper.rst b/Documentation/dev-tools/kunit/run_wrapper.rst index 653985ce9cae..a695f58cd64e 100644 --- a/Documentation/dev-tools/kunit/run_wrapper.rst +++ b/Documentation/dev-tools/kunit/run_wrapper.rst @@ -192,6 +192,20 @@ via UML. To run tests on qemu, by default it requires two flags: if we have downloaded the microblaze toolchain from the 0-day website to a directory in our home directory called toolchains. +This means that for most architectures, running under qemu is as simple as: + +.. code-block:: bash + + ./tools/testing/kunit/kunit.py run --arch=x86_64 + +If a special toolchain is required, it can be slightly more complicated: + +.. code-block:: bash + + ./tools/testing/kunit/kunit.py run \ + --arch=s390 \ + --cross_compile=s390x-linux-gnu- + If we want to run KUnit tests on an architecture not supported by the ``--arch`` flag, or want to run KUnit tests on qemu using a non-default configuration; then we can write our own``QemuConfig``. @@ -214,9 +228,6 @@ as --jobs=12 \ --qemu_config=./tools/testing/kunit/qemu_configs/x86_64.py -To run existing KUnit tests on non-UML architectures, see: -Documentation/dev-tools/kunit/non_uml.rst. - Command-Line Arguments ====================== -- 2.37.0.rc0.161.g10f37bed90-goog