From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Lutomirski Subject: Re: [PATCH 00/12] Add kdbus implementation Date: Wed, 29 Oct 2014 15:15:51 -0700 Message-ID: References: <1414620056-6675-1-git-send-email-gregkh@linuxfoundation.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: In-Reply-To: <1414620056-6675-1-git-send-email-gregkh@linuxfoundation.org> Sender: linux-kernel-owner@vger.kernel.org To: Greg Kroah-Hartman Cc: Linux API , "linux-kernel@vger.kernel.org" , John Stultz , Arnd Bergmann , Tejun Heo , Marcel Holtmann , Ryan Lortie , Bastien Nocera , David Herrmann , Djalal Harouni , simon.mcvittie@collabora.co.uk, daniel@zonque.org, alban.crequy@collabora.co.uk, javier.martinez@collabora.co.uk, Tom Gundersen List-Id: linux-api@vger.kernel.org (reply 1/2 -- I'm replying twice to keep the threading sane) On Wed, Oct 29, 2014 at 3:00 PM, Greg Kroah-Hartman wrote: > kdbus is a kernel-level IPC implementation that aims for resemblance to > the the protocol layer with the existing userspace D-Bus daemon while > enabling some features that couldn't be implemented before in userspace. > > * Support for multiple domains, completely separated from each other, > allowing multiple virtualized instances to be used at the same time. Given that there is no such thing as a device namespace, how does this work? The docs seem a bit confusing to me as to whether there's a hierarchy of domains. Do domains have a concept of a parent? What's "container-name"? Given that domains have random IDs, how can they be checkpointed and restored? --Andy