From: Arnd Bergmann <arnd@arndb.de>
To: Avi Kivity <avi@qumranet.com>
Cc: kvm-devel@lists.sourceforge.net,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [kvm-devel] [PATCH][RFC] KVM: prepare user interface for smp guests
Date: Mon, 30 Oct 2006 13:19:10 +0100 [thread overview]
Message-ID: <200610301319.10710.arnd@arndb.de> (raw)
In-Reply-To: <4545C110.8080204@qumranet.com>
On Monday 30 October 2006 10:08, Avi Kivity wrote:
> > Your concept of allocating
> > a new context on each open is already weird, but there have been other
> > examples of that before.
>
> Actually that seemed to me quite natural.
It's described in LDD2 and other books, but the traditional view is
still that one device node in /dev refers to an actual device or
at least something that acts like a device (e.g. /dev/null, dev/tty).
> BTW, what does lsof show for spufs users? I thought lsof /dev/kvm would
> be a good way to look for virtual machines.
It does what you expect. Since spufs is mounted, 'ls /spu/' shows you
the existing spu contexts, 'lsof /spu/*' shows you the tasks using those.
Arnd <><
prev parent reply other threads:[~2006-10-30 12:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 13:31 [PATCH][RFC] KVM: prepare user interface for smp guests Avi Kivity
2006-10-30 0:01 ` [kvm-devel] " Arnd Bergmann
2006-10-30 9:08 ` Avi Kivity
2006-10-30 12:19 ` Arnd Bergmann [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=200610301319.10710.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=avi@qumranet.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox