From: Paolo Bonzini <email@example.com> To: Thomas Gleixner <firstname.lastname@example.org>, Borislav Petkov <email@example.com> Cc: Chenyi Qiang <firstname.lastname@example.org>, Sean Christopherson <email@example.com>, Vitaly Kuznetsov <firstname.lastname@example.org>, Wanpeng Li <email@example.com>, Jim Mattson <firstname.lastname@example.org>, Joerg Roedel <email@example.com>, Xiaoyao Li <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, "email@example.com" <firstname.lastname@example.org>, Andy Lutomirski <email@example.com> Subject: Re: [PATCH v4 2/5] KVM: X86: Expose PKS to guest Date: Fri, 5 Feb 2021 12:51:52 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> On 05/02/21 12:29, Thomas Gleixner wrote: > On Fri, Feb 05 2021 at 11:10, Paolo Bonzini wrote: >> On 05/02/21 10:56, Borislav Petkov wrote: >>>> This would need an ack from the x86 people. Andy, Boris? >>> >>> This looks like the PKS baremetal pile needs to be upstream first. >> >> Yes, it does. I would like to have an ack for including the above two >> hunks once PKS is upstream. >> >> I also have CET and bus lock #DB queued and waiting for the bare metal >> functionality, however they do not touch anything outside arch/x86/kvm. > > What's the exact point of queueing random stuff which lacks bare metal > support? The code is often completely independent of bare metal support even if it depends of it (CET and bus lock for example only share the #defines; for PKS this is not the case just because Intel decided not to use XSAVES *shrug*). I prefer to queue early, because it keeps my backlog small and because every resend comes with the risk of random changes sneaking in since the version that I reviewed. An early ack would also mean that I don't have to bug you in the middle of the merge window. But it's not a problem, I'll ask for acks again once PKS is merged into tip. Thanks, Paolo > Once PKS, CET or whatever is merged into tip then it's the point for > resending the KVM patches for inclusion and that's the point where it > gets acked and not $N month ahead when everything is still in flux.
next prev parent reply other threads:[~2021-02-05 11:56 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-02-05 8:37 [PATCH v4 0/5] KVM: PKS Virtualization support Chenyi Qiang 2021-02-05 8:37 ` [PATCH v4 1/5] KVM: VMX: Introduce PKS VMCS fields Chenyi Qiang 2021-02-05 8:37 ` [PATCH v4 2/5] KVM: X86: Expose PKS to guest Chenyi Qiang 2021-02-05 9:23 ` Paolo Bonzini 2021-02-05 9:25 ` Paolo Bonzini 2021-02-05 9:56 ` Borislav Petkov 2021-02-05 10:10 ` Paolo Bonzini 2021-02-05 11:29 ` Thomas Gleixner 2021-02-05 11:51 ` Paolo Bonzini [this message] 2021-07-29 16:44 ` Sean Christopherson 2021-08-03 8:50 ` Chenyi Qiang 2021-02-05 8:37 ` [PATCH v4 3/5] KVM: MMU: Rename the pkru to pkr Chenyi Qiang 2021-02-05 8:37 ` [PATCH v4 4/5] KVM: MMU: Add support for PKS emulation Chenyi Qiang 2021-02-05 9:20 ` Paolo Bonzini 2021-07-29 17:25 ` Sean Christopherson 2021-07-29 17:45 ` Paolo Bonzini 2021-08-03 8:52 ` Chenyi Qiang 2021-02-05 8:37 ` [PATCH v4 5/5] KVM: VMX: Enable PKS for nested VM Chenyi Qiang 2021-02-05 9:24 ` [PATCH v4 0/5] KVM: PKS Virtualization support Paolo Bonzini
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [PATCH v4 2/5] KVM: X86: Expose PKS to guest' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).