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 AE38EC76196 for ; Tue, 11 Apr 2023 14:10: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 EDE57F92C4 for ; Tue, 11 Apr 2023 14:10: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 C7FDE9863D1 for ; Tue, 11 Apr 2023 14:10: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 B419198636D; Tue, 11 Apr 2023 14:10: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 A212A98636E for ; Tue, 11 Apr 2023 14:10:19 +0000 (UTC) X-Virus-Scanned: amavisd-new at kavi.com X-MC-Unique: pFo-dobANZ6kzBrsRw74yg-1 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681222216; 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=88xsUJ8QEz31IcXN9onNyrzzGzKRGbSzPmZvk6P4I7k=; b=3cyZDxDQDnQgLpPxpUuZ7GnKOciaWaO11K6ezPBWVHX7ZdEJpbtWQk4wdEee9NOsfR 3bPILgQsxgrbuuvorV2xincgnRx1XmUJ0JxuecK3572qkESFwihfzrL3McdRXKn5SRI9 E+s1fi7QLKLeJXrTe74heYkJMhBHCuJyZ9RdutOqSqtwCtBTVbhvlR733B1DK4xuws8c W+TGrqd14btygeJcs6iwq1//Vr6HxuHC1xFrHiYe8pBS0XK8z5Sl28nouUW/YFWXx2BJ c/ciFB9uwhHNBN2nbd6pnafucWV2ylAilKQk0T/2rplg3XXx08CU29vVkOL9Ezox7nSy SjxQ== X-Gm-Message-State: AAQBX9fbnLyR6BEIpG9UIZJhsk9WnBZJII/cl7fsbE3gz+74T8Lv7Pwo RQQ9VdqRsfu1unJYDrDQeVJFBzUfBJ5YxzfyWj54vGz4MwO4oHZTEiz/ci3BgL4gx2t8Btt2fPy grNVaSRrDtsSK/vtDadlj7zQ+DoOmPKgSmtdJ X-Received: by 2002:a1c:f609:0:b0:3ed:316d:668d with SMTP id w9-20020a1cf609000000b003ed316d668dmr9709878wmc.5.1681222216035; Tue, 11 Apr 2023 07:10:16 -0700 (PDT) X-Google-Smtp-Source: AKy350Z9K6gcs2hA/uT2+UrzQZ3vZ0e9kFxw1p4H04dSjmgfCsw4B5qByHjhwSh1oSgk/PanZ9p6Bw== X-Received: by 2002:a1c:f609:0:b0:3ed:316d:668d with SMTP id w9-20020a1cf609000000b003ed316d668dmr9709864wmc.5.1681222215730; Tue, 11 Apr 2023 07:10:15 -0700 (PDT) Date: Tue, 11 Apr 2023 10:10: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 Message-ID: <20230411100914-mutt-send-email-mst@kernel.org> References: <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> <20230411100209-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: [virtio-comment] Re: [virtio-dev] [PATCH 08/11] transport-pci: Introduce virtio extended capability On Tue, Apr 11, 2023 at 02:07:27PM +0000, Parav Pandit wrote: > > > > From: virtio-comment@lists.oasis-open.org > open.org> On Behalf Of Michael S. Tsirkin > > > > > > > > > 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? > > > Existing virtio PCI capabilities which are in the PCI capabilities region in first 256 bytes of the PCI config space. well, of course, my question was for a new, future device, can we put all capabilities in the extended space? will we be able to teach bios to access these? > > > New capabilities like legacy (and pasid) has no backward compat > > > requirement from bios and drivers. > > > so they can start from new. > > > > sure. --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org