From: Marc Zyngier <maz@kernel.org>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, aleksandar.qemu.devel@gmail.com,
alexandru.elisei@arm.com, anup@brainfault.org,
aou@eecs.berkeley.edu, atishp@atishpatra.org,
benh@kernel.crashing.org, borntraeger@linux.ibm.com,
bp@alien8.de, catalin.marinas@arm.com, chenhuacai@kernel.org,
dave.hansen@linux.intel.com, frederic@kernel.org,
hca@linux.ibm.com, james.morse@arm.com, jmattson@google.com,
joro@8bytes.org, mingo@redhat.com, mpe@ellerman.id.au,
nsaenzju@redhat.com, palmer@dabbelt.com, paulmck@kernel.org,
paulus@samba.org, paul.walmsley@sifive.com, seanjc@google.com,
suzuki.poulose@arm.com, svens@linux.ibm.com, tglx@linutronix.de,
tsbogend@alpha.franken.de, vkuznets@redhat.com,
wanpengli@tencent.com, will@kernel.org
Subject: Re: [PATCH v3 0/5] kvm: fix latent guest entry/exit bugs
Date: Tue, 01 Feb 2022 17:48:01 +0000 [thread overview]
Message-ID: <87czk65vhq.wl-maz@kernel.org> (raw)
In-Reply-To: <c1371392-70ff-0a14-68cd-aa253998d271@redhat.com>
On Tue, 01 Feb 2022 17:10:35 +0000,
Paolo Bonzini <pbonzini@redhat.com> wrote:
>
> On 2/1/22 17:22, Mark Rutland wrote:
> > On Tue, Feb 01, 2022 at 04:59:47PM +0100, Paolo Bonzini wrote:
> >> On 2/1/22 14:29, Mark Rutland wrote:
> >>> I've pushed the series (based on v5.17-rc2) to my kvm/entry-rework branch:
> >>>
> >>> https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/log/?h=kvm/entry-rework
> >>> git://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git kvm/entry-rework
> >>
> >> Thanks! I cherry-picked the basic, x86 and mips patches to kvm.git's master
> >> branch (I did not use your branch in order to leave arm64 and riscv to the
> >> respective maintainers).
> >
> > Since everything's dependent upon that core patch, IIUC that's going to make it
> > a pain for them to queue things.
> >
> > How are you expecting the arm64 and riscv maintainers to queue things? Queue
> > their own copies of that core patch?
>
> The kvm.git master branch has a stable commit id, so the KVM/ARM and
> KVM/RISCV maintainers can just base their pull request to me on
> it. Alternatively, if they prefer it that way, I can get it quickly to
> Linus.
In which case, please add the arm64 patch to the mix. I'm not rebasing
my current queue.
M.
--
Without deviation from the norm, progress is not possible.
prev parent reply other threads:[~2022-02-01 17:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 13:29 [PATCH v3 0/5] kvm: fix latent guest entry/exit bugs Mark Rutland
2022-02-01 13:29 ` [PATCH v3 1/5] kvm: add guest_state_{enter,exit}_irqoff() Mark Rutland
2022-02-01 13:29 ` [PATCH v3 2/5] kvm/arm64: rework guest entry logic Mark Rutland
2022-02-01 13:29 ` [PATCH v3 3/5] kvm/x86: " Mark Rutland
2022-02-01 13:29 ` [PATCH v3 4/5] kvm/riscv: " Mark Rutland
2022-02-01 13:29 ` [PATCH v3 5/5] kvm/mips: " Mark Rutland
2022-02-01 14:02 ` [PATCH v3 0/5] kvm: fix latent guest entry/exit bugs Christian Borntraeger
2022-02-01 15:59 ` Paolo Bonzini
2022-02-01 16:22 ` Marc Zyngier
2022-02-01 16:22 ` Mark Rutland
2022-02-01 17:10 ` Paolo Bonzini
2022-02-01 17:48 ` Marc Zyngier [this message]
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=87czk65vhq.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=aleksandar.qemu.devel@gmail.com \
--cc=alexandru.elisei@arm.com \
--cc=anup@brainfault.org \
--cc=aou@eecs.berkeley.edu \
--cc=atishp@atishpatra.org \
--cc=benh@kernel.crashing.org \
--cc=borntraeger@linux.ibm.com \
--cc=bp@alien8.de \
--cc=catalin.marinas@arm.com \
--cc=chenhuacai@kernel.org \
--cc=dave.hansen@linux.intel.com \
--cc=frederic@kernel.org \
--cc=hca@linux.ibm.com \
--cc=james.morse@arm.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mpe@ellerman.id.au \
--cc=nsaenzju@redhat.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=paulmck@kernel.org \
--cc=paulus@samba.org \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=suzuki.poulose@arm.com \
--cc=svens@linux.ibm.com \
--cc=tglx@linutronix.de \
--cc=tsbogend@alpha.franken.de \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.