public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Martin <Dave.Martin@arm.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"Catalin Marinas" <Catalin.Marinas@arm.com>,
	"Marc Zyngier" <Marc.Zyngier@arm.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	"Radim Krčmář" <rkrcmar@redhat.com>,
	"KVM list" <kvm@vger.kernel.org>
Subject: Re: [GIT PULL] KVM changes for 4.18 merge window
Date: Wed, 13 Jun 2018 14:41:28 +0100	[thread overview]
Message-ID: <20180613134126.GL22983@e103592.cambridge.arm.com> (raw)
In-Reply-To: <CA+55aFxu4pD2Z8VFhojeSczb1Jf7sp9_vETvukAxFpadyj-oqw@mail.gmail.com>

On Tue, Jun 12, 2018 at 07:43:50PM +0100, Linus Torvalds wrote:
> On Tue, Jun 12, 2018 at 7:03 AM Paolo Bonzini <pbonzini@redhat.com> wrote:
> >
> >   git://git.kernel.org/pub/scm/virt/kvm/kvm.git tags/for-linus
> 
> Grr. Several tedious conflicts. I fixed them all up, and they all
> looked trivial, but since most of them were to ARM cases, I couldn't
> even test the end result.
> 
> I suspect the 'workaround_flags' could be merged into the (now)
> allegedly generic 'flags' field in the arm64 kvm_vcpu_arch structure,
> but I (obviously) didn't actually do that.

I think we decided that it was a bit premature to merge them, but we
will likely be able to do that later on.

> Adding some ARM people to the cc so that somebody on that side checks my merge.
> 
> (Still going through my basic build tests, not pushed out yet, but I'm
> assuming that will finish cleanly and it should be pushed out soon).

I've now build-tested master (f5b7769eb0) in a few configurations
(particularly KVM + !KVM) for arch/arm.  The main risk there is missing
new hooks called by the core virt/kvm/arm code.

For arm64 I've now done some basic boot/run/KVM testing as appropriate
on Juno and the Arm fast model for various configs (defconfig,
ARM64_SVE=n, KVM=n).

For the KVM/SVE interactions in particular, the merge looks good to me.

Cheers
---Dave

  reply	other threads:[~2018-06-13 13:41 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:03 [GIT PULL] KVM changes for 4.18 merge window Paolo Bonzini
2018-06-12 18:43 ` Linus Torvalds
2018-06-13 13:41   ` Dave Martin [this message]
2018-06-13  2:18 ` Linus Torvalds
2018-06-13  2:41   ` Linus Torvalds
2018-06-13  2:50     ` Wanpeng Li
2018-06-13  3:00       ` Linus Torvalds
2018-06-13  3:26         ` Linus Torvalds
2018-06-13  3:52           ` Linus Torvalds
2018-06-13  4:48             ` Greg Kroah-Hartman
2018-06-13  4:52               ` Linus Torvalds
2018-06-13 10:03                 ` Wanpeng Li
2018-06-13  4:47           ` Greg Kroah-Hartman
2018-06-13 10:09   ` Paolo Bonzini
2018-06-13 10:59     ` Vitaly Kuznetsov
2018-06-13 14:00       ` Linus Torvalds
2018-06-13 13:56     ` Linus Torvalds
2018-06-13 14:26       ` Paolo Bonzini
2018-06-13 14:29         ` Linus Torvalds

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=20180613134126.GL22983@e103592.cambridge.arm.com \
    --to=dave.martin@arm.com \
    --cc=Catalin.Marinas@arm.com \
    --cc=Marc.Zyngier@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=torvalds@linux-foundation.org \
    /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