qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
To: Hou Qiming <hqm03ster@gmail.com>, qemu-devel@nongnu.org
Cc: Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] ramfb enhancement
Date: Thu, 9 May 2019 13:50:39 +0300	[thread overview]
Message-ID: <eddfe7d6-e362-740e-4775-6d1a093935e6@gmail.com> (raw)
In-Reply-To: <CABSdmrn073Y6UTbbgs00y5-DCdF1ROK9zAg5JURD4SoUZAk2Mw@mail.gmail.com>



On 5/9/19 10:58 AM, Hou Qiming wrote:
>

The subject for this patch may be:

     [PATCH V2 2/3] hw/display/ramfb: don't allow resolution change 
until vm reset

> Only allow one resolution change per guest boot, which prevents a
> crash when the guest writes garbage to the configuration space (e.g.
> when rebooting).
>

It is actually a cool feature, changing the resolution following a 
display window
resize, but sadly is not stable enough. Let's hope it will be fixed someday.

> Signed-off-by: HOU Qiming <hqm03ster@gmail.com 
> <mailto:hqm03ster@gmail.com>>
> ---
>  hw/display/ramfb.c | 26 ++++++++++++++++++++++----
>  1 file changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/hw/display/ramfb.c b/hw/display/ramfb.c
> index c27fcc7..fa6296b 100644
> --- a/hw/display/ramfb.c
> +++ b/hw/display/ramfb.c
> @@ -31,6 +31,7 @@ struct RAMFBState {
>      uint32_t width, height;
>      hwaddr addr, length;
>      struct RAMFBCfg cfg;
> +    bool locked;
>  };
>
>  static void qemu_unmap_displaysurface_guestmem(pixman_image_t *image,
> @@ -73,11 +74,11 @@ static DisplaySurface 
> *qemu_create_displaysurface_guestmem(
>  static void ramfb_fw_cfg_write(void *dev, off_t offset, size_t len)
>  {
>      RAMFBState *s = dev;
> -    uint32_t fourcc, format;
> +    uint32_t fourcc, format, width, height;
>      hwaddr stride, addr, length;
>
> -    s->width  = be32_to_cpu(s->cfg.width);
> -    s->height = be32_to_cpu(s->cfg.height);
> +    width     = be32_to_cpu(s->cfg.width);
> +    height    = be32_to_cpu(s->cfg.height);
>      stride    = be32_to_cpu(s->cfg.stride);
>      fourcc    = be32_to_cpu(s->cfg.fourcc);
>      addr      = be64_to_cpu(s->cfg.addr);
> @@ -85,9 +86,16 @@ static void ramfb_fw_cfg_write(void *dev, off_t 
> offset, size_t len)
>      format    = qemu_drm_format_to_pixman(fourcc);
>
>      fprintf(stderr, "%s: %dx%d @ 0x%" PRIx64 "\n", __func__,
> -            s->width, s->height, addr);
> +            width, height, addr);
> +    if (s->locked) {
> +        fprintf(stderr, "%s: resolution locked, change rejected\n", 
> __func__);
> +        return;
> +    }
> +    s->locked = true;
>      s->addr = addr;
>      s->length = length;
> +    s->width = width;
> +    s->height = height;
>      s->ds = qemu_create_displaysurface_guestmem(s->width, s->height,
>                                                  format, stride, s->addr);
>  }
> @@ -107,6 +115,13 @@ void ramfb_display_update(QemuConsole *con, 
> RAMFBState *s)
>      dpy_gfx_update_full(con);
>  }
>
> +static void ramfb_reset(void *opaque)
> +{
> +    RAMFBState *s = (RAMFBState *)opaque;
> +    s->locked = false;
> +    memset(&s->cfg, 0, sizeof(s->cfg));
> +}
> +
>  RAMFBState *ramfb_setup(Error **errp)
>  {
>      FWCfgState *fw_cfg = fw_cfg_find();
> @@ -119,9 +134,12 @@ RAMFBState *ramfb_setup(Error **errp)
>
>      s = g_new0(RAMFBState, 1);
>
> +    s->locked = false;
> +
>      rom_add_vga("vgabios-ramfb.bin");
>      fw_cfg_add_file_callback(fw_cfg, "etc/ramfb",
>                               NULL, ramfb_fw_cfg_write, s,
>                               &s->cfg, sizeof(s->cfg), false);
> +    qemu_register_reset(ramfb_reset, s);
>      return s;
>  }
> -- 
> 2.17.1
>
>



  reply	other threads:[~2019-05-09 10:51 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-06  7:50 [Qemu-devel] Patch: Precautionary glBindTexture in surface_gl_update_texture Hou Qiming
2019-05-06  8:22 ` Marcel Apfelbaum
2019-05-09  0:15 ` [Qemu-devel] [PATCH] Multiple ramfb enhancements Hou Qiming
2019-05-09  6:48   ` Gerd Hoffmann
2019-05-09  7:43     ` Hou Qiming
2019-05-09  7:57       ` [Qemu-devel] [PATCH 1/3] ramfb enhancement Hou Qiming
2019-05-09 10:44         ` Marcel Apfelbaum
2019-05-10  4:59         ` Gerd Hoffmann
2019-05-09  7:58       ` [Qemu-devel] [PATCH 2/3] " Hou Qiming
2019-05-09 10:50         ` Marcel Apfelbaum [this message]
2019-05-10  5:01         ` Gerd Hoffmann
2019-05-10  6:41           ` Hou Qiming
2019-05-10  8:54             ` Gerd Hoffmann
2019-05-09  7:58       ` [Qemu-devel] [PATCH 3/3] " Hou Qiming
2019-05-09 10:58         ` Marcel Apfelbaum
2019-05-10  2:20           ` Hou Qiming
2019-05-10  6:20             ` Marcel Apfelbaum
2019-05-10  8:59               ` Gerd Hoffmann
2019-05-10  9:20                 ` Marcel Apfelbaum
2019-05-10 10:39                   ` Gerd Hoffmann
2019-05-10 10:52                     ` Marcel Apfelbaum
2019-05-10 16:28                       ` [Qemu-devel] [PATCH v2 1/3] hw/display/ramfb: fix guest memory un-mapping Hou Qiming
2019-05-10 16:29                         ` [Qemu-devel] [PATCH v2 2/3] hw/display/ramfb: lock guest resolution after it's set Hou Qiming
2019-05-10 16:29                         ` [Qemu-devel] [PATCH v2 3/3] hw/display/ramfb: initialize fw-config space with xres / yres Hou Qiming
2019-05-10  5:07         ` [Qemu-devel] [PATCH 3/3] ramfb enhancement Gerd Hoffmann

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=eddfe7d6-e362-740e-4775-6d1a093935e6@gmail.com \
    --to=marcel.apfelbaum@gmail.com \
    --cc=hqm03ster@gmail.com \
    --cc=kraxel@redhat.com \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).