From: ebiederm@xmission.com (Eric W. Biederman)
To: riya khanna <riyakhanna1983@gmail.com>
Cc: LXC development mailing-list
<lxc-devel@lists.linuxcontainers.org>,
Miklos Szeredi <miklos@szeredi.hu>,
fuse-devel <fuse-devel@lists.sourceforge.net>,
Tejun Heo <tj@kernel.org>,
Seth Forshee <seth.forshee@canonical.com>,
linux-kernel@vger.kernel.org,
Serge Hallyn <serge.hallyn@ubuntu.com>
Subject: Re: Using devices in Containers
Date: Thu, 25 Sep 2014 11:21:50 -0700 [thread overview]
Message-ID: <87iokbd0ht.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <CALRD3qLYAc+K8e1xYb27ipi4KyGRmTxokPCHN0L_zta=Cy9sCQ@mail.gmail.com> (riya khanna's message of "Wed, 24 Sep 2014 19:25:09 -0500")
riya khanna <riyakhanna1983@gmail.com> writes:
> What kind of existing multiplexers could be used? Is there one for fb? We have
> evdev abstractions for input in place already.
We have X and Wayland/Weston and pulse audio and doubtless more that I
am not aware of.
For video a lot of working is going into compositing and handling
multiple contexts in the hardware so there may already be support in the
kernel.
Fundamentally these are all pieces of hardware we allow multiple
userspace applications access to their information or to modify.
Therefore there is existing multiplexing somewhere.
I won't claim all of the existing multiplexing methods are good and
should be used as is, but they definitely should be used as a starting
point.
>From another perspective there is how kvm tackles this today. If you
really want to emulate the hardware and make it appear that your
instance of userspace has direct hardware access building upon the
infrastructure that is used for kvm may be worth exploring.
Eric
next prev parent reply other threads:[~2014-09-25 18:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CALRD3qKmpzJCRszkG_S9Z3XgoTGWVMFd7FqeJh+W-9pZqPVhCg@mail.gmail.com>
2014-09-24 5:04 ` [lxc-devel] device namespaces Eric W. Biederman
[not found] ` <CALRD3qKPJHmmY2DSNNfNKzmLihDLm9fgBQprCXNMHVOArV4iuw@mail.gmail.com>
2014-09-24 16:37 ` Serge Hallyn
2014-09-24 17:43 ` Using devices in Containers (was: [lxc-devel] device namespaces) Eric W. Biederman
2014-09-24 19:30 ` Riya Khanna
2014-09-24 22:38 ` Using devices in Containers Eric W. Biederman
[not found] ` <CALRD3qLYAc+K8e1xYb27ipi4KyGRmTxokPCHN0L_zta=Cy9sCQ@mail.gmail.com>
2014-09-25 15:40 ` riya khanna
2014-09-25 18:09 ` Eric W. Biederman
2014-09-25 18:21 ` Eric W. Biederman [this message]
2014-09-24 19:07 ` [lxc-devel] device namespaces Riya Khanna
2014-09-24 16:38 ` Serge Hallyn
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=87iokbd0ht.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=fuse-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=lxc-devel@lists.linuxcontainers.org \
--cc=miklos@szeredi.hu \
--cc=riyakhanna1983@gmail.com \
--cc=serge.hallyn@ubuntu.com \
--cc=seth.forshee@canonical.com \
--cc=tj@kernel.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 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.