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 ws5-mx01.kavi.com (ws5-mx01.kavi.com [34.193.7.191]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 4A2C6C77B7A for ; Tue, 16 May 2023 20:48:00 +0000 (UTC) Received: from lists.oasis-open.org (oasis.ws5.connectedcommunity.org [10.110.1.242]) by ws5-mx01.kavi.com (Postfix) with ESMTP id 8B0E4120D71 for ; Tue, 16 May 2023 20:47:59 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 7C1519862FB for ; Tue, 16 May 2023 20:47:59 +0000 (UTC) Received: from host09.ws5.connectedcommunity.org (host09.ws5.connectedcommunity.org [10.110.1.97]) by lists.oasis-open.org (Postfix) with QMQP id 700B19862F6; Tue, 16 May 2023 20:47:59 +0000 (UTC) Mailing-List: contact virtio-dev-help@lists.oasis-open.org; run by ezmlm List-ID: Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 5F7769862F7 for ; Tue, 16 May 2023 20:47:59 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: m9xw5M7mMAajvAIMDvHoFw-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684270073; x=1686862073; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=8gk4pvuepe50HPJk/BfB2umcECVMR7WSfmPRQilRy0g=; b=S5bJL+O2z/3+OdQB0/nKXESInl/MdoKLRzogjAwgn8PHwAlMg8mNfogo1aXhAarkKE dnXaJu8xI2sv87MnPvnzurTxlNP9x6c9Iz9+H1WoufBPGyiW6lNZIUt1I3SX1Kfl038N 2tKRsBcwH4XALIF/XgLN/U6FxgDAszPeAZsxsNrR9k3/sS98HsEVCgLC6+2sz2ensprZ +4VDMGvsiVM4X+EJL8bsAI/KNNjjQBaKPknQhLaMeW73bHAPYfXOfrXqdt18Ew+gqtmW Ej4HkmnsTRvSnc+xNha+toz0Df1vgBnWdJq1npjIUgD16vHdbI3ub0gc75j7kekwLt4/ Jkmg== X-Gm-Message-State: AC+VfDxyyHrr7ftABvhY7cQ+lbICiEp05ExWmy4PVyr+NAx9h9SIAHre tLOx/hD7vX1tHROoqPl5Kwta7Quhv86bZRoT1ZRIM5F6BadAv/y9o/OPfxlBwOq3mvzskJ/QqAE iIdVlsZMwW68OFQpmPhMdk2UwIRc+ X-Received: by 2002:a5d:6287:0:b0:309:3573:b659 with SMTP id k7-20020a5d6287000000b003093573b659mr2157325wru.31.1684270073249; Tue, 16 May 2023 13:47:53 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ46cafMdeFj/Q7vOTo7cEAskblKntlqGqcBv3D1zxUilFlwT/T1egG/Z0o0YOtgw9a4946lUg== X-Received: by 2002:a5d:6287:0:b0:309:3573:b659 with SMTP id k7-20020a5d6287000000b003093573b659mr2157312wru.31.1684270072949; Tue, 16 May 2023 13:47:52 -0700 (PDT) Date: Tue, 16 May 2023 16:47:48 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Cornelia Huck , "virtio-comment@lists.oasis-open.org" , "virtio-dev@lists.oasis-open.org" , Shahaf Shuler Message-ID: <20230516164254-mutt-send-email-mst@kernel.org> References: <20230516030139.767838-1-parav@nvidia.com> <20230516013842-mutt-send-email-mst@kernel.org> <87lehohefn.fsf@redhat.com> <20230516054313-mutt-send-email-mst@kernel.org> MIME-Version: 1.0 In-Reply-To: X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [virtio-dev] Re: [PATCH] content: Replace guest OS with driver On Tue, May 16, 2023 at 07:50:48PM +0000, Parav Pandit wrote: > > > From: Michael S. Tsirkin > > Sent: Tuesday, May 16, 2023 6:05 AM > > > > > SO I propose: > > > > \item[ACKNOWLEDGE (1)] Indicates that a transport driver has found the > > device and recognized it as a valid virtio device transport. > > > > \item[DRIVER (2)] Indicates that a device type specific driver was found > > and will attempt to attach to the device. > > > Above bisection is a implementation specific example of Linux (though valid and widely used one). > > The UEFI virtio driver doesn't even have such two drivers. > In some OS variant drivers are merged to single kernel binary. which one? > Does driver only matter with device_driver structure or module binary?... Can't parse your question. > Driver is largely the software entity that drives the device. > I think we can keep the spec simple enough to not mix these details and just call it a "driver". Not just linux there are lots of drivers like this. the two bits pass useful information the way you changed it this distinction is lots. I agree it is worth thinking what exactly does it mean. Since you researched it - what exactly do drivers such as uefi and the unnamed "some OS variant" do exactly? when do they set ACKNOWLEDGE and when DRIVER? > > > > BTW somewhat related, I would maybe fix > > device-types/mem/description.tex:change > > not to say "device driver", just "driver" for brevity. > > > Ok. will fix. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org