From: Wei Liu <wei.liu2@citrix.com>
To: Bob Liu <bob.liu@oracle.com>
Cc: joao.m.martins@oracle.com, xen-devel@lists.xensource.com,
Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] tools:libxl: return tty path for all serials
Date: Wed, 3 Aug 2016 10:11:12 +0100 [thread overview]
Message-ID: <20160803091112.GE15013@citrix.com> (raw)
In-Reply-To: <1470187639-10191-1-git-send-email-bob.liu@oracle.com>
I would suggest changing the title to
libxl: return any serial tty path in libxl_console_get_tty
On Wed, Aug 03, 2016 at 09:27:19AM +0800, Bob Liu wrote:
> When specifying a serial list in domain config, users of
> libxl_console_get_tty cannot get the tty path of a second specified pty serial,
> since right now it always returns the tty path of serial 0.
>
> Signed-off-by: Bob Liu <bob.liu@oracle.com>
> ---
> tools/libxl/libxl.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tools/libxl/libxl.c b/tools/libxl/libxl.c
> index 2cf7451..00af286 100644
> --- a/tools/libxl/libxl.c
> +++ b/tools/libxl/libxl.c
> @@ -1795,7 +1795,7 @@ int libxl_console_get_tty(libxl_ctx *ctx, uint32_t domid, int cons_num,
>
> switch (type) {
> case LIBXL_CONSOLE_TYPE_SERIAL:
> - tty_path = GCSPRINTF("%s/serial/0/tty", dom_path);
> + tty_path = GCSPRINTF("%s/serial/%d/tty", dom_path, cons_num);
Code-wise, this patch looks good to me. It's a valid bug fix that should
be backported.
Please CC Ian and me in your future submissions.
Wei.
> break;
> case LIBXL_CONSOLE_TYPE_PV:
> if (cons_num == 0)
> --
> 1.7.10.4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-08-03 9:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 1:27 [PATCH] tools:libxl: return tty path for all serials Bob Liu
2016-08-03 9:11 ` Wei Liu [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=20160803091112.GE15013@citrix.com \
--to=wei.liu2@citrix.com \
--cc=bob.liu@oracle.com \
--cc=joao.m.martins@oracle.com \
--cc=xen-devel@lists.xensource.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).