From: Amit Shah <amit.shah@redhat.com>
To: Kusanagi Kouichi <slash@ac.auone-net.jp>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [PATCH v2 2/2] virtio-console: Notify resize to the guest.
Date: Fri, 30 Apr 2010 16:13:39 +0530 [thread overview]
Message-ID: <20100430104338.GA27314@amit-x200.redhat.com> (raw)
In-Reply-To: <20100430081220.2178A6AC03A@msa102.auone-net.jp>
On (Fri) Apr 30 2010 [17:12:19], Kusanagi Kouichi wrote:
> I tested this patch as follows:
> I put printf()s into involved functions. Then ran qemu on a terminal
> emulator, and resized it.
> The guest kernel gets initial size. However, it doesn't update the size.
> It seems to need to enable multiport for resize.
If the guest kernel supports multiport, you should send the control
event.
If the guest kernel doesn't support multiport, then you should send a
config space update so that the console size is updated for the only
port that exists.
Sorry for not catching this earlier.
Can you test both the possibilities and let me know? This patch will
have to be updated, of course, to support resize over the config space
in the following function:
> +void virtio_serial_resize_console(VirtIOSerialPort *port, int rows, int cols)
> +{
> + port->vser->config.rows = rows;
> + port->vser->config.cols = cols;
> + send_control_event(port, VIRTIO_CONSOLE_RESIZE, 0);
> +}
> +
...
> struct virtio_console_config {
> /*
> - * These two fields are used by VIRTIO_CONSOLE_F_SIZE which
> - * isn't implemented here yet
> + * These two fields are used by VIRTIO_CONSOLE_F_SIZE
This comment could be expanded to explain when we use the config space
for size updates (!multiport) and when we use control messages
(multiport).
Thanks!
Amit
next prev parent reply other threads:[~2010-04-30 10:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-16 11:42 [Qemu-devel] [PATCH 2/2] virtio-console: Notify resize to the guest Kusanagi Kouichi
2010-04-16 13:02 ` Amit Shah
2010-04-29 7:12 ` Kusanagi Kouichi
2010-04-29 10:47 ` Amit Shah
2010-04-29 12:36 ` Kusanagi Kouichi
2010-04-29 12:49 ` Amit Shah
2010-04-30 8:12 ` [Qemu-devel] [PATCH v2 " Kusanagi Kouichi
2010-04-30 10:43 ` Amit Shah [this message]
2010-05-03 4:58 ` [Qemu-devel] [PATCH v3 " Kusanagi Kouichi
2010-05-03 6:37 ` [Qemu-devel] " Amit Shah
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=20100430104338.GA27314@amit-x200.redhat.com \
--to=amit.shah@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=slash@ac.auone-net.jp \
/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).