From: Jason Gunthorpe <jgg@nvidia.com>
To: Brett Creeley <bcreeley@amd.com>
Cc: Christoph Hellwig <hch@infradead.org>,
Brett Creeley <brett.creeley@amd.com>,
kvm@vger.kernel.org, netdev@vger.kernel.org,
alex.williamson@redhat.com, cohuck@redhat.com,
yishaih@nvidia.com, shameerali.kolothum.thodi@huawei.com,
kevin.tian@intel.com, shannon.nelson@amd.com,
drivers@pensando.io
Subject: Re: [PATCH v3 vfio 0/7] pds vfio driver
Date: Thu, 23 Feb 2023 09:26:12 -0400 [thread overview]
Message-ID: <Y/dpdJ650q/aRIO2@nvidia.com> (raw)
In-Reply-To: <a797f017-4233-0464-45fb-0d9aeab6b4e4@amd.com>
On Wed, Feb 22, 2023 at 11:01:33PM -0800, Brett Creeley wrote:
> > You have to remove the aux bus stuff also if you want this taken
> > seriously. Either aux for all or aux for none, I don't want drivers
>
> Can you please expand on the "aux for all or aux for none" comment? It's not
> clear what you mean here.
You shouldn't be using aux at all for this, but if you do figure out
how to make it work right then all the drivers should be moved to use
it.
Jason
prev parent reply other threads:[~2023-02-23 13:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 8:39 [PATCH v3 vfio 0/7] pds vfio driver Brett Creeley
2023-02-19 8:39 ` [PATCH v3 1/7] vfio/pds: Initial support for pds_vfio VFIO driver Brett Creeley
2023-02-19 8:39 ` [PATCH v3 2/7] vfio/pds: Add support to register as PDS client Brett Creeley
2023-02-19 8:39 ` [PATCH v3 3/7] vfio/pds: Add VFIO live migration support Brett Creeley
2023-02-19 8:39 ` [PATCH v3 4/7] vfio: Commonize combine_ranges for use in other VFIO drivers Brett Creeley
2023-02-19 8:39 ` [PATCH v3 5/7] vfio/pds: Add support for dirty page tracking Brett Creeley
2023-02-19 8:39 ` [PATCH v3 6/7] vfio/pds: Add support for firmware recovery Brett Creeley
2023-02-19 8:39 ` [PATCH v3 7/7] vfio/pds: Add Kconfig and documentation Brett Creeley
2023-02-20 6:29 ` [PATCH v3 vfio 0/7] pds vfio driver Christoph Hellwig
2023-02-21 0:45 ` Brett Creeley
2023-02-21 1:11 ` Jason Gunthorpe
2023-02-23 7:01 ` Brett Creeley
2023-02-23 13:26 ` Jason Gunthorpe [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=Y/dpdJ650q/aRIO2@nvidia.com \
--to=jgg@nvidia.com \
--cc=alex.williamson@redhat.com \
--cc=bcreeley@amd.com \
--cc=brett.creeley@amd.com \
--cc=cohuck@redhat.com \
--cc=drivers@pensando.io \
--cc=hch@infradead.org \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=shameerali.kolothum.thodi@huawei.com \
--cc=shannon.nelson@amd.com \
--cc=yishaih@nvidia.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.