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 277F7EB64D9 for ; Thu, 6 Jul 2023 20:41:45 +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 81FA07C671 for ; Thu, 6 Jul 2023 20:41:44 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 7934198680E for ; Thu, 6 Jul 2023 20:41:44 +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 6CBF6983B4A; Thu, 6 Jul 2023 20:41:44 +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 582389867F9 for ; Thu, 6 Jul 2023 20:41:39 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: oy404yiPN2y8xfmUfBsFxw-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1688676096; x=1691268096; 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=iQikHK+IFeXIsrbraOGWzP8vUTFAZoeDUY5hVGdMu/k=; b=IUW+ZNkUsE/vChxYlq5zhAB0D9DbZYoyAigSAmiD1BPhETBULoSbYHot/iwYzYH9+N sSdYg6RT7+oGM+XNbK1uzmvVixDG5OEihJUWmOwzBrTGhmBxGshdUUzTv1eH/Mtl8Xnm 7oDDrrau3DF/DD7OLnKnjo2G67MlBthzEpzYvFNH2V5cUdRGJD5MZLif79+AhEZr6YCc mfkORj5C2tNA6TCZL0t8+ttVbc/qOcMiJw3AIdgESX7NLgQFRicnNNOrL2HUeXRdhjiB HuJPDUrop9u27yC3GsSyGTAwCIlcVqwhmHPhRhn7FequeMdGzOCZXQTGQEJB70BOK6Sl gHHw== X-Gm-Message-State: ABy/qLaFDemqryEAxQu9LH/SbRsrfFY1SdQ1tlDOHrNL8lynwuCYY/Tl o+59WXrQR1k4ViULGrQlLo3k3BnmsCYrsU/BRZpyctpo+jrqePuJxLynmJQnolVs7gZCo25xfaQ kRfu63BaEmxLl9d6UKcG4sQMgG/Cn X-Received: by 2002:a7b:cbd9:0:b0:3fb:ac7b:4930 with SMTP id n25-20020a7bcbd9000000b003fbac7b4930mr2215190wmi.3.1688676096193; Thu, 06 Jul 2023 13:41:36 -0700 (PDT) X-Google-Smtp-Source: APBJJlEvUIgIXQjqu8mftYnGGBmLrOVTeIaT3mfAdH62qazyJC2oM5e863SrqfgRWdPZNM6Izk0j9w== X-Received: by 2002:a7b:cbd9:0:b0:3fb:ac7b:4930 with SMTP id n25-20020a7bcbd9000000b003fbac7b4930mr2215183wmi.3.1688676095911; Thu, 06 Jul 2023 13:41:35 -0700 (PDT) Date: Thu, 6 Jul 2023 16:41:31 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Cornelia Huck , "virtio-comment@lists.oasis-open.org" , "david.edmondson@oracle.com" , "virtio-dev@lists.oasis-open.org" , "sburla@marvell.com" , "jasowang@redhat.com" , Yishai Hadas , Maor Gottlieb , Shahaf Shuler Message-ID: <20230706164028-mutt-send-email-mst@kernel.org> References: <20230706135858-mutt-send-email-mst@kernel.org> <20230706144427-mutt-send-email-mst@kernel.org> <20230706145538-mutt-send-email-mst@kernel.org> <20230706154002-mutt-send-email-mst@kernel.org> <20230706162505-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 v10 4/4] transport-pci: Introduce group legacy group member config region access On Thu, Jul 06, 2023 at 08:35:37PM +0000, Parav Pandit wrote: > > > From: Michael S. Tsirkin > > Sent: Thursday, July 6, 2023 4:29 PM > > > > The driver has a final decision. Let's make it a SHOULD and then if driver knows > > best then it has the choice? > > > > As you said, the driver has the final say. > There is really no reason to complicate the spec for a narrow case where device cannot judge. > > > > > > > But I don't see any configs where leaving this to the driver's > > > > discretion is preferable. If you see one let me know. > > > > > > In doesn't need to be config. > > > It is the environment that chooses which is preferred by the driver. > > > For example preference of accessibility over ordering. > > > > > > what does accessibility mean exactly? I definitely see OSes where owner driver > > can't access a member. > Accessibility = access a member > > > So in that case naturally driver will skip the entry for member even if it's first. > > maybe there are configs where member access is possible but is very slow e.g. > > with lots of indirect function calls? > > OK fine, but then it will be up to the driver to test and make damn sure the > > benefits outweight the costs. > > > > IOW it's a hint for the driver. If you like you can say it explicitly even. > > > Device doesnt know anything about those indirect function calls, so device cannot hint about driver environment. > > Can we please avoid this over engineering? > Interface has the doors open for driver to make wise decision depending on its environment. what if driver can access both with the same ease? this is the case that bothers me and I think it's practical since it will be common on linux. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org