From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Jan Beulich <jbeulich@suse.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "Wei Liu" <wl@xen.org>, "Roger Pau Monné" <roger.pau@citrix.com>
Subject: Re: [PATCH 7/7] video/vesa: adjust (not just) command line option handling
Date: Tue, 27 Apr 2021 14:49:12 +0100 [thread overview]
Message-ID: <3e04b606-4e4f-e181-d3be-bcf99a2c8fa2@citrix.com> (raw)
In-Reply-To: <7e3f69d7-23e8-397d-72b6-8c489d80ea45@suse.com>
On 27/04/2021 13:56, Jan Beulich wrote:
The grammar in the subject is very awkward. The (not just) like that is
weird.
If it were me, I'd phrase this as "minor adjustments to command line
handling".
> Document both options. Add section annotations to both variables holding
> the parsed values as well as a few adjacent ones. Adjust the types of
> font_height and vga_compat.
>
> Signed-off-by: Jan Beulich <jbeulich@suse.com>
In principle, Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>, with
one note below.
However, is there really any value in these options? I can't see a case
where their use will result in a less broken system.
>
> --- a/docs/misc/xen-command-line.pandoc
> +++ b/docs/misc/xen-command-line.pandoc
> @@ -2369,9 +2369,21 @@ cache-warming. 1ms (1000) has been measu
> ### vesa-map
> > `= <integer>`
>
> +> Default: `0`
> +
> +Specify, in MiB, the portion of video RAM to actually remap. This will be
> +honored only when large enough to cover the space needed for the chosen video
> +mode, and only when less than a non-zero value possibly specified through
> +'vesa-ram'.
"and only when less than a non-zero value possibly specified" is
confusing to follow.
What I think you mean is that vesa-map will be honoured when it is >=
chosen video mode, and <= vesa-ram?
~Andrew
> +
> ### vesa-ram
> > `= <integer>`
>
> +> Default: `0`
> +
> +This allows to override the amount of video RAM, in MiB, determined to be
> +present.
> +
> ### vga
> > `= ( ask | current | text-80x<rows> | gfx-<width>x<height>x<depth> | mode-<mode> )[,keep]`
>
> --- a/xen/drivers/video/vesa.c
> +++ b/xen/drivers/video/vesa.c
> @@ -19,17 +19,17 @@
>
> static void lfb_flush(void);
>
> -static unsigned char *lfb;
> -static const struct font_desc *font;
> -static bool_t vga_compat;
> +static unsigned char *__read_mostly lfb;
> +static const struct font_desc *__initdata font;
> +static bool __initdata vga_compat;
>
> -static unsigned int vram_total;
> +static unsigned int __initdata vram_total;
> integer_param("vesa-ram", vram_total);
>
> -static unsigned int vram_remap;
> +static unsigned int __initdata vram_remap;
> integer_param("vesa-map", vram_remap);
>
> -static int font_height;
> +static unsigned int __initdata font_height;
> static int __init parse_font_height(const char *s)
> {
> if ( simple_strtoul(s, &s, 10) == 8 && (*s++ == 'x') )
>
next prev parent reply other threads:[~2021-04-27 13:50 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 12:51 [PATCH 0/7] x86: memcpy() / memset() (non-)ERMS flavors plus fallout Jan Beulich
2021-04-27 12:53 ` [PATCH 1/7] x86: correct comment about alternatives ordering Jan Beulich
2021-04-27 13:19 ` Andrew Cooper
2021-04-27 12:54 ` [PATCH 2/7] x86: introduce ioremap_wc() Jan Beulich
2021-04-27 17:13 ` Andrew Cooper
2021-04-28 9:41 ` Jan Beulich
2021-04-27 12:54 ` [PATCH 3/7] x86: re-work memset() Jan Beulich
2021-04-27 12:54 ` [PATCH 4/7] x86: re-work memcpy() Jan Beulich
2021-04-27 12:55 ` [PATCH 5/7] video/vesa: unmap frame buffer when relinquishing console Jan Beulich
2021-04-27 12:56 ` [PATCH 6/7] video/vesa: drop "vesa-mtrr" command line option Jan Beulich
2021-04-27 13:20 ` Andrew Cooper
2021-04-27 12:56 ` [PATCH 7/7] video/vesa: adjust (not just) command line option handling Jan Beulich
2021-04-27 13:49 ` Andrew Cooper [this message]
2021-04-27 14:04 ` Jan Beulich
2021-05-27 11:47 ` Jan Beulich
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=3e04b606-4e4f-e181-d3be-bcf99a2c8fa2@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.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.