All of lore.kernel.org
 help / color / mirror / Atom feed
From: Reinette Chatre <reinette.chatre@intel.com>
To: Jarkko Sakkinen <jarkko@kernel.org>, Shuah Khan <shuah@kernel.org>
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	<linux-kselftest@vger.kernel.org>, <linux-sgx@vger.kernel.org>
Subject: Re: [PATCH] selftests/sgx: Fix corrupted cpuid macro invocation
Date: Sat, 4 Dec 2021 16:32:59 -0800	[thread overview]
Message-ID: <c5792b66-4a27-0a62-bb75-6cc0c4219002@intel.com> (raw)
In-Reply-To: <20211204202355.23005-1-jarkko@kernel.org>

Hi Jarkko,

(Dave: I am very sorry - selftests on x86/sgx on tip.git is currently 
broken because of this)

On 12/4/2021 12:23 PM, Jarkko Sakkinen wrote:
> Compilation results:
> 
> $ make -C tools/testing/selftests/sgx/
> make: Entering directory '/home/jarkko/Projects/linux-sgx/tools/testing/selftests/sgx'
> gcc -Wall -Werror -g -I../../../../tools/include -fPIC -z noexecstack -c main.c -o /home/jarkko/Projects/linux-sgx/tools/testing/selftests/sgx/main.o
> main.c: In function ‘get_total_epc_mem’:
> main.c:296:17: error: implicit declaration of function ‘__cpuid’ [-Werror=implicit-function-declaration]
>    296 |                 __cpuid(&eax, &ebx, &ecx, &edx);
>        |                 ^~~~~~~
> cc1: all warnings being treated as errors
> make: *** [Makefile:33: /home/jarkko/Projects/linux-sgx/tools/testing/selftests/sgx/main.o] Error 1
> make: Leaving directory '/home/jarkko/Projects/linux-sgx/tools/testing/selftests/sgx'
> 
> Include to cpuid.h is missing and the macro usage is incorrect.
> 
> Include cpuid.h and use __cpuid_count() macro in order to fix the
> compilation issue.
> 
> Fixes: f0ff2447b861 ("selftests/sgx: Add a new kselftest: Unclobbered_vdso_oversubscribed")
> Signed-off-by: Jarkko Sakkinen <jarkko@kernel.org>

I am sorry - this was my mistake because of a last minute change to that 
patch that I submitted with a dependency that only arrives in a later 
patch that is not upstream yet.

Jarkko, thank you very much for catching this.

I am not sure what the right way is to fix it though - my original 
intention, what the code uses, was to add a snippet as below as is the 
custom for all tests needing to run cpuid. There are many usages of 
cpuid among the selftests but none rely on the cpuid.h to bring in 
__cpuid_count. I do not know the motivation for this but preferred to 
stick with the custom for my implementation.

+static inline void __cpuid(unsigned int *eax, unsigned int *ebx,
+			   unsigned int *ecx, unsigned int *edx)
+{
+	asm volatile("cpuid"
+	    : "=a" (*eax),
+	      "=b" (*ebx),
+	      "=c" (*ecx),
+	      "=d" (*edx)
+	    : "0" (*eax), "2" (*ecx)
+	    : "memory");
+}


Reinette

  reply	other threads:[~2021-12-05  0:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-04 20:23 [PATCH] selftests/sgx: Fix corrupted cpuid macro invocation Jarkko Sakkinen
2021-12-05  0:32 ` Reinette Chatre [this message]
2021-12-06 22:54   ` Dave Hansen
2021-12-06 23:32     ` Reinette Chatre
2021-12-06 23:36       ` Dave Hansen
2021-12-15  0:19 ` Reinette Chatre
2021-12-22  0:40   ` Jarkko Sakkinen
2021-12-17 16:58 ` [tip: x86/sgx] " tip-bot2 for Jarkko Sakkinen

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=c5792b66-4a27-0a62-bb75-6cc0c4219002@intel.com \
    --to=reinette.chatre@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=jarkko@kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-sgx@vger.kernel.org \
    --cc=shuah@kernel.org \
    /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.