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, kernel test robot <lkp@intel.com>
Subject: Re: [PATCH v4 0/4] x86/pvh: fix unbootable VMs again (PVH + KASAN)
Date: Sat, 30 May 2026 20:02:40 -0300 [thread overview]
Message-ID: <28155e57d75407a645d57e4a6f99859c@igalia.com> (raw)
In-Reply-To: <7f1af7169b4f8c90abae28cebd3e377f@igalia.com>
On 2026-05-30 20:01, Mauricio Faria de Oliveira wrote:
> On 2026-05-30 19:04, Borislav Petkov wrote:
>> On Sat, May 30, 2026 at 03:25:25PM -0300, Mauricio Faria de Oliveira wrote:
>>> In this instance, the use case is to speed up the dev-test cycle when
>>> debugging on VMs: PVH allows booting directly from vmlinux, avoiding the
>>> need to build/compress and decompress bzImage, while KASAN helps detect
>>> issues early.
>>
>> Makes sense in itself. And you can't do your use case with KVM? It has to be
>> Xen?
>
> It uses KVM, actually.
>
> IIUIC, the PVH entry point was originally developed for Xen, but later
> QEMU support was added for KVM as well.
> (found this blog post [1] with a nice summary and links about it.)
[1]
https://stefano-garzarella.github.io/posts/2019-08-23-qemu-linux-kernel-pvh/
>>> Briefly, this is a side effect of reusing code from 'boot/string.c'
>>> through <asm/string.h>, which introduces additional complications;
>>> please see patch 1 for details.
>>>
>>> These complications could be avoided by not reusing that code and
>>> instead adding slightly duplicated code [1] directly to <asm/string.h>,
>>> if that is preferred.
>>
>> I'll take a look.
>
> Ok, thanks!
>
>>
>> Thx.
--
Mauricio
next prev parent reply other threads:[~2026-05-30 23:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 14:52 Mauricio Faria de Oliveira
2026-05-26 14:52 ` [PATCH v4 1/4] x86/asm: move inline string functions to <asm/string_inline.h> Mauricio Faria de Oliveira
2026-05-30 23:48 ` Borislav Petkov
2026-05-30 23:57 ` Mauricio Faria de Oliveira
2026-05-26 14:52 ` [PATCH v4 2/4] x86/asm, x86/boot: expose inline memcmp Mauricio Faria de Oliveira
2026-05-26 14:52 ` [PATCH v4 3/4] x86/cpuid: fix unbootable VMs by really inlining memcmp() in hypervisor_cpuid_base() Mauricio Faria de Oliveira
2026-05-26 14:52 ` [PATCH v4 4/4] x86/pvh: fix unbootable VMs by really inlining memset() in xen_prepare_pvh() Mauricio Faria de Oliveira
2026-05-27 20:47 ` [PATCH v4 0/4] x86/pvh: fix unbootable VMs again (PVH + KASAN) Borislav Petkov
2026-05-30 18:25 ` Mauricio Faria de Oliveira
2026-05-30 22:04 ` Borislav Petkov
2026-05-30 23:01 ` Mauricio Faria de Oliveira
2026-05-30 23:02 ` Mauricio Faria de Oliveira [this message]
2026-06-01 18:04 ` Mauricio Faria de Oliveira
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=28155e57d75407a645d57e4a6f99859c@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=lkp@intel.com \
--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
Powered by JetHome