mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nipun Gupta <nipun.gupta@amd.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: jgg@ziepe.ca, linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
	masahiroy@kernel.org, nathan@kernel.org, ndesaulniers@google.com,
	nicolas@fjasle.eu, git@amd.com, harpreet.anand@amd.com,
	pieter.jansen-van-vuuren@amd.com, nikhil.agarwal@amd.com,
	michal.simek@amd.com
Subject: Re: [PATCH v6] vfio/cdx: add support for CDX bus
Date: Mon, 29 May 2023 13:36:30 +0530	[thread overview]
Message-ID: <1bf0323b-1191-de11-061e-00227e09dc35@amd.com> (raw)
In-Reply-To: <20230524134831.28dc97e2.alex.williamson@redhat.com>



On 5/25/2023 1:18 AM, Alex Williamson wrote:
> 
> On Wed, 24 May 2023 10:45:29 -0600
> Alex Williamson <alex.williamson@redhat.com> wrote:
> 
>> On Wed, 17 May 2023 15:27:18 +0530
>> Nipun Gupta <nipun.gupta@amd.com> wrote:
>>

<snip>

>>> +
>>> +MODULE_DEVICE_TABLE(cdx, vfio_cdx_table);
>>> +
>>> +static struct cdx_driver vfio_cdx_driver = {
>>> +   .probe          = vfio_cdx_probe,
>>> +   .remove         = vfio_cdx_remove,
>>> +   .match_id_table = vfio_cdx_table,
>>> +   .driver = {
>>> +           .name   = "vfio-cdx",
>>> +           .owner  = THIS_MODULE,
>>> +   },
>>> +   .driver_managed_dma = true,
> 
> Hmm, looks like cdx bus is broken here, there's no actual
> implementation of a dma_configure callback and no setup of the IOMMU
> default domain for theoretical cdx drivers that might want to use the
> DMA API.  Without that, this driver_manged_dma flag doesn't provide any
> guarantees to a vfio driver that we have exclusive ownership of the
> group.  Please fix, this flag needs to actually have some meaning on
> cdx.  Thanks,
> 
> Alex

Agree, this change was missed on CDX bus and we are working on fixing 
this. Shall I send this fix as a commit with this patch?

Thanks,
Nipun

  reply	other threads:[~2023-05-29  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-17  9:57 Nipun Gupta
2023-05-24 16:45 ` Alex Williamson
2023-05-24 19:48   ` Alex Williamson
2023-05-29  8:06     ` Nipun Gupta [this message]
2023-06-01 14:14       ` Jason Gunthorpe

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=1bf0323b-1191-de11-061e-00227e09dc35@amd.com \
    --to=nipun.gupta@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=git@amd.com \
    --cc=harpreet.anand@amd.com \
    --cc=jgg@ziepe.ca \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=michal.simek@amd.com \
    --cc=nathan@kernel.org \
    --cc=ndesaulniers@google.com \
    --cc=nicolas@fjasle.eu \
    --cc=nikhil.agarwal@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®