linux-kernel - Re: [PATCH v7 06/13] KVM: x86: Add Intel Processor Trace virtualization mode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <26505f7a-9e6b-efb9-e5f9-8aae3756be49@redhat.com>
Date:   Thu, 3 May 2018 14:50:12 +0200
From:   Paolo Bonzini <pbonzini@...hat.com>
To:     Alexander Shishkin <alexander.shishkin@...ux.intel.com>
Cc:     Luwei Kang <luwei.kang@...el.com>, kvm@...r.kernel.org,
        tglx@...utronix.de, mingo@...hat.com, hpa@...or.com,
        x86@...nel.org, rkrcmar@...hat.com, linux-kernel@...r.kernel.org,
        joro@...tes.org, peterz@...radead.org, chao.p.peng@...ux.intel.com
Subject: Re: [PATCH v7 06/13] KVM: x86: Add Intel Processor Trace
 virtualization mode

On 03/05/2018 14:48, Alexander Shishkin wrote:
>> Guest tracing can only be enabled at boot time, because the guest's
>> CPUID changes depending on whether it's enabled.  And likewise if perf
>> record can do system-wide tracing at any time during the guest's
>> execution, we need to know it at boot time in order to set the guest CPUID.
>
> CPUID is immaterial here; the real trick is to disallow the use of PT at
> runtime when the host suddenly decides to trace the guest, in such a way
> that the guest user is informed that their trace is incomplete due to the
> host activity.

How do you do that?  And you still need the module parameter to decide
whether the host is _allowed_ to cause incomplete traces in the guest.

Paolo

> Side note: the "system-wide tracing" is a misnomer here, all that matters
> is that there's a perf event on the host that wants to trace the guest, it
> can very well be a per-task event.