From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-6.9 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5A1F9C4332B for ; Fri, 20 Mar 2020 20:59:47 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 197CC20658 for ; Fri, 20 Mar 2020 20:59:47 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=redhat.com header.i=@redhat.com header.b="BozUlhIa" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727135AbgCTU7p (ORCPT ); Fri, 20 Mar 2020 16:59:45 -0400 Received: from us-smtp-delivery-74.mimecast.com ([216.205.24.74]:39069 "EHLO us-smtp-delivery-74.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726912AbgCTU7p (ORCPT ); Fri, 20 Mar 2020 16:59:45 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1584737984; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=VGrhaAgQuGc4nR5mDjGTeAxa5W8ePSIqBYL4zLw6fxw=; b=BozUlhIavgSKPfdCDobBwxpMDzrX80oiQuQKKSXu0P9kUPyZaTLIS7uoJuP4jASOSxdhwP YNjLbd2HJmbDUuaqbGFuhiNJ7XtjX8oi1WxXEXwdjFM+JNIEr9HVV2g2+f0a72AR/D6I4j jYe2pt/bXotjPMEfK8zyo09hf1buTZk= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-135-H-tmYnP7P422El7JWjAGDQ-1; Fri, 20 Mar 2020 16:59:37 -0400 X-MC-Unique: H-tmYnP7P422El7JWjAGDQ-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5EF2A107ACC4; Fri, 20 Mar 2020 20:59:36 +0000 (UTC) Received: from w520.home (ovpn-112-162.phx2.redhat.com [10.3.112.162]) by smtp.corp.redhat.com (Postfix) with ESMTP id B1B5D17B91; Fri, 20 Mar 2020 20:59:35 +0000 (UTC) Date: Fri, 20 Mar 2020 14:59:35 -0600 From: Alex Williamson To: Yonghyun Hwang Cc: Kirti Wankhede , Cornelia Huck , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Havard Skinnemoen , Moritz Fischer , Joshua Lang Subject: Re: [PATCH] vfio-mdev: support mediated device creation in kernel Message-ID: <20200320145935.4617c7c0@w520.home> In-Reply-To: References: <20200320175910.180266-1-yonghyun@google.com> <20200320123425.49c6568e@w520.home> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 20 Mar 2020 13:46:04 -0700 Yonghyun Hwang wrote: > On Fri, Mar 20, 2020 at 11:34 AM Alex Williamson > wrote: > > > > On Fri, 20 Mar 2020 10:59:10 -0700 > > Yonghyun Hwang wrote: > > > > > To enable a mediated device, a device driver registers its device to VFIO > > > MDev framework. Once the mediated device gets enabled, UUID gets fed onto > > > the sysfs attribute, "create", to create the mediated device. This > > > additional step happens after boot-up gets complete. If the driver knows > > > how many mediated devices need to be created during probing time, the > > > additional step becomes cumbersome. This commit implements a new function > > > to allow the driver to create a mediated device in kernel. > > > > But pre-creating mdev devices seems like a policy decision. Why can't > > userspace make such a policy decision, and do so with persistent uuids, > > via something like mdevctl? Thanks, > > > > Alex > > Yep, it can be viewed as the policy decision and userspace can make > the decision. However, it would be handy and plausible, if a device > driver can pre-create "fixed or default" # of mdev devices, while > allowing the device policy to come into play after bootup gets > complete. Without this patch, a device driver should release the > policy and the policy should be aligned with the driver, which would > be cumbersome (sometimes painful) in a cloud environment. My use case > with mdev is to enable a subset of vfio-pci features without losing my > device driver. Does this last comment suggest the parent device is not being multiplexed through mdev, but only mediated? If so, would something like Yan's vendor-ops approach[1] be better? Without a multiplexed device, the lifecycle management of an mdev device doesn't make a lot of sense, and I wonder if that's what you're trying to bypass here. Even SR-IOV devices have moved to userspace enablement with most module options to enable a default number of VFs being deprecated. I do see that that transition left a gap, but I'm not sure that heading in the opposite direction with mdevs is a good idea either. Thanks, Alex [1]https://lore.kernel.org/kvm/20200131020803.27519-1-yan.y.zhao@intel.com/ > > > Signed-off-by: Yonghyun Hwang > > > --- > > > drivers/vfio/mdev/mdev_core.c | 45 +++++++++++++++++++++++++++++++++++ > > > include/linux/mdev.h | 3 +++ > > > 2 files changed, 48 insertions(+) > > > > > > diff --git a/drivers/vfio/mdev/mdev_core.c b/drivers/vfio/mdev/mdev_core.c > > > index b558d4cfd082..a6d32516de42 100644 > > > --- a/drivers/vfio/mdev/mdev_core.c > > > +++ b/drivers/vfio/mdev/mdev_core.c > > > @@ -350,6 +350,51 @@ int mdev_device_create(struct kobject *kobj, > > > return ret; > > > } > > > > > > +/* > > > + * mdev_create_device : Create a mdev device > > > + * @dev: device structure representing parent device. > > > + * @uuid: uuid char string for a mdev device. > > > + * @group: index to supported type groups for a mdev device. > > > + * > > > + * Create a mdev device in kernel. > > > + * Returns a negative value on error, otherwise 0. > > > + */ > > > +int mdev_create_device(struct device *dev, > > > + const char *uuid, int group) > > > +{ > > > + struct mdev_parent *parent = NULL; > > > + struct mdev_type *type = NULL; > > > + guid_t guid; > > > + int i = 1; > > > + int ret; > > > + > > > + ret = guid_parse(uuid, &guid); > > > + if (ret) { > > > + dev_err(dev, "Failed to parse UUID"); > > > + return ret; > > > + } > > > + > > > + parent = __find_parent_device(dev); > > > + if (!parent) { > > > + dev_err(dev, "Failed to find parent mdev device"); > > > + return -ENODEV; > > > + } > > > + > > > + list_for_each_entry(type, &parent->type_list, next) { > > > + if (i == group) > > > + break; > > > + i++; > > > + } > > > + > > > + if (!type || i != group) { > > > + dev_err(dev, "Failed to find mdev device"); > > > + return -ENODEV; > > > + } > > > + > > > + return mdev_device_create(&type->kobj, parent->dev, &guid); > > > +} > > > +EXPORT_SYMBOL(mdev_create_device); > > > + > > > int mdev_device_remove(struct device *dev) > > > { > > > struct mdev_device *mdev, *tmp; > > > diff --git a/include/linux/mdev.h b/include/linux/mdev.h > > > index 0ce30ca78db0..b66f67998916 100644 > > > --- a/include/linux/mdev.h > > > +++ b/include/linux/mdev.h > > > @@ -145,4 +145,7 @@ struct device *mdev_parent_dev(struct mdev_device *mdev); > > > struct device *mdev_dev(struct mdev_device *mdev); > > > struct mdev_device *mdev_from_dev(struct device *dev); > > > > > > +extern int mdev_create_device(struct device *dev, > > > + const char *uuid, int group_idx); > > > + > > > #endif /* MDEV_H */ > > >