From: Cole Robinson <crobinso@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>, Gerd Hoffmann <kraxel@redhat.com>,
qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@amazon.com>
Subject: Re: [Qemu-devel] [PULL 7/8] gtk: Fix -serial vc
Date: Sun, 04 May 2014 13:07:54 -0400 [thread overview]
Message-ID: <536673EA.7090402@redhat.com> (raw)
In-Reply-To: <5365FBD4.90108@web.de>
On 05/04/2014 04:35 AM, Jan Kiszka wrote:
> On 2014-04-29 11:46, Gerd Hoffmann wrote:
>> From: Cole Robinson <crobinso@redhat.com>
>>
>> Try kicking off a rhel5 text install over serial, the text menu navigation
>> is all messed up, and some of the kernel boot messages are randomly
>> corrupted.
>>
>> Drop use of a pty and just use vte infrastructure for reading and writing.
>> This fixes the above corruption, and is simpler to boot.
>>
>> (I don't know what was wrong with the original code though. FWIW this is
>> what virt-manager has done for years).
>>
>> Signed-off-by: Cole Robinson <crobinso@redhat.com>
>> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
>> ---
>> ui/gtk.c | 41 +++++++++--------------------------------
>> 1 file changed, 9 insertions(+), 32 deletions(-)
>>
>> diff --git a/ui/gtk.c b/ui/gtk.c
>> index c85aea3..1465a38 100644
>> --- a/ui/gtk.c
>> +++ b/ui/gtk.c
>> @@ -115,7 +115,6 @@ typedef struct VirtualConsole
>> GtkWidget *scrolled_window;
>> CharDriverState *chr;
>> #endif
>> - int fd;
>> } VirtualConsole;
>>
>> typedef struct GtkDisplayState
>> @@ -1162,9 +1161,12 @@ static gboolean gd_focus_out_event(GtkWidget *widget,
>>
>> static int gd_vc_chr_write(CharDriverState *chr, const uint8_t *buf, int len)
>> {
>> +#if defined(CONFIG_VTE)
>> VirtualConsole *vc = chr->opaque;
>>
>> - return vc ? write(vc->fd, buf, len) : len;
>> + vte_terminal_feed(VTE_TERMINAL(vc->terminal), (const char *)buf, len);
>> +#endif
>> + return len;
>> }
>>
>> static int nb_vcs;
>> @@ -1190,19 +1192,12 @@ void early_gtk_display_init(void)
>> }
>>
>> #if defined(CONFIG_VTE)
>> -static gboolean gd_vc_in(GIOChannel *chan, GIOCondition cond, void *opaque)
>> +static gboolean gd_vc_in(VteTerminal *terminal, gchar *text, guint size,
>> + gpointer user_data)
>> {
>> - VirtualConsole *vc = opaque;
>> - uint8_t buffer[1024];
>> - ssize_t len;
>> -
>> - len = read(vc->fd, buffer, sizeof(buffer));
>> - if (len <= 0) {
>> - return FALSE;
>> - }
>> -
>> - qemu_chr_be_write(vc->chr, buffer, len);
>> + VirtualConsole *vc = user_data;
>>
>> + qemu_chr_be_write(vc->chr, (uint8_t *)text, (unsigned int)size);
>> return TRUE;
>> }
>> #endif
>> @@ -1214,13 +1209,8 @@ static GSList *gd_vc_init(GtkDisplayState *s, VirtualConsole *vc, int index, GSL
>> const char *label;
>> char buffer[32];
>> char path[32];
>> -#if VTE_CHECK_VERSION(0, 26, 0)
>> - VtePty *pty;
>> -#endif
>> - GIOChannel *chan;
>> GtkWidget *scrolled_window;
>> GtkAdjustment *vadjustment;
>> - int master_fd, slave_fd;
>>
>> snprintf(buffer, sizeof(buffer), "vc%d", index);
>> snprintf(path, sizeof(path), "<QEMU>/View/VC%d", index);
>> @@ -1239,16 +1229,7 @@ static GSList *gd_vc_init(GtkDisplayState *s, VirtualConsole *vc, int index, GSL
>> gtk_accel_map_add_entry(path, GDK_KEY_2 + index, HOTKEY_MODIFIERS);
>>
>> vc->terminal = vte_terminal_new();
>> -
>> - master_fd = qemu_openpty_raw(&slave_fd, NULL);
>> - g_assert(master_fd != -1);
>> -
>> -#if VTE_CHECK_VERSION(0, 26, 0)
>> - pty = vte_pty_new_foreign(master_fd, NULL);
>> - vte_terminal_set_pty_object(VTE_TERMINAL(vc->terminal), pty);
>> -#else
>> - vte_terminal_set_pty(VTE_TERMINAL(vc->terminal), master_fd);
>> -#endif
>> + g_signal_connect(vc->terminal, "commit", G_CALLBACK(gd_vc_in), vc);
>>
>> vte_terminal_set_scrollback_lines(VTE_TERMINAL(vc->terminal), -1);
>>
>> @@ -1263,7 +1244,6 @@ static GSList *gd_vc_init(GtkDisplayState *s, VirtualConsole *vc, int index, GSL
>>
>> vte_terminal_set_size(VTE_TERMINAL(vc->terminal), 80, 25);
>>
>> - vc->fd = slave_fd;
>> vc->chr->opaque = vc;
>> vc->scrolled_window = scrolled_window;
>>
>> @@ -1281,9 +1261,6 @@ static GSList *gd_vc_init(GtkDisplayState *s, VirtualConsole *vc, int index, GSL
>> vc->chr->init(vc->chr);
>> }
>>
>> - chan = g_io_channel_unix_new(vc->fd);
>> - g_io_add_watch(chan, G_IO_IN, gd_vc_in, vc);
>> -
>> #endif /* CONFIG_VTE */
>> return group;
>> }
>>
>
> This commit somehow messes up the monitor vc: Fire up qemu-system-x86_64
> and switch to console 2 (monitor). You'll find it formatted as if the
> console was only ~10 chars wide during printout of the monitor
> greetings. When typing, everything is fine again. Maybe an ordering
> issue that was only revealed by this commit, dunno yet.
>
Check out gerd's ui-gtk-next branch, there's a few extra patches related to
vte sizing that might fix it.
- Cole
next prev parent reply other threads:[~2014-05-04 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1398764774-22595-1-git-send-email-kraxel@redhat.com>
2014-05-01 14:26 ` [Qemu-devel] [PULL 0/8] gtk patch queue Peter Maydell
[not found] ` <1398764774-22595-8-git-send-email-kraxel@redhat.com>
2014-05-04 8:35 ` [Qemu-devel] [PULL 7/8] gtk: Fix -serial vc Jan Kiszka
2014-05-04 17:07 ` Cole Robinson [this message]
2014-05-04 18:25 ` Jan Kiszka
2014-05-04 18:32 ` Jan Kiszka
2014-05-05 11:58 ` Gerd Hoffmann
2014-05-05 11:55 ` Gerd Hoffmann
2014-05-05 14:46 ` Gerd Hoffmann
2014-05-06 11:14 ` Jan Kiszka
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=536673EA.7090402@redhat.com \
--to=crobinso@redhat.com \
--cc=aliguori@amazon.com \
--cc=jan.kiszka@web.de \
--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).