public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Leif Lindholm" <leif@nuviainc.com>
To: Laszlo Ersek <lersek@redhat.com>
Cc: devel@edk2.groups.io, Jordan Justen <jordan.l.justen@intel.com>,
	Ard Biesheuvel <ard.biesheuvel@arm.com>
Subject: Re: [PATCH 1/1] OvmfPkg: drop redundant VendorID check in VirtioMmioDeviceLib
Date: Thu, 17 Sep 2020 13:03:36 +0100	[thread overview]
Message-ID: <20200917120336.GS5623@vanye> (raw)
In-Reply-To: <d048b6ff-06ba-2f38-9e60-e124fd0e12be@redhat.com>

On Mon, Sep 14, 2020 at 17:35:13 +0200, Laszlo Ersek wrote:
> Hi Leif,
> 
> On 09/12/20 18:40, Leif Lindholm wrote:
> > There is a DEBUG warning printout in VirtioMmioDeviceLib if the current
> > device's VendorID does not match the traditional 16-bit Red Hat PCIe
> > vendor ID used with virtio-pci. The virtio-mmio vendor ID is 32-bit and
> > has no connection to the PCIe registry.
> > 
> > Most specifically, this causes a bunch of noise when booting an AArch64
> > QEMU platform, since QEMU's virtio-mmio implementation used 'QEMU' as
> > the vendor ID:
> > VirtioMmioInit: Warning:
> >   The VendorId (0x554D4551) does not match the VirtIo VendorId (0x1AF4).
> 
> Good catch -- in QEMU, this has been the case since initial virtio-mmio
> commit 4b52530be987 ("virtio: Implement MMIO based virtio transport",
> 2013-07-19); and indeed neither the virtio-0.9.5 spec, nor the "Legacy
> MMIO" part of the 1.0 spec, require this vendor ID to be 0x1AF4.
> 
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>

Thanks!
Merged as 5648836987ca / #935.

> Thanks
> Laszlo
> 
> > 
> > Drop the warning message.
> > 
> > Cc: Jordan Justen <jordan.l.justen@intel.com>
> > Cc: Laszlo Ersek <lersek@redhat.com>
> > Cc: Ard Biesheuvel <ard.biesheuvel@arm.com>
> > Signed-off-by: Leif Lindholm <leif@nuviainc.com>
> > ---
> >  .../VirtioMmioDeviceLib/VirtioMmioDevice.c        | 15 ---------------
> >  1 file changed, 15 deletions(-)
> > 
> > diff --git a/OvmfPkg/Library/VirtioMmioDeviceLib/VirtioMmioDevice.c b/OvmfPkg/Library/VirtioMmioDeviceLib/VirtioMmioDevice.c
> > index 2f20272c1445..6dbbba008c75 100644
> > --- a/OvmfPkg/Library/VirtioMmioDeviceLib/VirtioMmioDevice.c
> > +++ b/OvmfPkg/Library/VirtioMmioDeviceLib/VirtioMmioDevice.c
> > @@ -58,7 +58,6 @@ VirtioMmioInit (
> >    )
> >  {
> >    UINT32     MagicValue;
> > -  UINT32     VendorId;
> >    UINT32     Version;
> >  
> >    //
> > @@ -84,20 +83,6 @@ VirtioMmioInit (
> >      return EFI_UNSUPPORTED;
> >    }
> >  
> > -  //
> > -  // Double-check MMIO-specific values
> > -  //
> > -  VendorId = VIRTIO_CFG_READ (Device, VIRTIO_MMIO_OFFSET_VENDOR_ID);
> > -  if (VendorId != VIRTIO_VENDOR_ID) {
> > -    //
> > -    // The ARM Base and Foundation Models do not report a valid VirtIo VendorId.
> > -    // They return a value of 0x0 for the VendorId.
> > -    //
> > -    DEBUG((DEBUG_WARN, "VirtioMmioInit: Warning: The VendorId (0x%X) does not "
> > -                       "match the VirtIo VendorId (0x%X).\n",
> > -                       VendorId, VIRTIO_VENDOR_ID));
> > -  }
> > -
> >    return EFI_SUCCESS;
> >  }
> >  
> > 
> 

  reply	other threads:[~2020-09-17 12:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-12 16:40 [PATCH 1/1] OvmfPkg: drop redundant VendorID check in VirtioMmioDeviceLib Leif Lindholm
2020-09-14 15:35 ` Laszlo Ersek
2020-09-17 12:03   ` Leif Lindholm [this message]
2020-09-14 18:04 ` [edk2-devel] " Philippe Mathieu-Daudé

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200917120336.GS5623@vanye \
    --to=devel@edk2.groups.io \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox