From: Robin Voetter <robin@streamhpc.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: PCIe atomics in pcie-root-port
Date: Wed, 12 Apr 2023 18:58:50 +0200 [thread overview]
Message-ID: <74c117e4-5a2a-2759-1dfe-5dc63b53eb75@streamhpc.com> (raw)
In-Reply-To: <20230406124009.4a5e7307.alex.williamson@redhat.com>
On 4/6/23 20:40, Alex Williamson wrote:
> I think the typical approach for QEMU would be expose options in the
> downstream ports that would then need to be enabled by the user or
> management tool, but that's where the complication begins. At some
> point we would want management tools to "do the right thing"
> themselves. Is support for PCIe atomics pervasive enough to default to
> enabling support?
Apparently this is supported from Haswell or newer on Intel, and
Ryzen/Threadripper/Epyc on AMD hardware. I don't have any official data
for this, though.
> How do we handle hotplugged endpoints where the
> interconnects do not expose atomics support, or perhaps when they
> expose support that doesn't exist? At some point in the future when we
> have migration of devices with atomics, do we need to test all endpoint
> to endpoint paths for equivalent atomic support on the migration target?
> Are there capabilities on the endpoint that we can virtualize to
> disable use of atomics if the host and guest topologies are out of sync?
It seems automatic detection is a lot of added complication for this
feature. For the time being, I think its best to allow enabling PCIe
atomics using a device property for the pcie-root-port that is disabled
by default. If general hardware support is good enough, it can be
enabled by default. Compatibility with older QEMU versions can then be
added using a newer hw compat in hw/core/machine.c.
Kind regards,
Robin
prev parent reply other threads:[~2023-04-12 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 9:29 PCIe atomics in pcie-root-port Robin Voetter
2023-04-06 18:40 ` Alex Williamson
2023-04-12 16:58 ` Robin Voetter [this message]
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=74c117e4-5a2a-2759-1dfe-5dc63b53eb75@streamhpc.com \
--to=robin@streamhpc.com \
--cc=alex.williamson@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).