[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <YjTUhRLmpP3PQbKr@zn.tnic>
Date: Fri, 18 Mar 2022 19:50:45 +0100
From: Borislav Petkov <bp@...en8.de>
To: Dongli Si <kvmx86@...il.com>
Cc: acme@...nel.org, alexander.shishkin@...ux.intel.com,
dave.hansen@...ux.intel.com, hpa@...or.com, joerg.roedel@....com,
jolsa@...nel.org, kim.phillips@....com, liam.merwick@...cle.com,
linux-kernel@...r.kernel.org, linux-perf-users@...r.kernel.org,
mark.rutland@....com, mingo@...nel.org, namhyung@...nel.org,
peterz@...radead.org, tglx@...utronix.de, x86@...nel.org
Subject: Re: [PATCH v3] perf/x86/amd: Don't touch the Host-only bit inside
the guest hypervisor
On Fri, Mar 18, 2022 at 11:07:57AM +0800, Dongli Si wrote:
> Hi Borislav, this is just to more clearly test if the current kernel is
> running directly on the host.
>
> If this is redundant, I can remove this "wrapper" and resend the patch,
> the v4 patch code will be the same as the v1 patch.
Yes please. Using
hypervisor_is_type(X86_HYPER_NATIVE)
directly is a lot more descriptive than "run_as_host".
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists