Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754999Ab2BCWwN (ORCPT ); Fri, 3 Feb 2012 17:52:13 -0500 Received: from mail-pz0-f46.google.com ([209.85.210.46]:49949 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753740Ab2BCWwM (ORCPT ); Fri, 3 Feb 2012 17:52:12 -0500 Message-ID: <4F2C6517.3040203@codemonkey.ws> Date: Fri, 03 Feb 2012 16:52:07 -0600 From: Anthony Liguori User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.23) Gecko/20110922 Lightning/1.0b2 Thunderbird/3.1.15 MIME-Version: 1.0 To: Eric Northup CC: Avi Kivity , linux-kernel , KVM list , qemu-devel Subject: Re: [Qemu-devel] [RFC] Next gen kvm api References: <4F2AB552.2070909@redhat.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 957 Lines: 30 On 02/03/2012 12:07 PM, Eric Northup wrote: > On Thu, Feb 2, 2012 at 8:09 AM, Avi Kivity wrote: > [...] >> >> Moving to syscalls avoids these problems, but introduces new ones: >> >> - adding new syscalls is generally frowned upon, and kvm will need several >> - syscalls into modules are harder and rarer than into core kernel code >> - will need to add a vcpu pointer to task_struct, and a kvm pointer to >> mm_struct > - Lost a good place to put access control (permissions on /dev/kvm) > for which user-mode processes can use KVM. > > How would the ability to use sys_kvm_* be regulated? Why should it be regulated? It's not a finite or privileged resource. Regards, Anthony Liguori > -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/