From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 5AF63425E9; Mon, 25 Sep 2023 11:53:48 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id CB205402CC; Mon, 25 Sep 2023 11:53:47 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mails.dpdk.org (Postfix) with ESMTP id 8B3B9402B7 for ; Mon, 25 Sep 2023 11:53:45 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1695635624; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=YWVptou5ddYPYtHV7HgTk7SBzpKEr/Z/Uzc8xE8W3m8=; b=SAFmPOaQgBt5R8TOdlBUArM+u1rpyhHTemqOmKyL2t1dIENHbxZ07ki1SMv08lsDCurGpk 2qNWOhkA0H4v6wYzRsD4/4xGNCVlPea7vxGWFpYoxHIRc0jgjn7ybCbbkwkFAacxsYNyEN U8ZbN12wb/QcGYRvgCxTtdzfkNdHOvo= Received: from mail-lj1-f200.google.com (mail-lj1-f200.google.com [209.85.208.200]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-32-qC1_l3XyP6WJCDDonEW77A-1; Mon, 25 Sep 2023 05:53:43 -0400 X-MC-Unique: qC1_l3XyP6WJCDDonEW77A-1 Received: by mail-lj1-f200.google.com with SMTP id 38308e7fff4ca-2bfdcba1144so83790861fa.1 for ; Mon, 25 Sep 2023 02:53:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1695635622; x=1696240422; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=YWVptou5ddYPYtHV7HgTk7SBzpKEr/Z/Uzc8xE8W3m8=; b=TGeFczvXZRozMiAXhUAXaTIjkFqhKSxYBG3CwHW5gBaZsdiP8YIas0uQ2RNfOpMJ0j ssO+XXq5h1jAbzNXDLrj3HiRyi+ySw4lYxIL8fosKTuGOaJPoj6+1SnfbQMdbsYGJ+LN mFUW1zRli5z32fTzTBMCZYjcoYftE0iIoDbhPapqDVrbtUGhV4F0S0z3DoMDxCXokqYX 2l9LRyhjJqaoH/0HrlIS115tdLUxsdqpt38cdBnF12g40QPwTpjJtrJLM6i/QjyKUvC0 TN9qX6ufB6ZgmsYBhcih/ERCcLDP3CMNquyi+PqD8Adcybs+KubgGlKff2sEknznQWS7 e9lQ== X-Gm-Message-State: AOJu0YzgKGYZmEBbpOVvwTHt/OIY6ySvziq8HzzCP9JQ7SZOHjUOnPUX zXz/PmtrWWpuMJeUCnZN1BDjQgEjr9E5mWiDX5sAUJQU2EjabgU21QBXtBocplc21FBxH5gM3mG qzyVp4ppNpNDtHLC/8HELFic4CjkAxQ== X-Received: by 2002:a2e:9d87:0:b0:2bc:d8cb:5a13 with SMTP id c7-20020a2e9d87000000b002bcd8cb5a13mr5498774ljj.42.1695635621807; Mon, 25 Sep 2023 02:53:41 -0700 (PDT) X-Google-Smtp-Source: AGHT+IG1N7Ob9viTUMsofgGnfhrJn4JuVbWBvGTCZPeUMnmlMSTjrDm9HCLVK7L1GxcHbKbehC7cPKzG+BHlyQSu72Y= X-Received: by 2002:a2e:9d87:0:b0:2bc:d8cb:5a13 with SMTP id c7-20020a2e9d87000000b002bcd8cb5a13mr5498759ljj.42.1695635621463; Mon, 25 Sep 2023 02:53:41 -0700 (PDT) MIME-Version: 1.0 References: <089a8254-82e8-44a1-9641-4b6da6515dde@aakef.fastmail.fm> In-Reply-To: <089a8254-82e8-44a1-9641-4b6da6515dde@aakef.fastmail.fm> From: David Marchand Date: Mon, 25 Sep 2023 11:53:30 +0200 Message-ID: Subject: Re: SIGILL in rte_cpu_get_flag_enabled / RTE_CPUFLAG_RTM To: Bernd Schubert Cc: dev@dpdk.org X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org On Fri, Sep 22, 2023 at 7:48=E2=80=AFPM Bernd Schubert wrote: > > I'm trying to compile our tools on an older lab system and get > > Program received signal SIGILL, Illegal instruction. > 0x00007ffff434c766 in rte_cpu_get_flag_enabled (feature=3Dfeature@entry= =3DRTE_CPUFLAG_RTM) at ../lib/eal/x86/rte_cpuflags.c:173 > 173 return (regs[feat->reg] >> feat->bit) & 1; > (gdb) bt > #0 0x00007ffff434c766 in rte_cpu_get_flag_enabled (feature=3Dfeature@ent= ry=3DRTE_CPUFLAG_RTM) at ../lib/eal/x86/rte_cpuflags.c:173 > #1 0x00007ffff3ffb572 in rte_rtm_init () at ../lib/eal/x86/rte_spinlock.= c:14 > ##2 0x00007ffff7fc947e in call_init (l=3D, argc=3Dargc@en= try=3D1, argv=3Dargv@entry=3D0x7fffffffe088, env=3Denv@entry=3D0x7fffffffe0= 98) > at ./elf/dl-init.c:70 > #3 0x00007ffff7fc9568 in call_init (env=3D0x7fffffffe098, argv=3D0x7ffff= fffe088, argc=3D1, l=3D) at ./elf/dl-init.c:33 > #4 _dl_init (main_map=3D0x7ffff7ffe2e0, argc=3D1, argv=3D0x7fffffffe088,= env=3D0x7fffffffe098) at ./elf/dl-init.c:117 > #5 0x00007ffff7fe32ea in _dl_start_user () from /lib64/ld-linux-x86-64.s= o.2 > > > This already has been reported here > https://inbox.dpdk.org/users/C7FF2508-D633-404E-95AF-5F604D8E8E4B@intel.c= om/t/ > but I don't see a solution there. It just ends up asking for the line num= bers. > Well, the line is > > > __cpuid_count(feat->leaf, feat->subleaf, > regs[RTE_REG_EAX], regs[RTE_REG_EBX], > regs[RTE_REG_ECX], regs[RTE_REG_EDX]); > > /* check if the feature is enabled */ > return (regs[feat->reg] >> feat->bit) & 1; =3D=3D=3D=3D> line 173 > > > Maybe this should catch SIGILL? SIGILL is a sign that some unsupported instruction (for your old cpu) has been executed. Did you try building dpdk with -Dplatform=3Dgeneric meson option? --=20 David Marchand