From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Alejandro Lucero <alejandro.lucero@netronome.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: eric.zhang@windriver.com, dev <dev@dpdk.org>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Allain Legacy <allain.legacy@windriver.com>,
matt.peters@windriver.com,
Stephen Hemminger <stephen@networkplumber.org>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Shahaf Shuler <shahafs@mellanox.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
David Marchand <david.marchand@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode
Date: Tue, 30 Oct 2018 13:47:55 +0000 [thread overview]
Message-ID: <aafc3c45-d220-c60d-200f-cfc8a18a54ac@intel.com> (raw)
In-Reply-To: <CAD+H9933Y1zyw_e2c+1kJ3_SaDQa+2pvMVw2nKzFaCLY4C5qmg@mail.gmail.com>
On 30-Oct-18 12:02 PM, Alejandro Lucero wrote:
>
>
> On Sun, Oct 28, 2018 at 11:04 PM Thomas Monjalon <thomas@monjalon.net
> <mailto:thomas@monjalon.net>> wrote:
>
> 11/10/2018 12:08, Thomas Monjalon:
> > +Cc more maintainers in order to collect more reviews
> >
> > 04/10/2018 11:19, Burakov, Anatoly:
> > > On 03-Oct-18 9:53 PM, eric zhang wrote:
> > > > This patchset introduces an EAL command line option "--iova-mode"
> > > > to give the user a facility to force IOVA mode to a special
> value.
> > > >
> > > > Auto detection of the IOVA mode, based on probing the bus and
> IOMMU
> > > > configuration, may not report the desired addressing mode
> when virtual
> > > > devices that are not directly attached to the bus are present.
> > > > The EAL command line option "--iova-mode" can be used to
> select either
> > > > physical addressing('pa') or virtual addressing('va').
> > >
> > > Acked-by: Anatoly Burakov <anatoly.burakov@intel.com
> <mailto:anatoly.burakov@intel.com>>
>
> Rebased and applied, thanks
>
>
>
> Could not this lead to a problem if a device can not wok with the mode set?
> For example, IOVA mode set to VA and IOMMU hw with less bits than those
> required for the virtual addresses?
>
> IMO any device should be attached to a bus, and a bus should have a
> function for setting IOVA mode and the --iova-mode option just allowed
> with supported IOVA modes within the bus.
I don't think it should work that way. It should warn the user that an
incompatible IOVA mode was selected, but the user has specified an IOVA
mode for a reason - it probably implies he really means it, so let him :)
--
Thanks,
Anatoly
next prev parent reply other threads:[~2018-10-30 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 20:53 eric zhang
2018-10-03 20:53 ` [dpdk-dev] [PATCH v3 1/3] eal: add eal option to configure iova mode eric zhang
2018-10-03 20:53 ` [dpdk-dev] [PATCH v3 2/3] eal: force IOVA to a particular mode eric zhang
2018-10-03 20:53 ` [dpdk-dev] [PATCH v3 3/3] doc: document --iova-mode EAL option eric zhang
2018-10-18 13:18 ` Kovacevic, Marko
2018-10-04 9:19 ` [dpdk-dev] [PATCH v3 0/3] force IOVA to a particular mode Burakov, Anatoly
2018-10-11 10:08 ` Thomas Monjalon
2018-10-28 23:04 ` Thomas Monjalon
2018-10-30 12:02 ` Alejandro Lucero
2018-10-30 13:47 ` Burakov, Anatoly [this message]
2018-10-30 14:03 ` Alejandro Lucero
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=aafc3c45-d220-c60d-200f-cfc8a18a54ac@intel.com \
--to=anatoly.burakov@intel.com \
--cc=alejandro.lucero@netronome.com \
--cc=allain.legacy@windriver.com \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=eric.zhang@windriver.com \
--cc=ferruh.yigit@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=john.mcnamara@intel.com \
--cc=matt.peters@windriver.com \
--cc=maxime.coquelin@redhat.com \
--cc=shahafs@mellanox.com \
--cc=stephen@networkplumber.org \
--cc=thomas@monjalon.net \
/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).