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: <87bltxfjo3.fsf@ashishki-desk.ger.corp.intel.com>
Date:   Thu, 31 Oct 2019 09:39:24 +0200
From:   Alexander Shishkin <alexander.shishkin@...ux.intel.com>
To:     "Kang\, Luwei" <luwei.kang@...el.com>,
        Peter Zijlstra <peterz@...radead.org>
Cc:     "kvm\@vger.kernel.org" <kvm@...r.kernel.org>,
        "linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
        "pbonzini\@redhat.com" <pbonzini@...hat.com>,
        "rkrcmar\@redhat.com" <rkrcmar@...hat.com>,
        "Christopherson\, Sean J" <sean.j.christopherson@...el.com>,
        "vkuznets\@redhat.com" <vkuznets@...hat.com>,
        "wanpengli\@tencent.com" <wanpengli@...cent.com>,
        "jmattson\@google.com" <jmattson@...gle.com>,
        "joro\@8bytes.org" <joro@...tes.org>,
        "tglx\@linutronix.de" <tglx@...utronix.de>,
        "mingo\@redhat.com" <mingo@...hat.com>,
        "bp\@alien8.de" <bp@...en8.de>, "hpa\@zytor.com" <hpa@...or.com>,
        "x86\@kernel.org" <x86@...nel.org>,
        "ak\@linux.intel.com" <ak@...ux.intel.com>,
        "thomas.lendacky\@amd.com" <thomas.lendacky@....com>,
        "acme\@kernel.org" <acme@...nel.org>,
        "mark.rutland\@arm.com" <mark.rutland@....com>,
        "jolsa\@redhat.com" <jolsa@...hat.com>,
        "namhyung\@kernel.org" <namhyung@...nel.org>,
        alexander.shishkin@...ux.intel.com
Subject: RE: [PATCH v1 8/8] perf/x86: Add event owner check when PEBS output to Intel PT

"Kang, Luwei" <luwei.kang@...el.com> writes:

>> Then how does KVM deal with the host using PT? You can't just steal PT.
>
> Intel PT in virtualization can work in system and host_guest mode.
> In system mode (default), the trace produced by host and guest will be saved in host PT buffer. Intel PT will not be exposed to guest in this mode.
>  In host_guest mode, Intel PT will be exposed to guest and guest can use PT like native. The value of host PT register will be saved and guest PT register value will be restored during VM-entry. Both trace of host and guest are exported to their respective PT buffer. The host PT buffer not include guest trace in this mode.

IOW, it will steal PT from the host.

Regards,
--
Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ