From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>, pbonzini@redhat.com
Cc: Andrew Jones <drjones@redhat.com>,
Fangrui Song <maskray@google.com>,
Mark Rutland <mark.rutland@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
Zenghui Yu <yuzenghui@huawei.com>,
James Morse <james.morse@arm.com>,
Julien Thierry <julien.thierry.kdev@gmail.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL] KVM/arm fixes for 5.7, take #2
Date: Mon, 4 May 2020 12:30:52 +0100 [thread overview]
Message-ID: <20200504113051.GB1326@willie-the-truck> (raw)
In-Reply-To: <20200501101204.364798-1-maz@kernel.org>
Hi Marc, Paolo,
On Fri, May 01, 2020 at 11:12:00AM +0100, Marc Zyngier wrote:
> This is the second batch of KVM/arm fixes for 5.7. A compilation fix,
> a GICv4.1 fix, plus a couple of sanity checks (SP_EL0 save/restore,
> and the sanitising of AArch32 registers).
>
> Note that the pull request I sent a week ago[1] is still valid, and
> that this new series is built on top of the previous one.
>
> Please pull,
I don't see this queued up in the kvm tree, which appears to have been
sitting dormant for 10 days. Consequently, there are fixes sitting in
limbo and we /still/ don't have a sensible base for arm64/kvm patches
targetting 5.8.
Paolo -- how can I help get this stuff moving again? I'm more than happy
to send this lot up to Linus via arm64 if you're busy atm. Please just
let me know.
Cheers,
Will
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>, pbonzini@redhat.com
Cc: kvm@vger.kernel.org, Fangrui Song <maskray@google.com>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-arm-kernel@lists.infradead.org,
kvmarm@lists.cs.columbia.edu
Subject: Re: [GIT PULL] KVM/arm fixes for 5.7, take #2
Date: Mon, 4 May 2020 12:30:52 +0100 [thread overview]
Message-ID: <20200504113051.GB1326@willie-the-truck> (raw)
In-Reply-To: <20200501101204.364798-1-maz@kernel.org>
Hi Marc, Paolo,
On Fri, May 01, 2020 at 11:12:00AM +0100, Marc Zyngier wrote:
> This is the second batch of KVM/arm fixes for 5.7. A compilation fix,
> a GICv4.1 fix, plus a couple of sanity checks (SP_EL0 save/restore,
> and the sanitising of AArch32 registers).
>
> Note that the pull request I sent a week ago[1] is still valid, and
> that this new series is built on top of the previous one.
>
> Please pull,
I don't see this queued up in the kvm tree, which appears to have been
sitting dormant for 10 days. Consequently, there are fixes sitting in
limbo and we /still/ don't have a sensible base for arm64/kvm patches
targetting 5.8.
Paolo -- how can I help get this stuff moving again? I'm more than happy
to send this lot up to Linus via arm64 if you're busy atm. Please just
let me know.
Cheers,
Will
_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: Marc Zyngier <maz@kernel.org>, pbonzini@redhat.com
Cc: Mark Rutland <mark.rutland@arm.com>,
Andrew Jones <drjones@redhat.com>,
kvm@vger.kernel.org, Fangrui Song <maskray@google.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Nick Desaulniers <ndesaulniers@google.com>,
James Morse <james.morse@arm.com>,
linux-arm-kernel@lists.infradead.org,
Zenghui Yu <yuzenghui@huawei.com>,
kvmarm@lists.cs.columbia.edu,
Julien Thierry <julien.thierry.kdev@gmail.com>
Subject: Re: [GIT PULL] KVM/arm fixes for 5.7, take #2
Date: Mon, 4 May 2020 12:30:52 +0100 [thread overview]
Message-ID: <20200504113051.GB1326@willie-the-truck> (raw)
In-Reply-To: <20200501101204.364798-1-maz@kernel.org>
Hi Marc, Paolo,
On Fri, May 01, 2020 at 11:12:00AM +0100, Marc Zyngier wrote:
> This is the second batch of KVM/arm fixes for 5.7. A compilation fix,
> a GICv4.1 fix, plus a couple of sanity checks (SP_EL0 save/restore,
> and the sanitising of AArch32 registers).
>
> Note that the pull request I sent a week ago[1] is still valid, and
> that this new series is built on top of the previous one.
>
> Please pull,
I don't see this queued up in the kvm tree, which appears to have been
sitting dormant for 10 days. Consequently, there are fixes sitting in
limbo and we /still/ don't have a sensible base for arm64/kvm patches
targetting 5.8.
Paolo -- how can I help get this stuff moving again? I'm more than happy
to send this lot up to Linus via arm64 if you're busy atm. Please just
let me know.
Cheers,
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-05-04 11:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 10:12 [GIT PULL] KVM/arm fixes for 5.7, take #2 Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` [PATCH 1/4] KVM: arm64: Delete duplicated label in invalid_vector Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` [PATCH 2/4] KVM: arm64: Save/restore sp_el0 as part of __guest_enter Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` [PATCH 3/4] KVM: arm64: vgic-v4: Initialize GICv4.1 even in the absence of a virtual ITS Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` [PATCH 4/4] KVM: arm64: Fix 32bit PC wrap-around Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-01 10:12 ` Marc Zyngier
2020-05-06 23:42 ` Sasha Levin
2020-05-04 11:30 ` Will Deacon [this message]
2020-05-04 11:30 ` [GIT PULL] KVM/arm fixes for 5.7, take #2 Will Deacon
2020-05-04 11:30 ` Will Deacon
2020-05-04 16:05 ` Paolo Bonzini
2020-05-04 16:05 ` Paolo Bonzini
2020-05-04 16:05 ` Paolo Bonzini
2020-05-04 16:51 ` Will Deacon
2020-05-04 16:51 ` Will Deacon
2020-05-04 16:51 ` Will Deacon
2020-05-04 17:02 ` Paolo Bonzini
2020-05-04 17:02 ` Paolo Bonzini
2020-05-04 17:02 ` 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 \
--in-reply-to=20200504113051.GB1326@willie-the-truck \
--to=will@kernel.org \
--cc=drjones@redhat.com \
--cc=james.morse@arm.com \
--cc=julien.thierry.kdev@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maskray@google.com \
--cc=maz@kernel.org \
--cc=ndesaulniers@google.com \
--cc=pbonzini@redhat.com \
--cc=suzuki.poulose@arm.com \
--cc=yuzenghui@huawei.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 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.