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 7D527C76196 for ; Tue, 11 Apr 2023 14:02:56 +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 EE84A6E6C8 for ; Tue, 11 Apr 2023 14:02:55 +0000 (UTC) Received: from lists.oasis-open.org (oasis-open.org [10.110.1.242]) by lists.oasis-open.org (Postfix) with ESMTP id E7E0F9864B3 for ; Tue, 11 Apr 2023 14:02:55 +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 DD0FC98636D; Tue, 11 Apr 2023 14:02:55 +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 CE07C98636E for ; Tue, 11 Apr 2023 14:02:55 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: 3GhZ9HQcOCmWFC8E3Rtlyg-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681221764; 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=I3wLHsbk7eNcdHKUta6QZ4bpEaniepj0YvQG5BcB9dM=; b=0vXH176ZiQhW45k7nfypgd3hPFBidz62/AFeXgBM8RGPb+iDYyHhJ3cdIracymRvS+ maJv9xTGFxikhIpBFbEfY4oF8bnPSU1Vcqj1YhtPvMkfXLSGSXyNdOFXa8UHA7L/cgNj 6kFEH3nXafbhCegf7WCSIK2+5TaxDVuq2tgTQymU36pPzVL4Ko24i2MM0bE6Y+M+o5ib rjlRAwXp0EwKTOKOvLS/ozLRK079CejgRAv4+bODWeQ9Q5MSTUyjvoAP9h0mkLUy+vz/ DFIltS6Gf9Wf+QXDQi5to2DbJ96WHu0hA+hb3O/+B2PFFv1MrAlZ4BoUAs8+4/XD7nb1 yE2Q== X-Gm-Message-State: AAQBX9cHosZaHeMyzIlOwyf8Ztb8bnAReUiu6pqLq0ma+OFd5EdrIoXW KuC8FLVH8FEnOxsL2b69SqWVdpdoHBPzk9cNY0XSELfMse+OQzobLRTRGmVLMz6mN2VKr4NAhoa jSx6+VRV3AOC58pW1PJkuSCK3yz9V X-Received: by 2002:a1c:f716:0:b0:3ef:4138:9eef with SMTP id v22-20020a1cf716000000b003ef41389eefmr10379249wmh.36.1681221763905; Tue, 11 Apr 2023 07:02:43 -0700 (PDT) X-Google-Smtp-Source: AKy350bQrouy29peDWKPL30kJDLR+yIjWgUmYEfX6O9Yn6PRnXsG7QHaGl8avM4vxGN2zVB3OXEjvA== X-Received: by 2002:a1c:f716:0:b0:3ef:4138:9eef with SMTP id v22-20020a1cf716000000b003ef41389eefmr10379220wmh.36.1681221763560; Tue, 11 Apr 2023 07:02:43 -0700 (PDT) Date: Tue, 11 Apr 2023 10:02:39 -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, shahafs@nvidia.com, Satananda Burla Message-ID: <20230411100209-mutt-send-email-mst@kernel.org> References: <20230330225834.506969-1-parav@nvidia.com> <20230330225834.506969-9-parav@nvidia.com> <20230410021619-mutt-send-email-mst@kernel.org> <20230410055947-mutt-send-email-mst@kernel.org> <20230411025646-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-dev] [PATCH 08/11] transport-pci: Introduce virtio extended capability On Tue, Apr 11, 2023 at 09:47:50AM -0400, Parav Pandit wrote: > > > On 4/11/2023 3:00 AM, Michael S. Tsirkin wrote: > > > > I meant, it depends on the capability semantics. Both PASID and legacy > > > MMIO don't need to be accessed by BIOS. We can't change legacy BIOS to > > > use legacy MMIO bars. > > > > > > Thanks > > > > makes sense. > > > > > > now, imagine someone building a new device. if existing drivers are not > > a concern, it is possible to move capabilities all to extended space. is > > that possible while keeping the bios working? > > > unlikely as bios is looking in the legacy section. what do you mean by the legacy section? > New capabilities like legacy (and pasid) has no backward compat requirement > from bios and drivers. > so they can start from new. sure. -- MST --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org