From: Christoph Hellwig <hch@infradead.org>
To: Sherry Sun <sherry.sun@nxp.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"sudeep.dutt@intel.com" <sudeep.dutt@intel.com>,
"ashutosh.dixit@intel.com" <ashutosh.dixit@intel.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"kishon@ti.com" <kishon@ti.com>,
"lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH V2 3/4] misc: vop: simply return the saved dma address instead of virt_to_phys
Date: Tue, 29 Sep 2020 19:11:56 +0100 [thread overview]
Message-ID: <20200929181156.GA7516@infradead.org> (raw)
In-Reply-To: <VI1PR04MB4960A4E7D6A72C2CDEAC47CE92320@VI1PR04MB4960.eurprd04.prod.outlook.com>
On Tue, Sep 29, 2020 at 01:10:12PM +0000, Sherry Sun wrote:
> > > if (!offset) {
> > > - *pa = virt_to_phys(vpdev->hw_ops->get_dp(vpdev));
> > > + if (vpdev->hw_ops->get_dp_dma)
> > > + *pa = vpdev->hw_ops->get_dp_dma(vpdev);
> > > + else {
> > > + dev_err(vop_dev(vdev), "can't get device page
> > physical address\n");
> > > + return -EINVAL;
> > > + }
> >
> > I don't think we need the NULL check here. Wouldn't it also make sense to
> > return the virtual and DMA address from ->get_dp instead of adding another
> > method?
>
> Do you mean that we should only change the original ->get_dp callback to return virtual
> and DMA address at the same time, instead of adding the ->get_dp_dma callback?
That was my intention when writing it, yes. But it seems like most
other callers don't care. Maybe move the invocation of
dma_mmap_coherent into a new ->mmap helper, that way it seems like
the calling code doesn't need to know about the dma_addr_t at all.
That being said the layering in the code keeps puzzling me. As far as
I can tell only a single instance of struct vop_driver even exists, so
we might be able to kill all the indirections entirely.
next prev parent reply other threads:[~2020-09-29 18:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-29 8:44 [PATCH V2 0/4] Change vring space from nomal memory to dma coherent memory Sherry Sun
2020-09-29 8:44 ` [PATCH V2 1/4] misc: vop: change the way of allocating vring Sherry Sun
2020-09-29 10:23 ` Christoph Hellwig
2020-09-29 13:02 ` Sherry Sun
2020-09-29 8:44 ` [PATCH V2 2/4] misc: vop: do not allocate and reassign the used ring Sherry Sun
2020-09-29 10:24 ` Christoph Hellwig
2020-09-29 13:02 ` Sherry Sun
2020-09-29 14:28 ` David Laight
2020-09-29 8:44 ` [PATCH V2 3/4] misc: vop: simply return the saved dma address instead of virt_to_phys Sherry Sun
2020-09-29 10:26 ` Christoph Hellwig
2020-09-29 13:10 ` Sherry Sun
2020-09-29 18:11 ` Christoph Hellwig [this message]
2020-09-30 7:30 ` Sherry Sun
2020-10-05 13:42 ` Christoph Hellwig
2020-09-29 8:44 ` [PATCH V2 4/4] misc: vop: mapping kernel memory to user space as noncached Sherry Sun
2020-09-29 10:28 ` Christoph Hellwig
2020-09-29 13:12 ` Sherry Sun
2020-09-29 15:39 ` David Laight
2020-10-13 2:02 ` Sherry Sun
2020-10-20 1:33 ` Sherry Sun
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=20200929181156.GA7516@infradead.org \
--to=hch@infradead.org \
--cc=arnd@arndb.de \
--cc=ashutosh.dixit@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=kishon@ti.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=sherry.sun@nxp.com \
--cc=sudeep.dutt@intel.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.