From: Moritz Fischer <mdf@kernel.org>
To: Dominic Chen <d.c.ddcc@gmail.com>
Cc: hao.wu@intel.com, mdf@kernel.org, linux-fpga@vger.kernel.org
Subject: Re: [PATCH v2] fpga: dfl: afu: support debug access to memory-mapped afu regions
Date: Wed, 4 Mar 2020 19:09:28 -0800 [thread overview]
Message-ID: <20200305030926.GA4253@epycbox.lan> (raw)
In-Reply-To: <20200304133847.103881-1-d.c.ddcc@gmail.com>
On Wed, Mar 04, 2020 at 08:38:47AM -0500, Dominic Chen wrote:
> Allow debug access to memory-mapped regions using e.g. gdb.
>
> Signed-off-by: Dominic Chen <d.c.ddcc@gmail.com>
> ---
> drivers/fpga/dfl-afu-main.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/fpga/dfl-afu-main.c b/drivers/fpga/dfl-afu-main.c
> index 02baa6a227c0..ec9dbd3d51b8 100644
> --- a/drivers/fpga/dfl-afu-main.c
> +++ b/drivers/fpga/dfl-afu-main.c
> @@ -459,6 +459,12 @@ static long afu_ioctl(struct file *filp, unsigned int cmd, unsigned long arg)
> return -EINVAL;
> }
>
> +static const struct vm_operations_struct afu_vma_ops = {
> +#ifdef CONFIG_HAVE_IOREMAP_PROT
> + .access = generic_access_phys,
> +#endif /* CONFIG_HAVE_IOREMAP_PROT */
I remember there were issues in the past with modules and this, are
those resolved?
> +};
> +
> static int afu_mmap(struct file *filp, struct vm_area_struct *vma)
> {
> struct platform_device *pdev = filp->private_data;
> @@ -488,6 +494,9 @@ static int afu_mmap(struct file *filp, struct vm_area_struct *vma)
> !(region.flags & DFL_PORT_REGION_WRITE))
> return -EPERM;
>
> + // Support debug access to the mapping
Please use kernel style comments /* */ checkpatch.pl should catch this.
> + vma->vm_ops = &afu_vma_ops;
> +
> vma->vm_page_prot = pgprot_noncached(vma->vm_page_prot);
>
> return remap_pfn_range(vma, vma->vm_start,
> --
> 2.17.1
>
Thanks,
Moritz
next prev parent reply other threads:[~2020-03-05 3:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 13:38 [PATCH v2] fpga: dfl: afu: support debug access to memory-mapped afu regions Dominic Chen
2020-03-05 3:09 ` Moritz Fischer [this message]
2020-03-05 3:32 ` Dominic Chen
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=20200305030926.GA4253@epycbox.lan \
--to=mdf@kernel.org \
--cc=d.c.ddcc@gmail.com \
--cc=hao.wu@intel.com \
--cc=linux-fpga@vger.kernel.org \
/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