qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
To: "Michael S . Tsirkin" <mst@redhat.com>,
	Marcel Apfelbaum <marcel.apfelbaum@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH v2 1/1] docs: pcie: describe PCIe option ROMs
Date: Sun, 31 Dec 2023 12:56:32 +0100	[thread overview]
Message-ID: <5742f50b-2e32-4541-8d66-70c4966a02bf@canonical.com> (raw)
In-Reply-To: <20220814153220.2439468-1-heinrich.schuchardt@canonical.com>

On 8/14/22 17:32, Heinrich Schuchardt wrote:
> Provide a descriptions of the options that control the emulation of option
> ROMS for PCIe devices.
> 
> Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> ---
> v2:
> 	correct description of rombar property
> 	use romfile= to suppress option ROM loading
> ---
>   docs/pcie.txt | 28 ++++++++++++++++++++++++++++
>   1 file changed, 28 insertions(+)
> 
> diff --git a/docs/pcie.txt b/docs/pcie.txt
> index 89e3502075..b60f189bd4 100644
> --- a/docs/pcie.txt
> +++ b/docs/pcie.txt
> @@ -292,6 +292,34 @@ PCI-PCI Bridge slots can be used for legacy PCI host devices.
>   If you can see the "Express Endpoint" capability in the
>   output, then the device is indeed PCI Express.
>   
> +8. Option ROM
> +=============
> +PCIe devices may provide an option ROM. The following properties control the
> +emulation of the option ROM:
> +
> +``rombar`` (default: ``1``)
> +  For vfio-pci devices a vendor and product ID based denylist exists which
> +  controls if an available option ROM shall be probed. The 'rombar' option
> +  allows to override this setting. The value is used as follows:
> +  0 = skip probing, 1 = force probing
> +
> +``romfile``
> +  Defines the name of the file to be loaded as option ROM.
> +  The file size may neither exceed 2 GiB nor ``romsize``.
> +  Some devices like virtio-net-pci define a default file name.
> +
> +``romsize`` (default: ``-1``)
> +  Specifies the size of the option ROM in bytes. The value must be either
> +  ``-1`` or a power of two. ``-1`` signifies unlimited size.
> +
> +Some QEMU PCIe devices like virtio-net-pci use an option ROM by default. In the
> +following example the option ROM of a virtio-net-pci device is disabled by
> +specifying an empty ``romfile`` property. This is useful for architectures where
> +QEMU does not supply an option ROM file.
> +
> +.. code-block:: console
> +
> +    -device virtio-net-pci,netdev=eth1,mq=on,romfile=
>   
>   7. Virtio devices
>   =================

Hello Michael, hello Marcel,

Unfortunately the patch was never reviewed.

The patch is available at:

https://lore.kernel.org/qemu-devel/20220814153220.2439468-1-heinrich.schuchardt@canonical.com/

https://patchwork.kernel.org/project/qemu-devel/patch/20220814153220.2439468-1-heinrich.schuchardt@canonical.com/
Best regards

Heinrich


  reply	other threads:[~2023-12-31 11:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-14 15:32 [PATCH v2 1/1] docs: pcie: describe PCIe option ROMs Heinrich Schuchardt
2023-12-31 11:56 ` Heinrich Schuchardt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-20 12:27 Ahmad

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-all 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=5742f50b-2e32-4541-8d66-70c4966a02bf@canonical.com \
    --to=heinrich.schuchardt@canonical.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    /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;
as well as URLs for NNTP newsgroup(s).