From: Marc Zyngier <maz@kernel.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: Wujie Duan <wjduan@linx-info.com>,
james.morse@arm.com, suzuki.poulose@arm.com,
yuzenghui@huawei.com, kvmarm@lists.linux.dev
Subject: Re: [PATCH] KVM: arm64: Change back kvm fault condition to translation
Date: Mon, 18 Mar 2024 17:43:41 +0000 [thread overview]
Message-ID: <86sf0nzb8y.wl-maz@kernel.org> (raw)
In-Reply-To: <Zfh4TOQxzTUxGePf@linux.dev>
On Mon, 18 Mar 2024 17:22:20 +0000,
Oliver Upton <oliver.upton@linux.dev> wrote:
>
> Hey,
>
> On Mon, Mar 18, 2024 at 10:17:47AM +0000, Marc Zyngier wrote:
>
> > I think 7 tries are enough ;-). Here's what I was expecting:
>
> Hopefully I'm looking at the right thread!
You are!
>
> > - a subject indicating the nature of the issue as a one-liner
> > - a commit message describing the exact situation
> > - a Fixes: tag indicating the commit being fixed
> > - a Cc: stable tag to indicate this needs backporting
> > - Ard's Ack, as he's been kind enough to look into it
> >
> > See below for the full patch and my own RB tag. In the future, please
> > try to follow these guidelines.
> >
> > Oliver, can you please pick this ASAP?
>
> Yup, I'll queue it up but I only plan on sending the first set of fixes
> after -rc1 as I'll be AFK for a few days this week. I'll get a respin of
> the vPMU + nVHE stuff out too.
Sounds good. This is only a corner case anyway, which is why it didn't
show up in my testing, and -rc1 is the right spot for it.
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-03-18 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 10:02 [PATCH] KVM: arm64: Change back kvm fault condition to translation Wujie Duan
2024-03-18 10:17 ` Marc Zyngier
2024-03-18 10:31 ` Zenghui Yu
2024-03-18 17:22 ` Oliver Upton
2024-03-18 17:43 ` Marc Zyngier [this message]
2024-03-26 13:48 ` (subset) " Oliver Upton
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=86sf0nzb8y.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=wjduan@linx-info.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox