From: Marc Zyngier <maz@kernel.org>
To: Jan Kotas <jank@cadence.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Subject: Re: KVM NV + SVE host OS warning
Date: Thu, 25 Sep 2025 16:35:13 +0100 [thread overview]
Message-ID: <864isq1r66.wl-maz@kernel.org> (raw)
In-Reply-To: <F9556C9F-2671-4EF6-A725-D080C3793A34@global.cadence.com>
On Thu, 25 Sep 2025 16:10:22 +0100,
Jan Kotas <jank@cadence.com> wrote:
>
> Hi Marc,
>
> Thank you for a quick response.
>
> > On 25 Sep 2025, at 16:38, Marc Zyngier <maz@kernel.org> wrote:
> >
> > EXTERNAL MAIL
> >
> >
> > [+Oliver for the SVE stuff]
> >
> > Hi Jan,
[...]
> >
> > I would also recommend to update to 6.17 -- 6.16 was the first release
> > with NV, and while it may work, it will also have a lot of ugly bugs.
>
> I will try, but as I don’t own this machine, changing kernels might
> be… challenging.
Well, you're already passing something on the command-line that is
documented as "experimental and should be used with extreme caution".
Changing the kernel is a walk in the park compared to that ;-).
> If there’s anything else I can provide to help track it down,
> please let me know.
Testing the provided patch would be good -- I would if I could.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-09-25 15:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <799DD5E5-8BC2-47B3-A919-33429D3FB2F1@global.cadence.com>
2025-09-25 14:38 ` KVM NV + SVE host OS warning Marc Zyngier
2025-09-25 15:10 ` Jan Kotas
2025-09-25 15:35 ` Marc Zyngier [this message]
2025-09-25 22:46 ` Oliver Upton
2025-10-07 11:12 ` Jan Kotas
2025-10-07 23:26 ` Oliver Upton
2025-10-08 6:32 ` Jan Kotas
2025-10-08 7:29 ` Jan Kotas
2025-10-08 9:28 ` Marc Zyngier
2025-10-08 9:45 ` Jan Kotas
2025-10-08 11:58 ` Marc Zyngier
2025-10-08 13:43 ` Jan Kotas
2025-10-08 15:22 ` Marc Zyngier
2025-10-09 10:59 ` Jan Kotas
2025-10-09 12:22 ` Marc Zyngier
2025-10-09 14:41 ` Jan Kotas
2025-10-09 15:01 ` Marc Zyngier
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=864isq1r66.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jank@cadence.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@linux.dev \
/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