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 8C186C77B61 for ; Sun, 16 Apr 2023 20:44:34 +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 A71B52B054 for ; Sun, 16 Apr 2023 20:44:33 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id 8020D9863BA for ; Sun, 16 Apr 2023 20:44:33 +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 69F16986288; Sun, 16 Apr 2023 20:44:33 +0000 (UTC) Mailing-List: contact virtio-comment-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 51C629862A1 for ; Sun, 16 Apr 2023 20:44:33 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: CZYW-Ei2OfOWwwVUgfdX_w-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1681677870; x=1684269870; 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=BcFEZbNI5d2z3cJh5ThbBpEMo4clcPq77geY9l+6Mpc=; b=GMsSt8HjJXfqfH0xf53Coe4+H8oU19rBhLoYZ0IyUeoZeXfpO1Ckr83juDWxBQDiN2 PH7VDWcTt+8fNYKCcTkF45Ry8Br87YXoPeCQfBgT/SE7XdMUvcuPa4c5zjkhVf+7bbTg tuKZqtr6FGp6itGKyzxk7m2rBAj5cHyooat1dYgqLTskQVSLtGu0IxzSSE+TD2qH9IAI MnP5N2Vvc7jMB7FlKlPIdPGQbUTgWV+Prnr2gAgBe1iLGi/nNZhCtPapcfJ31oM5kf97 etVAa3dgxvns+mJQwJe3M7M9zFchqP73nsjBuph5P6ZkGizbw22RwPC4XQhmtUsGyZk9 frrQ== X-Gm-Message-State: AAQBX9dswS27xiLEAVMcYevbGzTbOp2Kc4+qxumaNhbZg0JSe4Bdc5CX 1ev3N9CSr3vlU03BladzeNXmXyVB1Bm5BHVRLiinaq8gAMrViWivLe/EqgrjXVqJ4Byvna0WtAK cI0WmBWA2MGbIMl0gWa8kvSTZRC0xe3kj4g== X-Received: by 2002:adf:dc91:0:b0:2d9:81b2:322a with SMTP id r17-20020adfdc91000000b002d981b2322amr4023538wrj.55.1681677870138; Sun, 16 Apr 2023 13:44:30 -0700 (PDT) X-Google-Smtp-Source: AKy350bpnxkBwTlSX/jTknjSEm/jhodfMxIAANe8O9aq3p506Ack5mdtkYxkYUZt9w2lW3kwPB8Huw== X-Received: by 2002:adf:dc91:0:b0:2d9:81b2:322a with SMTP id r17-20020adfdc91000000b002d981b2322amr4023523wrj.55.1681677869770; Sun, 16 Apr 2023 13:44:29 -0700 (PDT) Date: Sun, 16 Apr 2023 16:44:25 -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: <20230416163929-mutt-send-email-mst@kernel.org> References: <20230413163216-mutt-send-email-mst@kernel.org> <20230414025523-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: Re: [virtio-comment] Re: [PATCH 09/11] transport-pci: Describe PCI MMR dev config registers On Sun, Apr 16, 2023 at 01:41:55PM +0000, Parav Pandit wrote: > > From: virtio-comment@lists.oasis-open.org > open.org> On Behalf Of Michael S. Tsirkin > > Sent: Friday, April 14, 2023 2:57 AM > > > Do you refer to the trick Jason proposed where BAR0 is memory but otherwise > > matches legacy BAR0 exactly? Is this your preferred solution at this point then? > > We look at it again. > Above solution can work reliably only for a very small number of PF and that too with very special hardware circuitry due to the reset flow. > > Therefore, for virtualization below interface is preferred. > a. For transitional device legacy configuration register transport over AQ, I don't get what this has to do with transitional ... > Notification to utilize transitional device notification area of the BAR. The vq transport does something like this, no? > b. Non legacy interface of transitional and non-transitional PCI device to access direct PCI device without mediation. So VF can either be accessed through AQ of PF, or through direct mapping? -- MST This publicly archived list offers a means to provide input to the OASIS Virtual I/O Device (VIRTIO) TC. In order to verify user consent to the Feedback License terms and to minimize spam in the list archive, subscription is required before posting. Subscribe: virtio-comment-subscribe@lists.oasis-open.org Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org List help: virtio-comment-help@lists.oasis-open.org List archive: https://lists.oasis-open.org/archives/virtio-comment/ Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists Committee: https://www.oasis-open.org/committees/virtio/ Join OASIS: https://www.oasis-open.org/join/