From: Keith Busch <keith.busch@intel.com>
To: Takao Indoh <indou.takao@fujitsu.com>
Cc: "Elliott, Robert (Persistent Memory)" <elliott@hpe.com>,
Takao Indoh <indou.takao@jp.fujitsu.com>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"axboe@fb.com" <axboe@fb.com>, "hch@lst.de" <hch@lst.de>
Subject: Re: [PATCH] nvme: Enable acceleration feature of A64FX processor
Date: Fri, 22 Feb 2019 10:07:15 -0700 [thread overview]
Message-ID: <20190222170715.GA10237@localhost.localdomain> (raw)
In-Reply-To: <20190220094610.GB3559@esprimo>
On Wed, Feb 20, 2019 at 06:46:11PM +0900, Takao Indoh wrote:
> On Thu, Feb 14, 2019 at 08:44:48PM +0000, Elliott, Robert (Persistent Memory) wrote:
> > * how does this interact with an iommu, if there is one? Must the
> > address with bit 56 also be granted permission, or is that
> > stripped off before any iommu comparisons?
>
> The latter. A bit 56 is cleared in Root Port before pass it to iommu.
What if the intendend destination is a peer and never hits the root port?
Really, though, PCI device vendors need to just use the existing
capability as intended and not have arch specific work-arounds. I'm sure
nvme can't be the only device class you'd want this behavior.
next prev parent reply other threads:[~2019-02-22 17:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-01 12:46 [PATCH] nvme: Enable acceleration feature of A64FX processor Takao Indoh
2019-02-01 14:54 ` Keith Busch
2019-02-05 12:56 ` Takao Indoh
2019-02-05 14:39 ` Keith Busch
2019-02-05 16:13 ` Christoph Hellwig
2019-02-13 12:03 ` Takao Indoh
2019-02-14 17:11 ` Christoph Hellwig
2019-02-14 20:44 ` Elliott, Robert (Persistent Memory)
2019-02-14 21:17 ` Keith Busch
2019-02-20 9:46 ` Takao Indoh
2019-02-22 17:07 ` Keith Busch [this message]
2019-02-01 15:51 ` Christoph Hellwig
2019-02-05 12:56 ` Takao Indoh
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=20190222170715.GA10237@localhost.localdomain \
--to=keith.busch@intel.com \
--cc=axboe@fb.com \
--cc=elliott@hpe.com \
--cc=hch@lst.de \
--cc=indou.takao@fujitsu.com \
--cc=indou.takao@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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