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 52EB7C77B75 for ; Tue, 18 Apr 2023 11:58:20 +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 632B89F4E7 for ; Tue, 18 Apr 2023 11:58:19 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 461CC9863FB for ; Tue, 18 Apr 2023 11:58:19 +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 346F6984043; Tue, 18 Apr 2023 11:58:19 +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 219AA9863E7 for ; Tue, 18 Apr 2023 11:58:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: skd2f9FSPdiWjLmqbgq3Wg-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681819096; x=1684411096; h=in-reply-to:content-transfer-encoding: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=8TtIpQFmh6KEPWQeNckjC4fUVrBL7e4REAHDp201IZg=; b=b+tSP/LF9qLhnnEowrNmTTB7ZGl107WFQ6yP1DFJ9rnOMl7p/RhfMgEFTlFtrUL2cg P1Vmuob+au9nN5J9pm+Rn5mB5SnTQeXfufix8+UbjoJ70QPjgyDwDrWdnMIejmBkcTER BHafOCMt24aynkZnt6VgnJh7/x+mZs7MSzssJXNfLV5+EeMNmer0pcn++JeB2Msc/lKS 7EhOgVN0rKktz4YmA8tK6fM5nMAeHwfgl5EYkDQv4poBxsnTzoIQSKg8d7bboLFLHnR4 7zknifftoCvwyWZo83ITj2dndkWoifcpnf1sa1u7jcC19t95FlEkpPUECnoFQ2oZ98Gh m7dQ== X-Gm-Message-State: AAQBX9ebYoEv1D+da9XCGhp7no3fj3s4Oo7z58la7GIUMdDXSAR0o0XQ 2uPyrGoj37VbhFHGYEPIKufM6z/s0fcvAoU8XxIBELNgOrSxNYxy/jAnfhZZbU40I33U/z+RMsR 4MG6AJTm66YR9h612R5r75n22zp91 X-Received: by 2002:a05:6000:1107:b0:2e5:56f8:61fc with SMTP id z7-20020a056000110700b002e556f861fcmr1682425wrw.15.1681819095837; Tue, 18 Apr 2023 04:58:15 -0700 (PDT) X-Google-Smtp-Source: AKy350a8+tHP80PH4qz20BxxCUu37KHorM8hFjrlBdOczuc8uIH61ZhkuIIblAgW5F+IyMiC+E2CHg== X-Received: by 2002:a05:6000:1107:b0:2e5:56f8:61fc with SMTP id z7-20020a056000110700b002e556f861fcmr1682411wrw.15.1681819095572; Tue, 18 Apr 2023 04:58:15 -0700 (PDT) Date: Tue, 18 Apr 2023 07:58:11 -0400 From: "Michael S. Tsirkin" To: Parav Pandit Cc: Jason Wang , "virtio-dev@lists.oasis-open.org" , "cohuck@redhat.com" , "virtio-comment@lists.oasis-open.org" , Shahaf Shuler , Satananda Burla , Maxime Coquelin , Yan Vugenfirer Message-ID: <20230418075401-mutt-send-email-mst@kernel.org> References: <20230417162618-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=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit Subject: [virtio-dev] Re: [virtio-comment] Re: [PATCH 09/11] transport-pci: Describe PCI MMR dev config registers On Tue, Apr 18, 2023 at 01:30:43AM +0000, Parav Pandit wrote: > > > > From: Jason Wang > > Sent: Monday, April 17, 2023 8:37 PM > > > > > > Do you mean say we have three AQs, AQ_1, AQ_2, and AQ_3; > > > > > AQ_1 of the PF used by admin work as SIOV device create, SRIOV > > > > > MSIX > > > > configuration. > > > > > AQ_2 of the PF used for transporting legacy config access of the > > > > > PCI VF > > > > > AQ_3 of the PF for some transport work. > > > > > > > > > > If yes, sounds find to me. > > > > > > > > Latest proposal simply leaves the split between AQs up to the driver. > > > > Seems the most flexible. > > > Yes. It is. Different opcode range and multiple AQs enable to do so. > > > > Right, so it would be some facility that makes the transport commands of > > modern and legacy are mutually exclusive. > > Ok. I didn’t follow the mutual exclusion part. > If a device has exposed legacy interface it will have to transport legacy access via its PF. > Same device can be transitional, and its 1.x interface doesn’t need to through this transport channel of PF, right? I think in any case, using device through two transports at the same time shouldn't be legal. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org