From: Sean Christopherson <seanjc@google.com>
To: Sasha Levin <sashal@kernel.org>
Cc: linux-kernel@vger.kernel.org, Borislav Petkov <bp@alien8.de>,
Chuck Wolber <chuck@wolber.net>,
Dave Hansen <dave.hansen@linux.intel.com>,
"H. Peter Anvin" <hpa@zytor.com>, Ingo Molnar <mingo@redhat.com>,
kvm@vger.kernel.org, Marco Elver <elver@google.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@kernel.org>,
x86@kernel.org
Subject: Re: [PATCH v2 10/20] x86/sev: Use non-instrumented bitops in the GHCB accessors
Date: Wed, 4 Nov 2026 05:36:29 -0800 [thread overview]
Message-ID: <aus03eVALC1m86Aa@google.com> (raw)
In-Reply-To: <20261103015238.3780910-11-sashal@kernel.org>
On Mon, Nov 02, 2026, Sasha Levin wrote:
> The GHCB accessors are used from noinstr code, such as
> __sev_es_nmi_complete(), but use test_bit() and __set_bit(), which
> call the KASAN and KCSAN checks. arch/x86/coco/sev/Makefile disables
> KASAN and KCSAN for noinstr.o, which turns those checks into empty
> stubs, but they still have to be inlined. Instrumentation such as gcov
> can prevent that and leave calls to kasan_check_write() behind in
> noinstr code.
>
> Use the arch_ bitops, which aren't instrumented, as is done elsewhere
> for noinstr code.
>
> Signed-off-by: Sasha Levin <sashal@kernel.org>
> ---
Reviewed-by: Sean Christopherson <seanjc@google.com>
prev parent reply other threads:[~2026-11-04 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20261103015238.3780910-1-sashal@kernel.org>
2026-11-03 1:52 ` [PATCH v2 10/20] x86/sev: Use non-instrumented bitops in the GHCB accessors Sasha Levin
2026-11-04 13:36 ` Sean Christopherson [this message]
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=aus03eVALC1m86Aa@google.com \
--to=seanjc@google.com \
--cc=bp@alien8.de \
--cc=chuck@wolber.net \
--cc=dave.hansen@linux.intel.com \
--cc=elver@google.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=sashal@kernel.org \
--cc=tglx@kernel.org \
--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