From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Cc: Chenbo Xia <chenbox@nvidia.com>,
Nipun Gupta <nipun.gupta@amd.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Tyler Retzlaff <roretzla@linux.microsoft.com>
Subject: Re: [RFC] eal: remove support for I/O port
Date: Tue, 8 Apr 2025 12:04:17 -0700 [thread overview]
Message-ID: <20250408120417.3e7c5236@hermes.local> (raw)
In-Reply-To: <20250408183032.86167-1-stephen@networkplumber.org>
On Tue, 8 Apr 2025 11:30:32 -0700
Stephen Hemminger <stephen@networkplumber.org> wrote:
> In early days of virtio, the x86 I/O instructions were used
> to ring the doorbell for host access. To support these DPDK
> needed to enable IO access. This is no longer necessary and
> the vestiage can be marked deprecated.
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
Not yet, FreeBSD still uses it and the virtio support still needs it.
Really needs to go since many kernels fully block userspace to I/O
because it allows unrestricted access to hardware.
prev parent reply other threads:[~2025-04-08 19:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 18:30 [RFC] eal: remove support for I/O port Stephen Hemminger
2025-04-08 19:04 ` Stephen Hemminger [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=20250408120417.3e7c5236@hermes.local \
--to=stephen@networkplumber.org \
--cc=chenbox@nvidia.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nipun.gupta@amd.com \
--cc=roretzla@linux.microsoft.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.