[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH 4/5] xen: fix handling framebuffer located above 4GB



>>> On 07.05.19 at 17:38, <marmarek@xxxxxxxxxxxxxxxxxxxxxx> wrote:
> What do you think about adding something that could be backported?
> Xen is quite insistent on initializing framebuffer, even with
> console=com1 or console=none. Which means, there is no workaround for
> this problem.

When the system is in a simple text mode the /basevideo option of
xen.efi ought to help, but if it's in an LFB-based mode already (which
is the case on the systems I have) then indeed I can't see any
workaround.

> Maybe, as a first step, a change that abort framebuffer initialization
> if lfb_base == 0 (I assume this is never valid value here, right?)?

Yes, that would be an option. But it would help only in your specific
case, not if the truncation results in a non-zero value. I guess we'd
better avoid filling the structure if we'd truncate the value.

But what's wrong with backporting your change as is?

> If not, then at least abort boot when text console is still there
> (blexit before efi_exit_boot). Any preference?

What's wrong with the text console still active? Or maybe I'm
misunderstanding this point you make...

Jan



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxx
https://lists.xenproject.org/mailman/listinfo/xen-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.