linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Paolo Bonzini <pbonzini@redhat.com>,
	linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: "Radim Krčmář" <rkrcmar@redhat.com>,
	"KarimAllah Ahmed" <karahmed@amazon.de>
Subject: Re: [PATCH v2 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti
Date: Mon, 29 Jan 2018 12:53:51 +0000	[thread overview]
Message-ID: <1517230431.18619.12.camel@infradead.org> (raw)
In-Reply-To: <1517043027-7655-1-git-send-email-pbonzini@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]



On Sat, 2018-01-27 at 09:50 +0100, Paolo Bonzini wrote:
> David and others,
> 
> the following changes since commit ba804bb4b72e57374b5f567b783aa0298fba0ce6:
> 
>   Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/net (2018-01-26 09:03:16 -0800)
> 
> are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/virt/kvm/kvm.git msr-bitmaps

Hm, we are pushing the other bits through tip/x86/pti, which is still
based on 4.14 so that everything can be backported easily. I was
expecting to be able to pull a clean 4.14-based tree which you had
*also* pulled into the latest kvm.git and resolved any merge issues...
but I just pulled a whole bunch of unrelated post-4.14 changes into my
working tree.

How do you want to handle this? 

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5213 bytes --]

  parent reply	other threads:[~2018-01-29 12:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-27  8:50 [PATCH v2 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Paolo Bonzini
2018-01-27  8:50 ` [PATCH v2 1/3] KVM: nVMX: Eliminate vmcs02 pool Paolo Bonzini
2018-01-27  8:50 ` [PATCH v2 2/3] KVM: VMX: introduce alloc_loaded_vmcs Paolo Bonzini
2018-01-29 10:31   ` David Hildenbrand
2018-01-27  8:50 ` [PATCH v2 3/3] KVM: VMX: make MSR bitmaps per-VCPU Paolo Bonzini
2018-01-29 10:35   ` David Hildenbrand
2018-01-30 13:07   ` [v2,3/3] " Mihai Carabas
2018-01-30 16:23   ` [PATCH v2 3/3] " Radim Krčmář
2018-01-30 16:30     ` David Woodhouse
2018-01-31 17:37     ` Paolo Bonzini
2018-01-31 18:14       ` Radim Krčmář
2018-01-29 12:53 ` David Woodhouse [this message]
2018-01-29 14:28   ` [PATCH v2 0/3] Per-VCPU MSR bitmaps patches - topic branch for x86/pti Paolo Bonzini
2018-01-29 14:57     ` David Woodhouse

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 \
    --in-reply-to=1517230431.18619.12.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=karahmed@amazon.de \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).