From: "Pedro Falcato" <pedro.falcato@gmail.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Ard Biesheuvel <ardb@kernel.org>,
devel@edk2.groups.io, Laszlo Ersek <lersek@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Jiewen Yao <jiewen.yao@intel.com>,
dun.tan@intel.com
Subject: Re: [edk2-devel] [PATCH 1/1] OvmfPkg/QemuVideoDxe: purge VbeShim
Date: Tue, 13 Feb 2024 15:47:11 +0000 [thread overview]
Message-ID: <CAKbZUD0tErja0Efrxd4wWPSkM2qce4dN_ZW2iLCC2PJsB=xOjA@mail.gmail.com> (raw)
In-Reply-To: <yjdu3dza5rz5a3buscfr5vgl2b2sxobo3zb3mkdgt7w4xh4zam@m7eux5gyd433>
On Tue, Feb 13, 2024 at 3:28 PM Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> Hi,
>
> > > > New theory: This is a NULL pointer dereference corrupting the zero page.
> > >
> > > Tangentially related: Maybe it's time to unmap the NULL page? :)
>
> Suggestion: read mails to the end. Had the same idea + question ;)
Sorry! My bad. Apparently I don't know how to read ;)
>
> > That would break many 3rd party GPU and network drivers.
>
> For virtual machine firmware it might be acceptable to just ignore
> that, or at least default to an unmapped zero page and offer an
> qemu fw-cfg override in case someone needs that when pci-assigning
> nic or gpu to a VM.
IMO this is a really nice suggestion. Could QEMU be modified to inject
the fwcfg option if a VFIO device is present or something? Would that
solve most of the compatibility issues? Are OVMF and QEMU usually
packaged (distro-side) in somewhat of a lockstep?
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#115388): https://edk2.groups.io/g/devel/message/115388
Mute This Topic: https://groups.io/mt/104329097/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-02-13 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-13 8:59 [edk2-devel] [PATCH 1/1] OvmfPkg/QemuVideoDxe: purge VbeShim Gerd Hoffmann
2024-02-13 10:41 ` Ard Biesheuvel
2024-02-13 10:44 ` Laszlo Ersek
2024-02-13 14:02 ` Gerd Hoffmann
2024-02-13 14:55 ` Pedro Falcato
2024-02-13 14:56 ` Ard Biesheuvel
2024-02-13 15:07 ` Pedro Falcato
2024-02-13 15:28 ` Gerd Hoffmann
2024-02-13 15:47 ` Pedro Falcato [this message]
2024-02-13 17:31 ` Laszlo Ersek
2024-02-13 17:28 ` Laszlo Ersek
2024-02-13 18:13 ` Laszlo Ersek
2024-02-13 20:25 ` Laszlo Ersek
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-list 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='CAKbZUD0tErja0Efrxd4wWPSkM2qce4dN_ZW2iLCC2PJsB=xOjA@mail.gmail.com' \
--to=devel@edk2.groups.io \
/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