From: Marc Zyngier <maz@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Mostafa Saleh <smostafa@google.com>,
oliver.upton@linux.dev, linux-arm-kernel@lists.infradead.org,
kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org,
tabba@google.com, qperret@google.com, will@kernel.org,
catalin.marinas@arm.com, yuzenghui@huawei.com,
suzuki.poulose@arm.com, james.morse@arm.com, bgardon@google.com,
gshan@redhat.com
Subject: Re: [PATCH v3] KVM: arm64: Use BTI for nvhe
Date: Wed, 12 Jul 2023 11:44:08 +0100 [thread overview]
Message-ID: <864jm9wgsn.wl-maz@kernel.org> (raw)
In-Reply-To: <55bffc21-5f19-765f-9dbc-1b565c880426@leemhuis.info>
On Wed, 12 Jul 2023 11:34:51 +0100,
"Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info> wrote:
>
> [CCing the regression list, as it should be in the loop for regressions:
> https://docs.kernel.org/admin-guide/reporting-regressions.html]
>
> [TLDR: I'm adding this report to the list of tracked Linux kernel
> regressions; the text you find below is based on a few templates
> paragraphs you might have encountered already in similar form.
> See link in footer if these mails annoy you.]
>
> On 04.07.23 15:41, Sudeep Holla wrote:
> > On Tue, May 30, 2023 at 03:08:45PM +0000, Mostafa Saleh wrote:
> >> CONFIG_ARM64_BTI_KERNEL compiles the kernel to support ARMv8.5-BTI.
> >> However, the nvhe code doesn't make use of it as it doesn't map any
> >> pages with Guarded Page(GP) bit.
> > [...]
> > I was chasing a bug in linux-next yesterday with protected nVHE(pKVM) and
> > cpuidle enabled. The system fails to boot. I just bisected the issue to this
> > patch and also saw this patch landed in the linus tree yesterday/today.
> > Not sure if this is something to do with the fact that pKVM skips to
> > __kvm_handle_stub_hvc in __host_hvc.
> >
> > Let me know if you want be to try something.
>
> Thanks for the report. Seems the fix is slow to progress.
It's not. See [1].
M.
[1] https://lore.kernel.org/r/20230706152240.685684-1-smostafa@google.com
--
Without deviation from the norm, progress is not possible.
_______________________________________________
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:[~2023-07-12 10:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-30 15:08 [PATCH v3] KVM: arm64: Use BTI for nvhe Mostafa Saleh
2023-05-30 18:01 ` Oliver Upton
2023-07-04 13:41 ` Sudeep Holla
2023-07-04 14:18 ` Mostafa Saleh
2023-07-04 14:33 ` Sudeep Holla
2023-07-04 16:27 ` Mostafa Saleh
2023-07-04 19:25 ` Sudeep Holla
2023-07-05 15:56 ` Mostafa Saleh
2023-07-06 12:49 ` Mostafa Saleh
2023-07-06 14:27 ` Marc Zyngier
2023-07-06 15:23 ` Mostafa Saleh
2023-07-12 10:34 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-12 10:44 ` Marc Zyngier [this message]
2023-07-12 10:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-07-12 11:01 ` Marc Zyngier
2023-07-12 11:16 ` Linux regression tracking (Thorsten Leemhuis)
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=864jm9wgsn.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=bgardon@google.com \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=james.morse@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=qperret@google.com \
--cc=regressions@lists.linux.dev \
--cc=smostafa@google.com \
--cc=sudeep.holla@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).