From patchwork Fri Sep 22 09:37:19 2023 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: David Marchand X-Patchwork-Id: 173 Return-Path: X-Original-To: patchwork@inbox.dpdk.org Delivered-To: patchwork@inbox.dpdk.org Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id DD66542616; Fri, 22 Sep 2023 11:37:40 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id C6F414029C; Fri, 22 Sep 2023 11:37:40 +0200 (CEST) Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mails.dpdk.org (Postfix) with ESMTP id 3C11B40150 for ; Fri, 22 Sep 2023 11:37:39 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1695375458; 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; bh=kel2F4VZyTLooM9aBKnp6vAaa0imqQy9qnh0bCmgUhw=; b=OyOFoyAZgsyt8XEK4s00pUwFycW7FDsDY1uXuwS8pvG5Qvx563hEmOf1GY5WuB1HVFN3j7 TszvpHNs0kdb1qLv3otLrmFL71NT9jW2wQLTC175pNrBX5VfWJB1KRLq2tGtPbzz7cMsRf TK33r9mE1AQNyjBSqJPeXulauz7POVM= Received: from mimecast-mx02.redhat.com (mx-ext.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-357-LAJ_Gd5wPmS3YDTcxrfNWg-1; Fri, 22 Sep 2023 05:37:35 -0400 X-MC-Unique: LAJ_Gd5wPmS3YDTcxrfNWg-1 Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.rdu2.redhat.com [10.11.54.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 7B64E3C11C71; Fri, 22 Sep 2023 09:37:34 +0000 (UTC) Received: from dmarchan.redhat.com (unknown [10.45.224.128]) by smtp.corp.redhat.com (Postfix) with ESMTP id 844A52156701; Fri, 22 Sep 2023 09:37:30 +0000 (UTC) From: David Marchand To: dev@dpdk.org Cc: ferruh.yigit@amd.com, thomas@monjalon.net, bruce.richardson@intel.com, konstantin.v.ananyev@yandex.ru, ruifeng.wang@arm.com, zhoumin@loongson.cn, drc@linux.vnet.ibm.com, kda@semihalf.com, roretzla@linux.microsoft.com Subject: [PATCH 0/2] Introduce x86 specific identification API Date: Fri, 22 Sep 2023 11:37:19 +0200 Message-ID: <20230922093722.2057688-1-david.marchand@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.6 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com 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 Rather than have every driver implement their own set of cpuid() ugly stuff, provide an abstracted (gcc/clang vs MSVC) API for querying about x86 processor details. Note: - coming up with a cross arch API seems a difficult task, hence a arch specific API has been preferred. If other arches have ideas how to abstract I am open to suggestions though I won't have the time to implement it for this release, - usage of this arch specific API must not become the common practice and maintainers will have to be wary that drivers are still working fine with generic/common processor/arch features,