All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel@nongnu.org,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Alexander Graf <agraf@suse.de>
Subject: Re: [Qemu-devel] [PATCH] vfio: Make BARs native endian
Date: Thu, 19 Jun 2014 10:42:04 +1000	[thread overview]
Message-ID: <53A231DC.2040004@ozlabs.ru> (raw)
In-Reply-To: <1403117875.3707.184.camel@ul30vt.home>

On 06/19/2014 04:57 AM, Alex Williamson wrote:
> On Wed, 2014-06-18 at 21:35 +1000, Alexey Kardashevskiy wrote:
>> Slow BAR access path is used when VFIO fails to mmap() BAR or TCG is used.
> 
> TCG can use the mmap too

Oh, right.


> 
>> Since this is just a transport between the guest and a device, there is
>> no need to do endianness swapping.
>>
>> This changes BARs to use native endianness. Since non-ROM BARs were
>> doing byte swapping, we need to remove it so does the patch. No change
>> in behavior is expected though.
>>
>> ROM BARs were declared little endian but byte swapping was not
>> implemented for them so they never actually worked on big endian systems.
>> This fixes endiannes for ROM BARs: this declares them native endian and
>> fixes access sizes.
> 
> So the only actual behavior change we expect from this is to fix ROM
> access on big endian where we had an unbalanced set of byte swaps.  BAR
> access worked because the byte swapping in the read/write handler
> canceled the byte swapping in QEMU because we declared the BARs as
> little endian.  Otherwise we're just removing canceling byte swaps for
> big endian.  Is that correct?

Yes.

> 
> Also, as the kernel patch appears to not produce any behavioral change,
> only eliminates canceling swaps, there's no dependency between patches,
> right?  Thanks,

That is right.

> 
> Alex
> 
>> Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru>
>> ---
>>  hw/misc/vfio.c | 41 +++++++++++++++++++++++++++++++----------
>>  1 file changed, 31 insertions(+), 10 deletions(-)
>>
>> diff --git a/hw/misc/vfio.c b/hw/misc/vfio.c
>> index 7437c2e..3eb3c71 100644
>> --- a/hw/misc/vfio.c
>> +++ b/hw/misc/vfio.c
>> @@ -1052,10 +1052,10 @@ static void vfio_bar_write(void *opaque, hwaddr addr,
>>          buf.byte = data;
>>          break;
>>      case 2:
>> -        buf.word = cpu_to_le16(data);
>> +        buf.word = data;
>>          break;
>>      case 4:
>> -        buf.dword = cpu_to_le32(data);
>> +        buf.dword = data;
>>          break;
>>      default:
>>          hw_error("vfio: unsupported write size, %d bytes", size);
>> @@ -1112,10 +1112,10 @@ static uint64_t vfio_bar_read(void *opaque,
>>          data = buf.byte;
>>          break;
>>      case 2:
>> -        data = le16_to_cpu(buf.word);
>> +        data = buf.word;
>>          break;
>>      case 4:
>> -        data = le32_to_cpu(buf.dword);
>> +        data = buf.dword;
>>          break;
>>      default:
>>          hw_error("vfio: unsupported read size, %d bytes", size);
>> @@ -1142,7 +1142,7 @@ static uint64_t vfio_bar_read(void *opaque,
>>  static const MemoryRegionOps vfio_bar_ops = {
>>      .read = vfio_bar_read,
>>      .write = vfio_bar_write,
>> -    .endianness = DEVICE_LITTLE_ENDIAN,
>> +    .endianness = DEVICE_NATIVE_ENDIAN,
>>  };
>>  
>>  static void vfio_pci_load_rom(VFIODevice *vdev)
>> @@ -1204,21 +1204,42 @@ static void vfio_pci_load_rom(VFIODevice *vdev)
>>  static uint64_t vfio_rom_read(void *opaque, hwaddr addr, unsigned size)
>>  {
>>      VFIODevice *vdev = opaque;
>> -    uint64_t val = ((uint64_t)1 << (size * 8)) - 1;
>> +    union {
>> +        uint8_t byte;
>> +        uint16_t word;
>> +        uint32_t dword;
>> +        uint64_t qword;
>> +    } buf;
>> +    uint64_t data = 0;
>>  
>>      /* Load the ROM lazily when the guest tries to read it */
>>      if (unlikely(!vdev->rom && !vdev->rom_read_failed)) {
>>          vfio_pci_load_rom(vdev);
>>      }
>>  
>> -    memcpy(&val, vdev->rom + addr,
>> +    memcpy(&buf, vdev->rom + addr,
>>             (addr < vdev->rom_size) ? MIN(size, vdev->rom_size - addr) : 0);
>>  
>> +    switch (size) {
>> +    case 1:
>> +        data = buf.byte;
>> +        break;
>> +    case 2:
>> +        data = buf.word;
>> +        break;
>> +    case 4:
>> +        data = buf.dword;
>> +        break;
>> +    default:
>> +        hw_error("vfio: unsupported read size, %d bytes", size);
>> +        break;
>> +    }
>> +
>>      DPRINTF("%s(%04x:%02x:%02x.%x, 0x%"HWADDR_PRIx", 0x%x) = 0x%"PRIx64"\n",
>>              __func__, vdev->host.domain, vdev->host.bus, vdev->host.slot,
>> -            vdev->host.function, addr, size, val);
>> +            vdev->host.function, addr, size, data);
>>  
>> -    return val;
>> +    return data;
>>  }
>>  
>>  static void vfio_rom_write(void *opaque, hwaddr addr,
>> @@ -1229,7 +1250,7 @@ static void vfio_rom_write(void *opaque, hwaddr addr,
>>  static const MemoryRegionOps vfio_rom_ops = {
>>      .read = vfio_rom_read,
>>      .write = vfio_rom_write,
>> -    .endianness = DEVICE_LITTLE_ENDIAN,
>> +    .endianness = DEVICE_NATIVE_ENDIAN,
>>  };
>>  
>>  static bool vfio_blacklist_opt_rom(VFIODevice *vdev)
> 
> 
> 


-- 
Alexey

  reply	other threads:[~2014-06-19  0:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-18 11:35 [Qemu-devel] [PATCH] vfio: Make BARs native endian Alexey Kardashevskiy
2014-06-18 18:57 ` Alex Williamson
2014-06-19  0:42   ` Alexey Kardashevskiy [this message]
2014-06-19  1:53     ` Alexey Kardashevskiy
2014-06-20  3:21       ` Alex Williamson

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=53A231DC.2040004@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    /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.