All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Vlad Poenaru" <vlad.wing@gmail.com>
Cc: virtualization@lists.linux.dev,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Eugenio Perez" <eperezma@redhat.com>
Subject: Re: [PATCH] virtio_pci: limit Oracle DSC2-200 virtio-net to 48-bit DMA
Date: Mon, 09 Nov 2026 18:48:52 +0000	[thread overview]
Message-ID: <sashiko-outbox-205441@kernel.org> (raw)
In-Reply-To: <20261109184253.531677-1-vlad.wing@gmail.com>

> The virtio-net function of the AMD Pensando DSC2-200 (Elba) DPU, as
> shipped by Oracle (1af4:1041, subsystem 108e:1200), cannot DMA to
> arbitrary 64-bit bus addresses, and Oracle advises limiting it to 48
> bits. virtio_pci gives it a 64-bit mask, so its virtqueues stop
> completing requests once the IOMMU starts handing it IOVAs above 2^48.
> The card is used in OCI bare-metal shapes such as BM.Standard.E6.288.
> 
> On those AMD EPYC 9005 hosts the AMD IOMMU supports a 6-level v1 page
> table (EFR[HATS] = 2), so the aperture spans all 64 bits and the IOVA
> allocator, which works down from min(mask, aperture), returns addresses
> just below 2^64:
> 
>  - With iommu.forcedac=1, the first control virtqueue command never
>    completes and virtio_net hangs in probe.
> 
> [ ... ]
> 
> Cc: stable@vger.kernel.org # 6.5+
> Co-developed-by: Kyle McMartin <jkkm@meta.com>
> Signed-off-by: Kyle McMartin <jkkm@meta.com>
> Signed-off-by: Vlad Poenaru <vlad.wing@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109184253.531677-1-vlad.wing@gmail.com?part=1


      reply	other threads:[~2026-11-09 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-09 18:42 [PATCH] virtio_pci: limit Oracle DSC2-200 virtio-net to 48-bit DMA Vlad Poenaru
2026-11-09 18:48 ` sashiko-bot [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=sashiko-outbox-205441@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=eperezma@redhat.com \
    --cc=mst@redhat.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=virtualization@lists.linux.dev \
    --cc=vlad.wing@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.