From: Wei Liu <wei.liu2@citrix.com>
To: Dongli Zhang <dongli.zhang@oracle.com>
Cc: <xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>,
<boris.ostrovsky@oracle.com>, <jgross@suse.com>,
<ian.jackson@eu.citrix.com>, <wei.liu2@citrix.com>,
<srinivas.eeda@oracle.com>
Subject: Re: [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch)
Date: Mon, 23 Apr 2018 15:09:11 +0100 [thread overview]
Message-ID: <20180423140911.bihiwfwtlneobgzd@citrix.com> (raw)
In-Reply-To: <1523100355-27647-1-git-send-email-dongli.zhang@oracle.com>
On Sat, Apr 07, 2018 at 07:25:53PM +0800, Dongli Zhang wrote:
> About per-domU xenwatch thread create/destroy, a new type of xenstore node is
> introduced: '/local/domain/0/mtwatch/<domid>'.
>
> Suppose the new domid id 7. During the domU (domid=7) creation, the xen
> toolstack writes '/local/domain/0/mtwatch/7' to xenstore before the insertion
> of '/local/domain/7'. When the domid=7 is destroyed, the last xenstore
> operation by xen toolstack is to remove '/local/domain/0/mtwatch/7'.
>
> The dom0 kernel subscribes a watch at node '/local/domain/0/mtwatch'. Kernel
> thread [xen-mtwatch-7] is created when '/local/domain/0/mtwatch/7' is inserted,
> while this kernel thread is destroyed when the corresponding xenstore node is
> removed.
Instead of inventing yet another node, can you not watch /local/domain
directly?
Wei.
next prev parent reply other threads:[~2018-04-23 14:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-07 11:25 Dongli Zhang
2018-04-07 11:25 ` [PATCH RFC linux 1/2] xenbus: introduce xenwatch multithreading to dom0 linux kernel Dongli Zhang
2018-04-07 11:25 ` [PATCH RFC xen 2/2] libxl: introduce xenwatch multithreading to xen toolstack Dongli Zhang
2018-04-07 11:59 ` [RFC 0/2] To introduce xenwatch multithreading (xen mtwatch) Juergen Gross
2018-04-07 14:22 ` [Xen-devel] " Dongli Zhang
2018-04-23 14:09 ` Wei Liu [this message]
2018-04-23 23:55 ` Dongli Zhang
2018-04-24 5:22 ` Juergen Gross
2018-04-24 5:52 ` Dongli Zhang
2018-04-24 6:03 ` Juergen Gross
2018-04-24 6:10 ` Dongli Zhang
2018-04-24 6:23 ` Juergen Gross
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=20180423140911.bihiwfwtlneobgzd@citrix.com \
--to=wei.liu2@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=dongli.zhang@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=srinivas.eeda@oracle.com \
--cc=xen-devel@lists.xenproject.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
all inboxes | Powered by JetHome®