From: Greg KH <gregkh@linuxfoundation.org>
To: Nipun Gupta <nipun.gupta@amd.com>
Cc: alex.williamson@redhat.com, jgg@ziepe.ca,
linux-kernel@vger.kernel.org, git@amd.com,
harpreet.anand@amd.com, pieter.jansen-van-vuuren@amd.com,
nikhil.agarwal@amd.com, michal.simek@amd.com
Subject: Re: [RESEND PATCH] cdx: fix driver managed dma support
Date: Mon, 5 Jun 2023 17:22:52 +0200 [thread overview]
Message-ID: <2023060533-reseal-glider-11e7@gregkh> (raw)
In-Reply-To: <20230605131009.6869-1-nipun.gupta@amd.com>
On Mon, Jun 05, 2023 at 06:40:09PM +0530, Nipun Gupta wrote:
> The devices on cdx could be bound to drivers with the device
> DMA managed by kernel drivers or user-space applications.
> As multiple devices can be placed in the same IOMMU group, the
> DMA on these devices must either be entirely under kernel control
> or userspace control. Fix the CDX bus driver to acknowlege the
> driver_managed_dma flag and call the appropriate iommu APIs.
>
> Fixes: 2959ab247061 ("cdx: add the cdx bus driver")
> Signed-off-by: Nipun Gupta <nipun.gupta@amd.com>
> Reported-by: Alex Williamson <alex.williamson@redhat.com>
> Closes: https://lore.kernel.org/lkml/20230524134831.28dc97e2.alex.williamson@redhat.com/
> ---
>
> I have resend this patch to include fixes, closes and
> reported by tags. We request that this fix be incorporated
> into the 6.4 release, along with the inclusion of CDX bus
> driver support.
What do you mean by "inclusion of CDX bus driver support"? What patches
exactly?
confused,
greg k-h
next prev parent reply other threads:[~2023-06-05 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-05 13:10 Nipun Gupta
2023-06-05 15:22 ` Greg KH [this message]
2023-06-05 15:29 ` Nipun Gupta
2023-06-08 4:37 ` Agarwal, Nikhil
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=2023060533-reseal-glider-11e7@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=alex.williamson@redhat.com \
--cc=git@amd.com \
--cc=harpreet.anand@amd.com \
--cc=jgg@ziepe.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.simek@amd.com \
--cc=nikhil.agarwal@amd.com \
--cc=nipun.gupta@amd.com \
--cc=pieter.jansen-van-vuuren@amd.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
all inboxes | Powered by JetHome®