All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Blake <eblake@redhat.com>
To: xiaoqiang zhao <zxq_yx_007@163.com>, qemu-devel@nongnu.org
Cc: kwolf@redhat.com, peter.maydell@linaro.org, berrange@redhat.com,
	armbru@redhat.com, kraxel@redhat.com, pbonzini@redhat.com,
	marcandre.lureau@redhat.com
Subject: Re: [PATCH v4 3/3] qemu-options: updates for abstract unix sockets
Date: Fri, 15 May 2020 12:37:39 -0500	[thread overview]
Message-ID: <df4fe148-90af-771d-641e-0579e2049cc3@redhat.com> (raw)
In-Reply-To: <20200515043235.32189-4-zxq_yx_007@163.com>

On 5/14/20 11:32 PM, xiaoqiang zhao wrote:
> add options documents changes for -chardev
> 
> Signed-off-by: xiaoqiang zhao <zxq_yx_007@163.com>
> Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>   qemu-options.hx | 9 +++++++--
>   1 file changed, 7 insertions(+), 2 deletions(-)

I'd suggest listing 'abstract' before 'tight', since 'tight' only 
matters for abstract.  I also have grammar suggestions:

> -    ``unix options: path=path``
> +    ``unix options: path=path[,tight=on|off][,abstract=on|off]``
>           ``path`` specifies the local path of the unix socket. ``path``
>           is required.
> +	``tight`` whether to set @addrlen to the minimal string length,
> +        or the maximum sun_path length. defaults to true. ``tight`` is
> +        optional.
> +	``abstract`` whether use abstract address. defaults to false.
> +	``abstract`` is optional.

``abstract`` specifies the use of the abstract socket namespace, rather 
than the filesystem.  Optional, defaults to false.
``tight`` sets the socket length of abstract sockets to their minimum, 
rather than the full sun_path length.  Optional, defaults to true.

-- 
Eric Blake, Principal Software Engineer
Red Hat, Inc.           +1-919-301-3226
Virtualization:  qemu.org | libvirt.org



  reply	other threads:[~2020-05-15 17:38 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15  4:32 [PATCH v4 0/3] qemu-sockets: add abstract UNIX domain socket support xiaoqiang zhao
2020-05-15  4:32 ` [PATCH v4 1/3] " xiaoqiang zhao
2020-05-15  4:32 ` [PATCH v4 2/3] tests/util-sockets: add abstract unix socket cases xiaoqiang zhao
2020-05-15  8:09   ` Daniel P. Berrangé
2020-05-15  4:32 ` [PATCH v4 3/3] qemu-options: updates for abstract unix sockets xiaoqiang zhao
2020-05-15 17:37   ` Eric Blake [this message]
2020-05-16  3:01     ` xiaoqiang zhao

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=df4fe148-90af-771d-641e-0579e2049cc3@redhat.com \
    --to=eblake@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=zxq_yx_007@163.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 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.