qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: Peter Wu <lekensteyn@gmail.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] chardev: add baud parameter for serial host device
Date: Sat, 15 Jun 2013 16:38:51 +0100	[thread overview]
Message-ID: <51BC8A8B.3030607@redhat.com> (raw)
In-Reply-To: <2801661.HtiIQHWZAa@al>

[-- Attachment #1: Type: text/plain, Size: 2306 bytes --]

On 06/15/2013 04:25 PM, Peter Wu wrote:
> On Saturday 15 June 2013 16:14:23 Eric Blake wrote:
>> On 06/08/2013 10:49 PM, Peter Wu wrote:
>>> When QEMU starts, it always changes the serial port parameters including
>>> baud rate. This confused my guest which thought it was outputting at 9600
>>> baud while it was in fact changed to 115200.
>>>
>>> After this patch, I can use `-serial /dev/ttyS0,baud=9600` to override the
>>> default baud rate of 115200. Documentation is updated as well, so that
>>> users know about the new `baud` parameter for `-serial` and `-chardev
>>> serial` (and its alias `-chardev tty`).
>>>
>>> Note that the baud option is not implemented for Windows. QEMU does not
>>> change the default baud rate on Windows anyway. If somebody is going to
>>> implement it, do not forget to update the documentation on "COM" devices
>>> which is also of backend serial.
>>>

>>> -                                       'serial' : 'ChardevHostdev',
>>> +                                       'serial' : 'ChardevSerial',
>>
>> without introspection, libvirt has no idea whether 'baud' is supported
>> in the qemu it is talking to, other than trying and failing when talking
>> to older qemu.  This patch forms yet another reason why libvirt wants to
>> learn when we add optional parameters to a pre-existing QMP command.
> 
> I have do not use libvirt, do you want me to do further things for this patch 
> to get accepted? Or is it more a side-note?

I'm wondering if there is an alternative that we can come up with that
doesn't require the addition of an optional parameter, and therefore
something that libvirt could reliably use without needing Amos'
introspection support to go in first.  Besides, weren't some of the
other review comments in this thread questioning whether we should even
allow users to set baud rate at creation, or should we be fixing the
real underlying bug of not matching bare-metal hardware that always
initializes to a fixed rate of 9600?  That is, I think there are still
unanswered questions that must be resolved before we can even decide
whether an amended version of this patch is even worth including.

-- 
Eric Blake   eblake redhat com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 621 bytes --]

      reply	other threads:[~2013-06-15 15:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-08 21:49 [Qemu-devel] [PATCH] chardev: add baud parameter for serial host device Peter Wu
2013-06-10  5:56 ` Gerd Hoffmann
2013-06-10  8:42   ` Peter Wu
2013-06-10 12:58     ` Gerd Hoffmann
2013-06-10 13:23       ` Andreas Färber
2013-06-10 13:28       ` Peter Wu
2013-06-10 13:51         ` Peter Wu
2013-06-15 15:14 ` Eric Blake
2013-06-15 15:25   ` Peter Wu
2013-06-15 15:38     ` Eric Blake [this message]

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=51BC8A8B.3030607@redhat.com \
    --to=eblake@redhat.com \
    --cc=aliguori@us.ibm.com \
    --cc=lekensteyn@gmail.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).