From: Christoph Hellwig <hch@infradead.org>
To: Kirti Wankhede <kwankhede@nvidia.com>
Cc: cjia@nvidia.com, kvm@vger.kernel.org, aik@ozlabs.ru,
Zhengxiao.zx@alibaba-inc.com, shuangtai.tst@alibaba-inc.com,
qemu-devel@nongnu.org, eauger@redhat.com, yi.l.liu@intel.com,
eskultet@redhat.com, ziye.yang@intel.com, mlevitsk@redhat.com,
pasic@linux.ibm.com, felipe@nutanix.com, zhi.a.wang@intel.com,
kevin.tian@intel.com, yan.y.zhao@intel.com, dgilbert@redhat.com,
alex.williamson@redhat.com, changpeng.liu@intel.com,
cohuck@redhat.com, Ken.Xue@amd.com, jonathan.davies@nutanix.com
Subject: Re: [PATCH v15 Kernel 1/7] vfio: KABI for migration interface for device state
Date: Thu, 26 Mar 2020 02:33:10 -0700 [thread overview]
Message-ID: <20200326093310.GA12078@infradead.org> (raw)
In-Reply-To: <1584649004-8285-2-git-send-email-kwankhede@nvidia.com>
s/KABI/UAPI/ in the subject and anywhere else in the series.
Please avoid __packed__ structures and just properly pad them, they
have a major performance impact on some platforms and will cause
compiler warnings when taking addresses of members.
next prev parent reply other threads:[~2020-03-26 9:34 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-19 20:16 [PATCH v15 Kernel 0/7] KABIs to support migration for VFIO devices Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 1/7] vfio: KABI for migration interface for device state Kirti Wankhede
2020-03-23 20:30 ` Auger Eric
2020-03-24 19:31 ` Kirti Wankhede
2020-03-26 9:33 ` Christoph Hellwig [this message]
2020-03-26 21:39 ` Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 2/7] vfio iommu: Remove atomicity of ref_count of pinned pages Kirti Wankhede
2020-03-23 20:30 ` Auger Eric
2020-03-24 19:34 ` Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 3/7] vfio iommu: Add ioctl definition for dirty pages tracking Kirti Wankhede
2020-03-23 21:11 ` Auger Eric
2020-03-24 19:49 ` Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 4/7] vfio iommu: Implementation of ioctl " Kirti Wankhede
2020-03-19 22:57 ` Alex Williamson
2020-03-20 17:49 ` Kirti Wankhede
2020-03-20 18:01 ` Alex Williamson
2020-03-20 18:42 ` Kirti Wankhede
2020-03-20 18:59 ` Alex Williamson
2020-03-23 17:54 ` Kirti Wankhede
2020-03-23 18:44 ` Alex Williamson
2020-03-23 18:51 ` Dr. David Alan Gilbert
2020-03-24 3:01 ` Yan Zhao
2020-03-24 9:45 ` Kirti Wankhede
2020-03-24 14:36 ` Alex Williamson
2020-03-24 20:23 ` Dr. David Alan Gilbert
2020-03-25 5:31 ` Tian, Kevin
2020-03-19 20:16 ` [PATCH v15 Kernel 5/7] vfio iommu: Update UNMAP_DMA ioctl to get dirty bitmap before unmap Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 6/7] vfio iommu: Adds flag to indicate dirty pages tracking capability support Kirti Wankhede
2020-03-19 20:16 ` [PATCH v15 Kernel 7/7] vfio: Selective dirty page tracking if IOMMU backed device pins pages Kirti Wankhede
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=20200326093310.GA12078@infradead.org \
--to=hch@infradead.org \
--cc=Ken.Xue@amd.com \
--cc=Zhengxiao.zx@alibaba-inc.com \
--cc=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=changpeng.liu@intel.com \
--cc=cjia@nvidia.com \
--cc=cohuck@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eauger@redhat.com \
--cc=eskultet@redhat.com \
--cc=felipe@nutanix.com \
--cc=jonathan.davies@nutanix.com \
--cc=kevin.tian@intel.com \
--cc=kvm@vger.kernel.org \
--cc=kwankhede@nvidia.com \
--cc=mlevitsk@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=shuangtai.tst@alibaba-inc.com \
--cc=yan.y.zhao@intel.com \
--cc=yi.l.liu@intel.com \
--cc=zhi.a.wang@intel.com \
--cc=ziye.yang@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).