linux-kernel - Re: [PATCH 1/7] KVM: userspace interface

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061019232616.GA4876@kroah.com>
Date:	Thu, 19 Oct 2006 16:26:16 -0700
From:	Greg KH <greg@...ah.com>
To:	Avi Kivity <avi@...ranet.com>
Cc:	John Stoffel <john@...ffel.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/7] KVM: userspace interface

On Thu, Oct 19, 2006 at 04:43:20PM +0200, Avi Kivity wrote:
> John Stoffel wrote:
> >Avi> This patch defines a bunch of ioctl()s on /dev/kvm.  The ioctl()s
> >Avi> allow adding memory to a virtual machine, adding a virtual cpu to
> >Avi> a virtual machine (at most one at this time), transferring
> >Avi> control to the virtual cpu, and querying about guest pages
> >Avi> changed by the virtual machine.
> >
> >Yuck.  ioclts are deprecated, you should be using /sysfs instead for
> >stuff like this, or configfs.  
> >  
> 
> I need to pass small amounts of data back and forth very efficiently.  
> sysfs and configfs are more for one-time admin stuff, not for continuous 
> device control.

I agree, sysfs or configfs is not for what you are wanting to do here.

thanks,

greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/