From: Boris Ostrovsky <boris.ostrovsky@oracle.com>
To: Jan Beulich <jbeulich@suse.com>, Juergen Gross <jgross@suse.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xen/x86: obtain upper 32 bits of video frame buffer address for Dom0
Date: Tue, 4 Jan 2022 11:50:21 -0500 [thread overview]
Message-ID: <bfab8ff9-9762-f90d-3f25-b57362f05b0b@oracle.com> (raw)
In-Reply-To: <a3df8bf3-d044-b7bb-3383-cd5239d6d4af@suse.com>
On 1/4/22 3:46 AM, Jan Beulich wrote:
> The hypervisor has been supplying this information for a couple of major
> releases. Make use of it. The need to set a flag in the capabilities
> field also points out that the prior setting of that field from the
> hypervisor interface's gbl_caps one was wrong, so that code gets deleted
> (there's also no equivalent of this in native boot code).
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> --- a/arch/x86/xen/vga.c
> +++ b/arch/x86/xen/vga.c
> @@ -63,13 +63,17 @@ void __init xen_init_vga(const struct do
> }
>
> if (size >= offsetof(struct dom0_vga_console_info,
> - u.vesa_lfb.gbl_caps)
> - + sizeof(info->u.vesa_lfb.gbl_caps))
> - screen_info->capabilities = info->u.vesa_lfb.gbl_caps;
> - if (size >= offsetof(struct dom0_vga_console_info,
> u.vesa_lfb.mode_attrs)
> + sizeof(info->u.vesa_lfb.mode_attrs))
Do we still need this test? All 4.0+ hypervisors will have mode_attrs.
-boris
> screen_info->vesa_attributes = info->u.vesa_lfb.mode_attrs;
> +
> + if (size >= offsetof(struct dom0_vga_console_info,
> + u.vesa_lfb.ext_lfb_base)
> + + sizeof(info->u.vesa_lfb.ext_lfb_base)
> + && info->u.vesa_lfb.ext_lfb_base) {
> + screen_info->ext_lfb_base = info->u.vesa_lfb.ext_lfb_base;
> + screen_info->capabilities |= VIDEO_CAPABILITY_64BIT_BASE;
> + }
> break;
> }
> }
> --- a/include/xen/interface/xen.h
> +++ b/include/xen/interface/xen.h
> @@ -722,6 +722,9 @@ struct dom0_vga_console_info {
> uint32_t gbl_caps;
> /* Mode attributes (offset 0x0, VESA command 0x4f01). */
> uint16_t mode_attrs;
> + uint16_t pad;
> + /* high 32 bits of lfb_base */
> + uint32_t ext_lfb_base;
> } vesa_lfb;
> } u;
> };
>
next prev parent reply other threads:[~2022-01-04 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 8:46 Jan Beulich
2022-01-04 16:50 ` Boris Ostrovsky [this message]
2022-01-04 16:54 ` Jan Beulich
2022-01-04 17:03 ` Boris Ostrovsky
2022-01-05 7:59 ` Jan Beulich
2022-01-05 16:30 ` Boris Ostrovsky
2022-01-07 11:30 ` Juergen Gross
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=bfab8ff9-9762-f90d-3f25-b57362f05b0b@oracle.com \
--to=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.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®