From: Mauricio Faria de Oliveira <mfo@igalia.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Thomas Gleixner <tglx@kernel.org>, Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Juergen Gross <jgross@suse.com>,
Alexey Dobriyan <adobriyan@gmail.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
kernel-dev@igalia.com, linux-kernel@vger.kernel.org,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v6 0/4] x86/pvh: fix unbootable VMs again (PVH + KASAN)
Date: Tue, 21 Jul 2026 12:58:45 -0300 [thread overview]
Message-ID: <83f4af183354a1cfa67a5ebad092275c@igalia.com> (raw)
In-Reply-To: <20260718150230.GAaluVhlozNI__9IsA@fat_crate.local>
On 2026-07-18 12:02, Borislav Petkov wrote:
> On Wed, Jul 01, 2026 at 08:13:49PM -0300, Mauricio Faria de Oliveira wrote:
>> The issue of unbootable VMs with CONFIG_PVH due to CONFIG_KASAN is back.
>
> They look like preexisting issues but we probably should take care of them
> before we go forward:
>
> https://sashiko.dev/#/patchset/20260701-pvh-kasan-inline-v6-0-ba99045dfa9f%40igalia.com
>
> Thx.
Thanks for mentioning. Please see v7:
https://lore.kernel.org/all/20260721-pvh-kasan-inline-v7-0-38979a50cef0@igalia.com/
--
Mauricio
prev parent reply other threads:[~2026-07-21 15:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 23:13 Mauricio Faria de Oliveira
2026-07-01 23:13 ` [PATCH v6 1/4] x86/asm, x86/boot: expose inline memcmp Mauricio Faria de Oliveira
2026-07-01 23:13 ` [PATCH v6 2/4] x86/asm: group inline string functions Mauricio Faria de Oliveira
2026-07-01 23:13 ` [PATCH v6 3/4] x86/cpuid: fix unbootable VMs by really inlining memcmp() in hypervisor_cpuid_base() Mauricio Faria de Oliveira
2026-07-01 23:13 ` [PATCH v6 4/4] x86/pvh: fix unbootable VMs by really inlining memset() in xen_prepare_pvh() Mauricio Faria de Oliveira
2026-07-18 15:02 ` [PATCH v6 0/4] x86/pvh: fix unbootable VMs again (PVH + KASAN) Borislav Petkov
2026-07-21 15:58 ` Mauricio Faria de Oliveira [this message]
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=83f4af183354a1cfa67a5ebad092275c@igalia.com \
--to=mfo@igalia.com \
--cc=adobriyan@gmail.com \
--cc=boris.ostrovsky@oracle.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@kernel.org \
--cc=x86@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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
all inboxes | Powered by JetHome®