From: Jan Beulich <jbeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>, Wei Liu <wl@xen.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH] efifb: ignore frame buffer with physical address 0
Date: Fri, 18 Nov 2022 14:56:33 +0100 [thread overview]
Message-ID: <ab764680-c420-df54-8a63-fd9dbd284dbb@suse.com> (raw)
In-Reply-To: <Y3eMPMvtIgfkaMJV@Air-de-Roger>
On 18.11.2022 14:44, Roger Pau Monné wrote:
> On Fri, Nov 18, 2022 at 02:04:40PM +0100, Jan Beulich wrote:
>> On 18.11.2022 13:39, Roger Pau Monne wrote:
>>> --- a/xen/arch/x86/efi/efi-boot.h
>>> +++ b/xen/arch/x86/efi/efi-boot.h
>>> @@ -552,7 +552,7 @@ static void __init efi_arch_video_init(EFI_GRAPHICS_OUTPUT_PROTOCOL *gop,
>>> bpp = 0;
>>> break;
>>> }
>>> - if ( bpp > 0 )
>>> + if ( bpp > 0 && gop->Mode->FrameBufferBase )
>>> {
>>> vga_console_info.video_type = XEN_VGATYPE_EFI_LFB;
>>> vga_console_info.u.vesa_lfb.gbl_caps = 2; /* possibly non-VGA */
>>
>> A few lines up from here, just out of patch context, there is a
>> PrintErr() which imo is bogus/misleading when also encountering a
>> zero fb base. I'd like to suggest that you put the new check early
>> in the function (perhaps extended by a zero check of other
>> applicable fields, as per above), returning right away alongside
>> another new PrintErr().
>
> Would you be fine with the new message being "Invalid Frame Buffer
> configuration found"?
Yeah, that'll probably do.
Jan
prev parent reply other threads:[~2022-11-18 13:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-18 12:39 [PATCH] efifb: ignore frame buffer with physical address 0 Roger Pau Monne
2022-11-18 13:04 ` Jan Beulich
2022-11-18 13:44 ` Roger Pau Monné
2022-11-18 13:56 ` Jan Beulich [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=ab764680-c420-df54-8a63-fd9dbd284dbb@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=roger.pau@citrix.com \
--cc=wl@xen.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.