From: Marcelo Tosatti <mtosatti@redhat.com>
To: Mark Marshall <mark.marshall60@ntlworld.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, KVM list <kvm@vger.kernel.org>,
"David S. Ahern" <daahern@cisco.com>,
qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: more about serial ports: do they even work?
Date: Wed, 4 Feb 2009 06:09:42 -0200 [thread overview]
Message-ID: <20090204080942.GA3640@amt.cnet> (raw)
In-Reply-To: <4988032A.5010905@ntlworld.com>
On Tue, Feb 03, 2009 at 08:41:14AM +0000, Mark Marshall wrote:
> Michael Tokarev wrote:
>> David S. Ahern wrote:
>>> Michael Tokarev wrote:
>>>> David S. Ahern wrote:
>>>>> I don't recall seeing a followup to this post.
>>>>>
>>>>> To put Michael's second suggestion into patch form, the following fixes
>>>>> the problem for me:
>>>>>
>>>>> --- kvm-81.orig/qemu/qemu-char.c 2008-12-14 06:16:27.000000000 -0700
>>>>> +++ kvm-81/qemu/qemu-char.c 2009-02-02 14:12:20.000000000 -0700
>>>>> @@ -1078,20 +1078,21 @@
>>>>> if (sarg | TIOCM_DTR)
>>>>> *targ |= CHR_TIOCM_DTR;
>>>>> if (sarg | TIOCM_RTS)
>>>>> *targ |= CHR_TIOCM_RTS;
>>>>> }
>>>>> break;
>>>>> case CHR_IOCTL_SERIAL_SET_TIOCM:
>>>>> {
>>>>> int sarg = *(int *)arg;
>>>>> int targ = 0;
>>>>> + ioctl(s->fd_in, TIOCMGET, &targ);
>>>> here, one more operation is necessary:
>>>> targ &= ~(TIOCM_DTR|TIOCM_RTS);
>>> Interesting. that change was not needed to fix my problem.
>>
>> It just means you (or, rather, your guests) never really needed to
>> DROP those signal lines, only to raise them.
>>
>>>>> if (sarg | CHR_TIOCM_DTR)
>>>>> targ |= TIOCM_DTR;
>>>>> if (sarg | CHR_TIOCM_RTS)
>>>>> targ |= TIOCM_RTS;
> Is this code really correct. If it is is there a comment somewhere
> describing why it's correct? I would have expected the lines above to
> be:
>
> if (sarg & CHR_TIOCM_DTR)
> targ |= TIOCM_DTR;
> if (sarg & CHR_TIOCM_RTS)
> targ |= TIOCM_RTS;
>
> (Just an observation as this went past).
Right. I don't understand the point of converting to an "internal"
representation of TIOCM control bits.
CHR_IOCTL_SERIAL_SET_TIOCM is clearly broken as mentioned. It should at
least preserve the bits it does not control.
diff --git a/qemu/qemu-char.c b/qemu/qemu-char.c
index ac431c7..66971e1 100644
--- a/qemu/qemu-char.c
+++ b/qemu/qemu-char.c
@@ -1063,33 +1063,12 @@ static int tty_serial_ioctl(CharDriverState *chr, int cmd, void *arg)
break;
case CHR_IOCTL_SERIAL_GET_TIOCM:
{
- int sarg = 0;
- int *targ = (int *)arg;
- ioctl(s->fd_in, TIOCMGET, &sarg);
- *targ = 0;
- if (sarg | TIOCM_CTS)
- *targ |= CHR_TIOCM_CTS;
- if (sarg | TIOCM_CAR)
- *targ |= CHR_TIOCM_CAR;
- if (sarg | TIOCM_DSR)
- *targ |= CHR_TIOCM_DSR;
- if (sarg | TIOCM_RI)
- *targ |= CHR_TIOCM_RI;
- if (sarg | TIOCM_DTR)
- *targ |= CHR_TIOCM_DTR;
- if (sarg | TIOCM_RTS)
- *targ |= CHR_TIOCM_RTS;
+ ioctl(s->fd_in, TIOCMGET, arg);
}
break;
case CHR_IOCTL_SERIAL_SET_TIOCM:
{
- int sarg = *(int *)arg;
- int targ = 0;
- if (sarg | CHR_TIOCM_DTR)
- targ |= TIOCM_DTR;
- if (sarg | CHR_TIOCM_RTS)
- targ |= TIOCM_RTS;
- ioctl(s->fd_in, TIOCMSET, &targ);
+ ioctl(s->fd_in, TIOCMSET, arg);
}
break;
default:
next prev parent reply other threads:[~2009-02-04 8:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <497E1B15.2090908@msgid.tls.msk.ru>
[not found] ` <497E1F7D.90300@msgid.tls.msk.ru>
2009-02-02 21:27 ` [Qemu-devel] Re: more about serial ports: do they even work? David S. Ahern
2009-02-02 21:32 ` Michael Tokarev
2009-02-02 21:36 ` David S. Ahern
2009-02-03 8:13 ` Michael Tokarev
2009-02-03 8:41 ` Mark Marshall
2009-02-04 8:09 ` Marcelo Tosatti [this message]
2009-02-04 8:37 ` Michael Tokarev
2009-02-04 8:52 ` Marcelo Tosatti
2009-02-04 8:56 ` Michael Tokarev
2009-02-04 11:09 ` Stefano Stabellini
2009-02-05 18:36 ` David S. Ahern
2009-02-05 20:50 ` Stefano Stabellini
2009-02-04 11:17 ` Stefano Stabellini
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=20090204080942.GA3640@amt.cnet \
--to=mtosatti@redhat.com \
--cc=daahern@cisco.com \
--cc=kvm@vger.kernel.org \
--cc=mark.marshall60@ntlworld.com \
--cc=mjt@tls.msk.ru \
--cc=qemu-devel@nongnu.org \
--cc=stefano.stabellini@eu.citrix.com \
/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).