From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.groups.io with SMTP id smtpd.web09.3765.1623215170616077126 for ; Tue, 08 Jun 2021 22:06:10 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=VXgVQkWf; spf=pass (domain: redhat.com, ip: 170.10.133.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1623215169; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=R0lBKUUL/03zloQ5CrE7vWPg+ktdgEiOp90hCgicZpg=; b=VXgVQkWfLD7sk3K+Tx5LQsK2zV8A/6CyqcJlxDm/b4gZW2ljQnqwb5PsRywBPKwebVIJ5E ppnpCe4XucgQHUkC3uh++gxkL7fYADUHzPwAg3VZMwcebyHw6IiuxoIbQidMujN70FblSd FcdWC7va47mwSvTo1FlRO5WjV3FFREA= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-234-jeyjk8XUOOaX2eaJ9C2_1g-1; Wed, 09 Jun 2021 01:06:08 -0400 X-MC-Unique: jeyjk8XUOOaX2eaJ9C2_1g-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 5DFF81E1B for ; Wed, 9 Jun 2021 05:06:07 +0000 (UTC) Received: from sirius.home.kraxel.org (ovpn-113-69.ams2.redhat.com [10.36.113.69]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 09A60100238C; Wed, 9 Jun 2021 05:06:04 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id 37F3318003B6; Wed, 9 Jun 2021 07:06:01 +0200 (CEST) From: "Gerd Hoffmann" To: devel@edk2.groups.io Cc: Gerd Hoffmann Subject: [PATCH 0/2] Quo vadis virtio-mmio? Date: Wed, 9 Jun 2021 07:05:59 +0200 Message-Id: <20210609050601.2754389-1-kraxel@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit virtio-mmio support in ovmf seems to be the unloved child. The final virto-1.0 specification was published five(!) years ago, nevertheless the mmio transport doesn't support it yet ... Some people argue that it has been obsoleted by virtio-pci. Which is a valid argument. But IMHO isn't a good reason to just let virtio-mmio bitrot. We should either remove it from the tree, or support it. So, opening the discussion with this little patch series. It does the latter and adds virtio 1.0 support. For the mmio transport the difference between 0.9.5 and 1.0 is rather small (when compared to the pci transport), it is just a bunch of new registers for the changed virtio queue initialization. So the patch series is small too ... take care, Gerd Gerd Hoffmann (2): OvmfPkg/Virtio10: Add virtio-mmio 1.0 defines OvmfPkg/VirtioMmioDeviceLib: Add virtio 1.0 support. OvmfPkg/Include/IndustryStandard/Virtio10.h | 12 +++++++ .../VirtioMmioDeviceLib/VirtioMmioDevice.h | 1 + .../VirtioMmioDeviceLib/VirtioMmioDevice.c | 17 +++++++--- .../VirtioMmioDeviceFunctions.c | 31 +++++++++++++++++-- 4 files changed, 54 insertions(+), 7 deletions(-) -- 2.31.1