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 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E80CAC433F5 for ; Wed, 27 Oct 2021 18:45:28 +0000 (UTC) Received: from smtp1.osuosl.org (smtp1.osuosl.org [140.211.166.138]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 93B2560E76 for ; Wed, 27 Oct 2021 18:45:28 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 93B2560E76 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=redhat.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.linux-foundation.org Received: from localhost (localhost [127.0.0.1]) by smtp1.osuosl.org (Postfix) with ESMTP id 5E27981D70; Wed, 27 Oct 2021 18:45:28 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from smtp1.osuosl.org ([127.0.0.1]) by localhost (smtp1.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QD9tNLdiBTi9; Wed, 27 Oct 2021 18:45:27 +0000 (UTC) Received: from lists.linuxfoundation.org (lf-lists.osuosl.org [IPv6:2605:bc80:3010:104::8cd3:938]) by smtp1.osuosl.org (Postfix) with ESMTPS id EE49B81C56; Wed, 27 Oct 2021 18:45:26 +0000 (UTC) Received: from lf-lists.osuosl.org (localhost [127.0.0.1]) by lists.linuxfoundation.org (Postfix) with ESMTP id B0F35C0019; Wed, 27 Oct 2021 18:45:26 +0000 (UTC) Received: from smtp2.osuosl.org (smtp2.osuosl.org [IPv6:2605:bc80:3010::133]) by lists.linuxfoundation.org (Postfix) with ESMTP id D8963C000E for ; Wed, 27 Oct 2021 18:45:25 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by smtp2.osuosl.org (Postfix) with ESMTP id BFEA9402D2 for ; Wed, 27 Oct 2021 18:45:25 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Authentication-Results: smtp2.osuosl.org (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com Received: from smtp2.osuosl.org ([127.0.0.1]) by localhost (smtp2.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BogrcFUUU97P for ; Wed, 27 Oct 2021 18:45:24 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by smtp2.osuosl.org (Postfix) with ESMTPS id 5A9E1400F6 for ; Wed, 27 Oct 2021 18:45:24 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1635360323; 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: in-reply-to:in-reply-to:references:references; bh=AE8uUoA0RuM1LER5viKtBIKx5xuRVYpElfenEqY9TLo=; b=N3yd9lhiZ30gGFRKDs+G6CaeFbQMliRpO5zyH2bqA7Eyg4D6uc71g+fYI8EgfLwbRc0Nag FhpAjTslhIJdF5D/1naXm8zEelAGSEIgTtM2TX57sT9a+7rBcRDj/aLa94IQJPh8WfGYdb 0TBlon4EVMw+UR4+dEycszRzvGWfsJA= Received: from mail-ed1-f72.google.com (mail-ed1-f72.google.com [209.85.208.72]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-370-EGwYYQPqNpGLQAyExBtcWw-1; Wed, 27 Oct 2021 14:45:21 -0400 X-MC-Unique: EGwYYQPqNpGLQAyExBtcWw-1 Received: by mail-ed1-f72.google.com with SMTP id v9-20020a50d849000000b003dcb31eabaaso3187862edj.13 for ; Wed, 27 Oct 2021 11:45:21 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=AE8uUoA0RuM1LER5viKtBIKx5xuRVYpElfenEqY9TLo=; b=u5wjX/pL2w2cmeOD9B0f4NG0Gh9G14/DtSNeo+sLd2kfKnkRCt7WCAd/q/W6S3Pgxt qS2WTkc6Iod9mZjue2oXoY8op9sFaZBn8dpMtjWRgyEqVs0n2ODSKZVWLJk6zJEibjri B0Yia2XdUFmOC702k1xDf+uypB4pQy5dAlAp/dpV76IgDHiBDbHiROdiP4OsMW9lO+0D 4btftOWb63oXG8+NzZkgKOaV9bhfv519TdYvhLQfu4zi3M3SdcHdTGM2mDTaS0WYQWeB u2WelOGEQMLX4nWI7uZ17e7n4DzzZzFzeOwajwCCShG3REsScJGGn764tx7DSBqljob0 HcSA== X-Gm-Message-State: AOAM532yaf6ESVyLeIw+CRqFUyne14WY7HfJ58WBV5GDPSBf+uIu/BbA MNQDkqG/SPyRZngKYQoWEuFhoda35WTZnJL0AdbYSAEJrfeK+0PBbtizzvfiF9rfwzgprIeZV1T FM5c5JhbnTfM9gR5EpP1rM8ia7Mgzi6hLgxtGe2zjHA== X-Received: by 2002:a05:6402:10cd:: with SMTP id p13mr40854895edu.111.1635360320350; Wed, 27 Oct 2021 11:45:20 -0700 (PDT) X-Google-Smtp-Source: ABdhPJws8TIqKC4ABBb80IsEuESM2Uk5/cMArq6m4yV4675OMckUCxWdSKHAmukoJVCJYGUu14s3xw== X-Received: by 2002:a05:6402:10cd:: with SMTP id p13mr40854878edu.111.1635360320163; Wed, 27 Oct 2021 11:45:20 -0700 (PDT) Received: from redhat.com ([2.55.137.59]) by smtp.gmail.com with ESMTPSA id hc10sm359034ejc.93.2021.10.27.11.45.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Oct 2021 11:45:18 -0700 (PDT) Date: Wed, 27 Oct 2021 14:45:15 -0400 From: "Michael S. Tsirkin" To: Stefano Garzarella Subject: Re: vDPA bus driver selection Message-ID: <20211027144048-mutt-send-email-mst@kernel.org> References: MIME-Version: 1.0 In-Reply-To: Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mst@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Disposition: inline Cc: Eli Cohen , Linux Virtualization X-BeenThere: virtualization@lists.linux-foundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Linux virtualization List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: virtualization-bounces@lists.linux-foundation.org Sender: "Virtualization" On Wed, Oct 27, 2021 at 04:33:50PM +0200, Stefano Garzarella wrote: > Hi folks, > I was trying to understand if we have a way to specify which vDPA bus > driver (e.g. vhost-vdpa, virtio-vdpa) a device should use. > IIUC we don't have it, and the first registered driver is used when a > new device is registered. > > I was thinking if it makes sense to extend the management API to > specify which bus driver to use for a device. A use case could be for > example a single host handling VMs and bare-metal containers, so we > would have both virtio-vdpa and vhost-vdpa loaded and we want to > attach some devices to VMs through vhost-vdpa and others to containers > through virtio-vdpa. > > What do you think? > > I can prepare an RFC with some code, the idea is to use the .match > callback of "struct bus_type" to use a driver instead of the other, > and extend netlink API to specify the vDPA bus driver name to use. > > Thanks, > Stefano So I think that doing this at create time is somewhat limited. For example a great way to do migration could be to unbind device from VM then bind virtio on the host to it, then bind macvtap to that. Ideas on how to allow that? -- MST _______________________________________________ Virtualization mailing list Virtualization@lists.linux-foundation.org https://lists.linuxfoundation.org/mailman/listinfo/virtualization