From: Christoph Hellwig <hch@infradead.org>
To: Jon Derrick <jonathan.derrick@intel.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Bjorn Helgaas <helgaas@kernel.org>,
Keith Busch <keith.busch@intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCI: vmd: Expose oob management window to users
Date: Tue, 17 Sep 2019 01:04:35 -0700 [thread overview]
Message-ID: <20190917080435.GA5666@infradead.org> (raw)
In-Reply-To: <20190916145128.5243-1-jonathan.derrick@intel.com>
On Mon, Sep 16, 2019 at 08:51:28AM -0600, Jon Derrick wrote:
> Some VMD devices provide a management window within MEMBAR2 that is used
> to communicate out-of-band with child devices. This patch creates a
> binary file for interacting with the interface.
>
> OOB Reads/Writes are bounds-checked by sysfs_fs_bin_{read,write}
I don't think this is a reasonable interface. If the OOB interfae
is useful please provide an actual kernel driver for it.
prev parent reply other threads:[~2019-09-17 8:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-16 14:51 [PATCH] PCI: vmd: Expose oob management window to users Jon Derrick
2019-09-17 8:04 ` Christoph Hellwig [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=20190917080435.GA5666@infradead.org \
--to=hch@infradead.org \
--cc=helgaas@kernel.org \
--cc=jonathan.derrick@intel.com \
--cc=keith.busch@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.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 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).