Message ID | 20190301052130.GA22341@blackberry |
---|---|
State | Accepted |
Headers | show |
Series | [GIT,PULL] Please pull my kvm-ppc-next-5.1-3 tag | expand |
On Fri, Mar 01, 2019 at 04:21:30PM +1100, Paul Mackerras wrote: > Paolo & Radim, > > Immediately after I sent my previous pull request, I saw that Suraj > had posted a patch that advertises a new mitigation for one of the > spectre vulnerabilities to userspace. The code for the host to know > about and use this new mitigation went into 4.19. Since the patch is > low-risk and security-related, I would like to get it into 5.1. With > this patch and a related QEMU patch, guests will be able to use this > new mitigation on machines that support it. > > So, please do a pull from my kvm-ppc-next-5.1-3 tag to get this > commit. (If you haven't already pulled the 5.1-2 tag then you will > get the compile fix as well, of course.) > > Thanks, > Paul. Ping? Also, if you have sent a pull request to Linus for the 5.1 merge window, I missed it. Has that been sent? Regards, Paul. > The following changes since commit e74d53e30e2927fa5b223296ac7922baf15ea89a: > > KVM: PPC: Fix compilation when KVM is not enabled (2019-02-27 09:14:44 +1100) > > are available in the git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.1-3 > > for you to fetch changes up to 2b57ecd0208f7ac0b20b1b171698f027481a39f6: > > KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char() (2019-03-01 15:11:14 +1100) > > ---------------------------------------------------------------- > Third PPC KVM update for 5.1 > > - Tell userspace about whether a particular hardware workaround for > one of the Spectre vulnerabilities is available, so that userspace > can inform the guest. > > ---------------------------------------------------------------- > Suraj Jitindar Singh (1): > KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char() > > arch/powerpc/include/uapi/asm/kvm.h | 2 ++ > arch/powerpc/kvm/powerpc.c | 18 ++++++++++++++---- > 2 files changed, 16 insertions(+), 4 deletions(-)
On 14/03/19 04:31, Paul Mackerras wrote: > On Fri, Mar 01, 2019 at 04:21:30PM +1100, Paul Mackerras wrote: >> Paolo & Radim, >> >> Immediately after I sent my previous pull request, I saw that Suraj >> had posted a patch that advertises a new mitigation for one of the >> spectre vulnerabilities to userspace. The code for the host to know >> about and use this new mitigation went into 4.19. Since the patch is >> low-risk and security-related, I would like to get it into 5.1. With >> this patch and a related QEMU patch, guests will be able to use this >> new mitigation on machines that support it. >> >> So, please do a pull from my kvm-ppc-next-5.1-3 tag to get this >> commit. (If you haven't already pulled the 5.1-2 tag then you will >> get the compile fix as well, of course.) >> >> Thanks, >> Paul. > > Ping? > > Also, if you have sent a pull request to Linus for the 5.1 merge > window, I missed it. Has that been sent? > > Regards, > Paul. > >> The following changes since commit e74d53e30e2927fa5b223296ac7922baf15ea89a: >> >> KVM: PPC: Fix compilation when KVM is not enabled (2019-02-27 09:14:44 +1100) >> >> are available in the git repository at: >> >> git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc tags/kvm-ppc-next-5.1-3 >> >> for you to fetch changes up to 2b57ecd0208f7ac0b20b1b171698f027481a39f6: >> >> KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char() (2019-03-01 15:11:14 +1100) >> >> ---------------------------------------------------------------- >> Third PPC KVM update for 5.1 >> >> - Tell userspace about whether a particular hardware workaround for >> one of the Spectre vulnerabilities is available, so that userspace >> can inform the guest. >> >> ---------------------------------------------------------------- >> Suraj Jitindar Singh (1): >> KVM: PPC: Book3S: Add count cache flush parameters to kvmppc_get_cpu_char() >> >> arch/powerpc/include/uapi/asm/kvm.h | 2 ++ >> arch/powerpc/kvm/powerpc.c | 18 ++++++++++++++---- >> 2 files changed, 16 insertions(+), 4 deletions(-) Pulled now, thanks. Paolo