From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7BA1FC433F5 for ; Mon, 9 May 2022 10:23:49 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232049AbiEIK1h (ORCPT ); Mon, 9 May 2022 06:27:37 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234173AbiEIK1M (ORCPT ); Mon, 9 May 2022 06:27:12 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 31B5E28E4D6 for ; Mon, 9 May 2022 03:22:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652091738; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=O1D+xFiUi4ihoABdmy5q5Cd5BL26SejXkNmfk43CPxo=; b=IkTZpRvZnONq+tuVwL8JaAjP//px8tKHcmNpZ0wrN8d72ewBNX0ECz7jOh8SZWK8FB2SXh 4shtA//wKSEyvnD03Q73FZ0uv9km4cflNJspGuod4pDlOLHCetUwD9vdd/TqsBDBifqOsg avD8GuCkAwJDCZFPt6UeV2AxdIp/rcg= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-646-p9vbl0osMrigf5Rne3xECQ-1; Mon, 09 May 2022 06:00:02 -0400 X-MC-Unique: p9vbl0osMrigf5Rne3xECQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 06C5C811E78; Mon, 9 May 2022 10:00:02 +0000 (UTC) Received: from localhost (unknown [10.39.193.170]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9421AC15E73; Mon, 9 May 2022 10:00:01 +0000 (UTC) From: Cornelia Huck To: Mark Brown Cc: Catalin Marinas , Will Deacon , Shuah Khan , Joey Gouly , linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org Subject: Re: [ARM64] status of MTE selftests? In-Reply-To: Organization: Red Hat GmbH References: <87wney4svy.fsf@redhat.com> User-Agent: Notmuch/0.34 (https://notmuchmail.org) Date: Mon, 09 May 2022 11:59:59 +0200 Message-ID: <87levb3u1s.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 Precedence: bulk List-ID: X-Mailing-List: linux-kselftest@vger.kernel.org On Fri, May 06 2022, Mark Brown wrote: > On Fri, May 06, 2022 at 04:50:41PM +0200, Cornelia Huck wrote: > >> I'm currently trying to run the MTE selftests on the FVP simulator (Base >> Model)[1], mainly to verify things are sane on the host before wiring up >> the KVM support in QEMU. However, I'm seeing some failures (the non-mte >> tests seemed all fine): > >> Are the MTE tests supposed to work on the FVP model? Something broken in >> my config? Anything I can debug? > > I would expect them to work, they seemed happy when I was doing > the async mode support IIRC and a quick spin with -next in qemu > everything seems fine, I'm travelling so don't have the > environment for models to hand right now. Thanks; I think that points to some setup/config problem on my side, then :/ (I ran the selftests under QEMU's tcg emulation, and while it looks better, I still get timeouts for check_gcr_el1_cswitch and check_user_mem.) > >> [1] Command line: >> "$MODEL" \ >> -C cache_state_modelled=0 \ >> -C bp.refcounter.non_arch_start_at_default=1 \ >> -C bp.secure_memory=false \ >> -C cluster0.has_arm_v8-1=1 \ >> -C cluster0.has_arm_v8-2=1 \ >> -C cluster0.has_arm_v8-3=1 \ >> -C cluster0.has_arm_v8-4=1 \ >> -C cluster0.has_arm_v8-5=1 \ >> -C cluster0.has_amu=1 \ >> -C cluster0.NUM_CORES=4 \ >> -C cluster0.memory_tagging_support_level=2 \ >> -a "cluster0.*=$AXF" \ > >> where $AXF contains a kernel at v5.18-rc5-16-g107c948d1d3e[2] and an >> initrd built by mbuto[3] from that level with a slightly tweaked "kselftests" >> profile (adding /dev/shm). > > What are you using for EL3 with the model? Both TF-A and > boot-wrapper are in regular use, TF-A gets *way* more testing > than boot-wrapper which is mostly used by individual developers. I'm building the .axf via boot-wrapper-aarch64 (enabling psci and gicv3, if that matters.) Didn't try to make use of TF-A yet beyond the dtb (I'm still in the process of getting familiar with the arm64 world, so I'm currently starting out with the setups that others had shared with me.) From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 96270C433F5 for ; Mon, 9 May 2022 10:01:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-ID:Date:References :In-Reply-To:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=Ch16p5NM6FxpYOnXYluZX6cFADzUxDQfg0lQskWh0UU=; b=LcR66YNIX2xTMS rlXxPpCQyrn3er+XchNDNkHsXpLMdlnBUiZETr8sRXDYm+5z/x+Bcrn+5C6BerniFDPet2U37cH9u iK8eozIsvQ1R0XVkqJP6SoKKm+8TH8vV241opRQYo9l8jlQSMXYxpNZ3gMhF3Bwzvo+C7Q7DLlbol NF/X58MdFFs+qAFjbcZD8mE8wN1xxl2bqkQHHTYI8lqUIhSbS+xaAnJ4s391iDtfcZj2TUCSjAUWu ylYx+lelALIqQJhumcAg67dKMdwaGhy9+VoT22qhcmzX/QsPu/naJRgPzfdXCv2VYeMWK0nB4gDs+ XCSWAJNC82BCstLrNFag==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1no0BZ-00DdWE-6Q; Mon, 09 May 2022 10:00:13 +0000 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1no0BS-00DdU1-Ry for linux-arm-kernel@lists.infradead.org; Mon, 09 May 2022 10:00:08 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1652090404; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=O1D+xFiUi4ihoABdmy5q5Cd5BL26SejXkNmfk43CPxo=; b=OxBv3FejcGrjdjO6e8EEuRV9tU71JHjXUjIqqELKgRuqKGhSBX6ZqbUNui/PAM6WMuMdC9 Weq56zG7baei8z4Z+4MuTJjU0cEfPB1OWIHMVegzQDvTK+49zVh7btZQVmtMeJQhL6rlY4 62eTWvt+SbxFqpEUDRBQSnp26k4U5OQ= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-646-p9vbl0osMrigf5Rne3xECQ-1; Mon, 09 May 2022 06:00:02 -0400 X-MC-Unique: p9vbl0osMrigf5Rne3xECQ-1 Received: from smtp.corp.redhat.com (int-mx08.intmail.prod.int.rdu2.redhat.com [10.11.54.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 06C5C811E78; Mon, 9 May 2022 10:00:02 +0000 (UTC) Received: from localhost (unknown [10.39.193.170]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9421AC15E73; Mon, 9 May 2022 10:00:01 +0000 (UTC) From: Cornelia Huck To: Mark Brown Cc: Catalin Marinas , Will Deacon , Shuah Khan , Joey Gouly , linux-arm-kernel@lists.infradead.org, linux-kselftest@vger.kernel.org Subject: Re: [ARM64] status of MTE selftests? In-Reply-To: Organization: Red Hat GmbH References: <87wney4svy.fsf@redhat.com> User-Agent: Notmuch/0.34 (https://notmuchmail.org) Date: Mon, 09 May 2022 11:59:59 +0200 Message-ID: <87levb3u1s.fsf@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.85 on 10.11.54.8 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220509_030007_044613_54599A97 X-CRM114-Status: GOOD ( 20.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, May 06 2022, Mark Brown wrote: > On Fri, May 06, 2022 at 04:50:41PM +0200, Cornelia Huck wrote: > >> I'm currently trying to run the MTE selftests on the FVP simulator (Base >> Model)[1], mainly to verify things are sane on the host before wiring up >> the KVM support in QEMU. However, I'm seeing some failures (the non-mte >> tests seemed all fine): > >> Are the MTE tests supposed to work on the FVP model? Something broken in >> my config? Anything I can debug? > > I would expect them to work, they seemed happy when I was doing > the async mode support IIRC and a quick spin with -next in qemu > everything seems fine, I'm travelling so don't have the > environment for models to hand right now. Thanks; I think that points to some setup/config problem on my side, then :/ (I ran the selftests under QEMU's tcg emulation, and while it looks better, I still get timeouts for check_gcr_el1_cswitch and check_user_mem.) > >> [1] Command line: >> "$MODEL" \ >> -C cache_state_modelled=0 \ >> -C bp.refcounter.non_arch_start_at_default=1 \ >> -C bp.secure_memory=false \ >> -C cluster0.has_arm_v8-1=1 \ >> -C cluster0.has_arm_v8-2=1 \ >> -C cluster0.has_arm_v8-3=1 \ >> -C cluster0.has_arm_v8-4=1 \ >> -C cluster0.has_arm_v8-5=1 \ >> -C cluster0.has_amu=1 \ >> -C cluster0.NUM_CORES=4 \ >> -C cluster0.memory_tagging_support_level=2 \ >> -a "cluster0.*=$AXF" \ > >> where $AXF contains a kernel at v5.18-rc5-16-g107c948d1d3e[2] and an >> initrd built by mbuto[3] from that level with a slightly tweaked "kselftests" >> profile (adding /dev/shm). > > What are you using for EL3 with the model? Both TF-A and > boot-wrapper are in regular use, TF-A gets *way* more testing > than boot-wrapper which is mostly used by individual developers. I'm building the .axf via boot-wrapper-aarch64 (enabling psci and gicv3, if that matters.) Didn't try to make use of TF-A yet beyond the dtb (I'm still in the process of getting familiar with the arm64 world, so I'm currently starting out with the setups that others had shared with me.) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel