All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Thomas, Ramesh" <ramesh.thomas@intel.com>
To: Jason Gunthorpe <jgg@ziepe.ca>
Cc: <alex.williamson@redhat.com>, <schnelle@linux.ibm.com>,
	<gbayer@linux.ibm.com>, <kvm@vger.kernel.org>,
	<linux-s390@vger.kernel.org>, <ankita@nvidia.com>,
	<yishaih@nvidia.com>, <pasic@linux.ibm.com>,
	<julianr@linux.ibm.com>, <bpsegal@us.ibm.com>,
	<kevin.tian@intel.com>, <cho@microsoft.com>
Subject: Re: [PATCH v2 2/2] vfio/pci: Remove #ifdef iowrite64 and #ifdef ioread64
Date: Tue, 10 Dec 2024 05:22:33 -0800	[thread overview]
Message-ID: <7611ed37-9ea9-47df-8409-29997bd34e37@intel.com> (raw)
In-Reply-To: <20241209181953.GD1888283@ziepe.ca>


On 12/9/2024 10:19 AM, Jason Gunthorpe wrote:
> On Tue, Dec 03, 2024 at 10:41:58AM -0800, Ramesh Thomas wrote:
>> Remove the #ifdef iowrite64 and #ifdef ioread64 checks around calls to
>> 64 bit IO access. Since default implementations have been enabled, the
>> checks are not required. Such checks can hide potential bugs as well.
>> Instead check for CONFIG_64BIT to make the 64 bit IO calls only when 64
>> bit support is enabled.
> Why?
>
> The whole point of the emulation header to to avoid this?
>
> I think you would just include the header and then remove the ifdef
> entirely. Instead of vfio doing memcpy with 32 bit it will do memcpy
> internally to the io accessors?
>
> There is nothing about this that has to be atomic or something.

Ok, I will send a new patch series that only removes the check for 
ioread64 and iowrite64.

Thanks,

Ramesh


      reply	other threads:[~2024-12-10 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 18:41 [PATCH v2 0/2] Extend 8-byte PCI load/store support to x86 arch Ramesh Thomas
2024-12-03 18:41 ` [PATCH v2 1/2] vfio/pci: Enable iowrite64 and ioread64 for vfio pci Ramesh Thomas
2024-12-04 17:13   ` Niklas Schnelle
2024-12-03 18:41 ` [PATCH v2 2/2] vfio/pci: Remove #ifdef iowrite64 and #ifdef ioread64 Ramesh Thomas
2024-12-09 18:19   ` Jason Gunthorpe
2024-12-10 13:22     ` Thomas, Ramesh [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=7611ed37-9ea9-47df-8409-29997bd34e37@intel.com \
    --to=ramesh.thomas@intel.com \
    --cc=alex.williamson@redhat.com \
    --cc=ankita@nvidia.com \
    --cc=bpsegal@us.ibm.com \
    --cc=cho@microsoft.com \
    --cc=gbayer@linux.ibm.com \
    --cc=jgg@ziepe.ca \
    --cc=julianr@linux.ibm.com \
    --cc=kevin.tian@intel.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=pasic@linux.ibm.com \
    --cc=schnelle@linux.ibm.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.