From: Christoffer Dall <cdall@linaro.org>
To: Marc Zyngier <marc.zyngier@arm.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
Christoffer Dall <christoffer.dall@linaro.org>,
kvm@vger.kernel.org, kvmarm@lists.cs.columbia.edu,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/5] KVM/ARM: Fixes for 4.12-rc1
Date: Tue, 2 May 2017 19:15:55 +0200 [thread overview]
Message-ID: <20170502171555.GA12916@cbox> (raw)
In-Reply-To: <c9f36b35-6a46-8ed8-0bb0-9c099f28d834@arm.com>
On Tue, May 02, 2017 at 04:00:49PM +0100, Marc Zyngier wrote:
> On 02/05/17 15:44, Paolo Bonzini wrote:
> >
> >
> > On 02/05/2017 15:30, Marc Zyngier wrote:
> >> Here's a handful of random fixes I've queued locally that didn't have
> >> a chance to make it in 4.11.
> >>
> >> The first two patches avoid stack-protector messing with the HYP code,
> >> as this ends up being a complete disaster.
> >>
> >> The following two patches fix a bug introduced in the new vgic, where
> >> we may queue HW interrupts with the Pending+Active state, which is
> >> illegal.
> >>
> >> The final patch fixes a misinterpretation of the spec, where we
> >> compute the number of APxRn register based on the number of priorities
> >> instead of using the number of preemption levels.
> >>
> >> I've tagged the first 4 patches for stable, given that we're doing
> >> something potentially harmful. The last patch is more of a theoretical
> >> issue at this stage, so probably need for a backport.
> >
> > Would you like me to apply them, or are you looking for reviews and
> > going to send them in a pull request?
> >
> > I can wait a couple days before sending my own pull request to Linus.
>
> Christoffer is in charge of the tree at the moment, so I'll leave it up
> to him to decide. But my guess is that he will send a PR some time
> later, with the rest of the fixes that have been posted lately.
>
Yes, I have some other fixes that I'll send together with these as soon
as -rc1 hits. And I plan on reviewing these.
Thanks,
-Christoffer
WARNING: multiple messages have this Message-ID (diff)
From: cdall@linaro.org (Christoffer Dall)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] KVM/ARM: Fixes for 4.12-rc1
Date: Tue, 2 May 2017 19:15:55 +0200 [thread overview]
Message-ID: <20170502171555.GA12916@cbox> (raw)
In-Reply-To: <c9f36b35-6a46-8ed8-0bb0-9c099f28d834@arm.com>
On Tue, May 02, 2017 at 04:00:49PM +0100, Marc Zyngier wrote:
> On 02/05/17 15:44, Paolo Bonzini wrote:
> >
> >
> > On 02/05/2017 15:30, Marc Zyngier wrote:
> >> Here's a handful of random fixes I've queued locally that didn't have
> >> a chance to make it in 4.11.
> >>
> >> The first two patches avoid stack-protector messing with the HYP code,
> >> as this ends up being a complete disaster.
> >>
> >> The following two patches fix a bug introduced in the new vgic, where
> >> we may queue HW interrupts with the Pending+Active state, which is
> >> illegal.
> >>
> >> The final patch fixes a misinterpretation of the spec, where we
> >> compute the number of APxRn register based on the number of priorities
> >> instead of using the number of preemption levels.
> >>
> >> I've tagged the first 4 patches for stable, given that we're doing
> >> something potentially harmful. The last patch is more of a theoretical
> >> issue at this stage, so probably need for a backport.
> >
> > Would you like me to apply them, or are you looking for reviews and
> > going to send them in a pull request?
> >
> > I can wait a couple days before sending my own pull request to Linus.
>
> Christoffer is in charge of the tree at the moment, so I'll leave it up
> to him to decide. But my guess is that he will send a PR some time
> later, with the rest of the fixes that have been posted lately.
>
Yes, I have some other fixes that I'll send together with these as soon
as -rc1 hits. And I plan on reviewing these.
Thanks,
-Christoffer
next prev parent reply other threads:[~2017-05-02 17:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-02 13:30 [PATCH 0/5] KVM/ARM: Fixes for 4.12-rc1 Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-02 13:30 ` [PATCH 1/5] arm64: KVM: Do not use stack-protector to compile EL2 code Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-02 14:40 ` Catalin Marinas
2017-05-02 14:40 ` Catalin Marinas
2017-05-02 14:48 ` Ard Biesheuvel
2017-05-02 14:48 ` Ard Biesheuvel
2017-05-02 14:50 ` Marc Zyngier
2017-05-02 14:50 ` Marc Zyngier
2017-05-11 16:02 ` Marc Zyngier
2017-05-11 16:02 ` Marc Zyngier
2017-05-11 16:11 ` Ard Biesheuvel
2017-05-11 16:11 ` Ard Biesheuvel
2017-05-11 16:36 ` Ard Biesheuvel
2017-05-11 16:36 ` Ard Biesheuvel
2017-05-11 16:42 ` Marc Zyngier
2017-05-11 16:42 ` Marc Zyngier
2017-05-11 17:01 ` Ard Biesheuvel
2017-05-11 17:01 ` Ard Biesheuvel
2017-05-12 15:07 ` Marc Zyngier
2017-05-12 15:07 ` Marc Zyngier
2017-05-02 13:30 ` [PATCH 2/5] arm: KVM: Do not use stack-protector to compile HYP code Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-02 13:30 ` [PATCH 3/5] KVM: arm/arm64: vgic-v2: Do not use Active+Pending state for a HW interrupt Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-02 20:56 ` Christoffer Dall
2017-05-02 20:56 ` Christoffer Dall
2017-05-02 13:30 ` [PATCH 4/5] KVM: arm/arm64: vgic-v3: " Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-02 20:56 ` Christoffer Dall
2017-05-02 20:56 ` Christoffer Dall
2017-05-02 13:30 ` [PATCH 5/5] KVM: arm/arm64: vgic-v3: Use PREbits to infer the number of ICH_APxRn_EL2 registers Marc Zyngier
2017-05-02 13:30 ` Marc Zyngier
2017-05-15 9:30 ` Christoffer Dall
2017-05-15 9:30 ` Christoffer Dall
2017-05-02 14:44 ` [PATCH 0/5] KVM/ARM: Fixes for 4.12-rc1 Paolo Bonzini
2017-05-02 14:44 ` Paolo Bonzini
2017-05-02 15:00 ` Marc Zyngier
2017-05-02 15:00 ` Marc Zyngier
2017-05-02 17:15 ` Christoffer Dall [this message]
2017-05-02 17:15 ` Christoffer Dall
2017-05-15 9:33 ` Christoffer Dall
2017-05-15 9:33 ` Christoffer Dall
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=20170502171555.GA12916@cbox \
--to=cdall@linaro.org \
--cc=christoffer.dall@linaro.org \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=pbonzini@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 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.