From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: Alexey Kardashevskiy <aik@amd.com>,
x86@kernel.org, linux-kernel@vger.kernel.org,
Ingo Molnar <mingo@redhat.com>,
Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest
Date: Sun, 1 Oct 2023 14:17:50 +0200 [thread overview]
Message-ID: <ZRljbqRbaj+eoUU6@gmail.com> (raw)
In-Reply-To: <20231001095322.GAZRlBkle6JC2rfM6u@fat_crate.local>
* Borislav Petkov <bp@alien8.de> wrote:
> On Sun, Oct 01, 2023 at 08:40:30PM +1100, Alexey Kardashevskiy wrote:
> > Ingo says different, who wins? :)
>
> I do: a function gives you type checking - a macro doesn't.
That's false, because this specific macro don't force any types, it
only passes types through as-is to type-checked functions, so both
the macro and the function variant does similar quality of type
checking ...
But I'm fine with both approaches, I suggested a macro because the
existing rdtsc definitions used macros already - but I have no
strong feelings which particular color this shed gets painted ...
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-01 12:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-26 4:05 [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest Alexey Kardashevskiy
2023-09-26 18:28 ` Tom Lendacky
2023-09-27 8:50 ` [tip: x86/mm] x86/sev: Reduce #VC nesting for intercepted CPUID for SEV-SNP guest, to fix nesting crash tip-bot2 for Alexey Kardashevskiy
2023-09-27 9:48 ` [PATCH kernel v2] x86/compressed/64: reduce #VC nesting for intercepted CPUID for SEV-SNP guest Ingo Molnar
2023-09-27 11:22 ` Borislav Petkov
2023-09-28 9:32 ` Ingo Molnar
2023-09-30 7:17 ` Borislav Petkov
2023-10-01 9:40 ` Alexey Kardashevskiy
2023-10-01 9:53 ` Borislav Petkov
2023-10-01 12:17 ` Ingo Molnar [this message]
2023-10-01 12:31 ` Ingo Molnar
2023-10-03 1:45 ` Alexey Kardashevskiy
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=ZRljbqRbaj+eoUU6@gmail.com \
--to=mingo@kernel.org \
--cc=aik@amd.com \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=thomas.lendacky@amd.com \
--cc=x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox