From: Octavian Purdila <tavip@google.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>, armbru@redhat.com
Cc: qemu-devel@nongnu.org, eblake@redhat.com,
peter.maydell@linaro.org, berrange@redhat.com,
Paulo Neves <ptsneves@gmail.com>
Subject: Re: [PATCH v4] chardev: add path option for pty backend
Date: Mon, 7 Oct 2024 18:29:01 -0700 [thread overview]
Message-ID: <CAGWr4cRM6o2tJJi1vVw4SPagUqiJPrmtNYUhn4rSuGpwHeSnDA@mail.gmail.com> (raw)
In-Reply-To: <CAJ+F1CLhDSMzT31TCiCuoXegyhAeSNr4Ly3Jm4Aqp9SFYW+kAg@mail.gmail.com>
On Tue, Sep 3, 2024 at 12:14 AM Marc-André Lureau
<marcandre.lureau@gmail.com> wrote:
>
>
>
> On Tue, Aug 6, 2024 at 5:09 AM Octavian Purdila <tavip@google.com> wrote:
>>
>> Add path option to the pty char backend which will create a symbolic
>> link to the given path that points to the allocated PTY.
>>
>> This avoids having to make QMP or HMP monitor queries to find out what
>> the new PTY device path is.
>>
>> Based on patch from Paulo Neves:
>>
>> https://patchew.org/QEMU/1548509635-15776-1-git-send-email-ptsneves@gmail.com/
>>
>> Tested with the following invocations that the link is created and
>> removed when qemu stops:
>>
>> qemu-system-x86_64 -nodefaults -mon chardev=compat_monitor \
>> -chardev pty,path=test,id=compat_monitor0
>>
>> qemu-system-x86_64 -nodefaults -monitor pty:test
>>
>> # check QMP invocation with path set
>> qemu-system-x86_64 -nodefaults -qmp tcp:localhost:4444,server=on,wait=off
>> nc localhost 4444
>> > {"execute": "qmp_capabilities"}
>> > {"execute": "chardev-add", "arguments": {"id": "bar", "backend": {
>> "type": "pty", "data": {"path": "test" }}}}
>>
>> # check QMP invocation with path not set
>> qemu-system-x86_64 -nodefaults -qmp tcp:localhost:4444,server=on,wait=off
>> nc localhost 4444
>> > {"execute": "qmp_capabilities"}
>> > {"execute": "chardev-add", "arguments": {"id": "bar", "backend": {
>> "type": "pty", "data": {}}}}
>>
>> Also tested that when a link path is not passed invocations still work, e.g.:
>>
>> qemu-system-x86_64 -monitor pty
>>
>> Co-authored-by: Paulo Neves <ptsneves@gmail.com>
>> Signed-off-by: Paulo Neves <ptsneves@gmail.com>
>> [OP: rebase and address original patch review comments]
>> Signed-off-by: Octavian Purdila <tavip@google.com>
>
>
> Reviewed-by: Marc-André Lureau <marcandre.lureau@redhat.com>
>
Ping, it looks like this got lost.
https://patchew.org/QEMU/20240605185050.1678102-1-tavip@google.com/
prev parent reply other threads:[~2024-10-08 1:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-06 1:07 [PATCH v4] chardev: add path option for pty backend Octavian Purdila
2024-09-03 7:13 ` Marc-André Lureau
2024-10-08 1:29 ` Octavian Purdila [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=CAGWr4cRM6o2tJJi1vVw4SPagUqiJPrmtNYUhn4rSuGpwHeSnDA@mail.gmail.com \
--to=tavip@google.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=ptsneves@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).