From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f53.google.com (mail-pa0-f53.google.com [209.85.220.53]) by dpdk.org (Postfix) with ESMTP id B60375963 for ; Tue, 6 Oct 2015 09:34:09 +0200 (CEST) Received: by pacex6 with SMTP id ex6so202563007pac.0 for ; Tue, 06 Oct 2015 00:34:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:date:from:to:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=LRBGF0g0pTS6plKGB5g6zkWwyWKEf8ZFEXbYqT/y8fo=; b=SgNyzpEndVCzv1Cy2eXc02FINLNTlRe8y5EAxu7rb3VPr9Q8+Y2dULZ7WU1T48vZXI Ty/uD+1BdXMr/AGfts1JpaiRmcpL1fH4Q2KsK5r1XTWzpcYP1csHxs/0ZM52GN4+6wCQ Sh3BeoXJqFLW65j9haJzr7IOT1vXhH9UUp5+PDQMlCiO3OX5VsSDucolHR/ENC2jwNVW FGFcT1ZX8VmkYaawlgU5FFFidzmbcp9vtmbHA0mGUorWa6Eqpm/7PGnbdmlXBfuwUCfn CoEEQS6BXsmPjWSCvAVtk3liSVQv3VCDY4yxztsjhQhKXMehANIHjc6MNFCsK2p7JlKS 8XTg== X-Gm-Message-State: ALoCoQnOncXM5hN6SzREdCda5pJLgu0Zr3lQzKY3jJvTYSx/YltWeicIpZGO8C1ds4L/5AYZocgW X-Received: by 10.66.255.42 with SMTP id an10mr44678582pad.107.1444116849025; Tue, 06 Oct 2015 00:34:09 -0700 (PDT) Received: from uryu.home.lan ([144.49.132.22]) by smtp.gmail.com with ESMTPSA id rw8sm31771073pac.11.2015.10.06.00.34.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 06 Oct 2015 00:34:08 -0700 (PDT) Date: Tue, 6 Oct 2015 08:33:56 +0100 From: Stephen Hemminger To: "Michael S. Tsirkin" Message-ID: <20151006083356.3da3defa@uryu.home.lan> In-Reply-To: <20151006013000-mutt-send-email-mst@redhat.com> References: <1443652138-31782-1-git-send-email-stephen@networkplumber.org> <1443652138-31782-3-git-send-email-stephen@networkplumber.org> <20151001104505-mutt-send-email-mst@redhat.com> <20151005215455.GA7608@redhat.com> <20151006013000-mutt-send-email-mst@redhat.com> X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, hjk@hansjkoch.de, gregkh@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [dpdk-dev] [PATCH 2/2] uio: new driver to support PCI MSI-X X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Oct 2015 07:34:10 -0000 Other than implementation objections, so far the two main arguments against this reduce to: 1. If you allow UIO ioctl then it opens an API hook for all the crap out of tree UIO drivers to do what they want. 2. If you allow UIO MSI-X then you are expanding the usage of userspace device access in an insecure manner. Another alternative which I explored was making a version of VFIO that works without IOMMU. It solves #1 but actually increases the likely negative response to arguent #2. This would keep same API, and avoid having to modify UIO. But we would still have the same (if not more resistance) from IOMMU developers who believe all systems have to be secure against root.