From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, Marcelo Tosatti <mtosatti@redhat.com>,
"David S. Ahern" <daahern@cisco.com>,
Mark Marshall <mark.marshall60@ntlworld.com>,
KVM list <kvm@vger.kernel.org>
Subject: Re: more about serial ports: do they even work?
Date: Wed, 04 Feb 2009 11:09:34 +0000 [thread overview]
Message-ID: <4989776E.1060504@eu.citrix.com> (raw)
In-Reply-To: <498953BA.7060407@msgid.tls.msk.ru>
Michael Tokarev wrote:
> Other than that, an.. excellent idea, I wanted to propose
> just that when I first saw all this stuff, but was somewhat
> afraid. And I *think* there's at least *some* sense. Qemu
> is a CPU emulator and may work on another arch where those
> bits are defined differently. Maybe that was the reason for
> all this converting - to be safe than sorry, so to say. No?
>
Yes, this is exactly the reason why they were introduced in the first place.
Let's suppose that the guest defines those constants differently: we
need to parse them and covert them appropriately to the host format.
CHR_IOCTL_SERIAL_SET_TIOCM and CHR_TIOCM_DTR correspond to the guest
version of TIOCMSET and TIOCM_DTR and can be defined differently
depending on the particular guest arch.
WARNING: multiple messages have this Message-ID (diff)
From: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
To: Michael Tokarev <mjt@tls.msk.ru>
Cc: qemu-devel@nongnu.org, Marcelo Tosatti <mtosatti@redhat.com>,
"David S. Ahern" <daahern@cisco.com>,
Mark Marshall <mark.marshall60@ntlworld.com>,
KVM list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: more about serial ports: do they even work?
Date: Wed, 04 Feb 2009 11:09:34 +0000 [thread overview]
Message-ID: <4989776E.1060504@eu.citrix.com> (raw)
In-Reply-To: <498953BA.7060407@msgid.tls.msk.ru>
Michael Tokarev wrote:
> Other than that, an.. excellent idea, I wanted to propose
> just that when I first saw all this stuff, but was somewhat
> afraid. And I *think* there's at least *some* sense. Qemu
> is a CPU emulator and may work on another arch where those
> bits are defined differently. Maybe that was the reason for
> all this converting - to be safe than sorry, so to say. No?
>
Yes, this is exactly the reason why they were introduced in the first place.
Let's suppose that the guest defines those constants differently: we
need to parse them and covert them appropriately to the host format.
CHR_IOCTL_SERIAL_SET_TIOCM and CHR_TIOCM_DTR correspond to the guest
version of TIOCMSET and TIOCM_DTR and can be defined differently
depending on the particular guest arch.
next prev parent reply other threads:[~2009-02-04 11:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-26 20:20 more about serial ports: do they even work? Michael Tokarev
2009-01-26 20:39 ` Michael Tokarev
2009-02-02 21:27 ` David S. Ahern
2009-02-02 21:27 ` [Qemu-devel] " David S. Ahern
2009-02-02 21:32 ` Michael Tokarev
2009-02-02 21:32 ` [Qemu-devel] " Michael Tokarev
2009-02-02 21:36 ` David S. Ahern
2009-02-02 21:36 ` [Qemu-devel] " David S. Ahern
2009-02-03 8:13 ` Michael Tokarev
2009-02-03 8:13 ` [Qemu-devel] " Michael Tokarev
2009-02-03 8:41 ` Mark Marshall
2009-02-03 8:41 ` [Qemu-devel] " Mark Marshall
2009-02-04 8:09 ` Marcelo Tosatti
2009-02-04 8:09 ` [Qemu-devel] " Marcelo Tosatti
2009-02-04 8:37 ` Michael Tokarev
2009-02-04 8:37 ` [Qemu-devel] " Michael Tokarev
2009-02-04 8:52 ` Marcelo Tosatti
2009-02-04 8:52 ` [Qemu-devel] " Marcelo Tosatti
2009-02-04 8:56 ` Michael Tokarev
2009-02-04 8:56 ` [Qemu-devel] " Michael Tokarev
2009-02-04 11:09 ` Stefano Stabellini [this message]
2009-02-04 11:09 ` Stefano Stabellini
2009-02-05 18:36 ` David S. Ahern
2009-02-05 18:36 ` [Qemu-devel] " David S. Ahern
2009-02-05 20:50 ` Stefano Stabellini
2009-02-05 20:50 ` [Qemu-devel] " Stefano Stabellini
2009-02-04 11:17 ` Stefano Stabellini
2009-02-04 11:17 ` Stefano Stabellini
2009-02-05 18:33 ` [PATCH, finally]: " Michael Tokarev
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=4989776E.1060504@eu.citrix.com \
--to=stefano.stabellini@eu.citrix.com \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.org \
--cc=mark.marshall60@ntlworld.com \
--cc=mjt@tls.msk.ru \
--cc=mtosatti@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 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.