[OASIS Issue Tracker] Updated: (VIRTIO-32) MMIO: allow full 64 bit ring addresses

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ http://tools.oasis-open.org/issues/browse/VIRTIO-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Rusty Russell updated VIRTIO-32:
--------------------------------

        Summary: MMIO: allow full 64 bit ring addresses  (was: allow full 64 bit ring addresses)
       Assignee: Pawel Moll
    Description: 
we are using a 32 bit queuepfn so addresses can't be anywhere
in 64 bit address space.

[Re-titling: This already resolved in the draft for PCI.  CCW doesn't use pfns at all, and uses a 64 bit address.  MMIO uses a QueuePFN and a GuestPageSize, meaning it can go to larger addresses by sacrificing alignment.]


  was:
we are using a 32 bit queuepfn so addresses can't be anywhere
in 64 bit address space.



Assigning to Pawel: does he want to fix this, or leave things as-is?

> MMIO: allow full 64 bit ring addresses
> --------------------------------------
>
>                 Key: VIRTIO-32
>                 URL: http://tools.oasis-open.org/issues/browse/VIRTIO-32
>             Project: OASIS Virtual I/O Device (VIRTIO) TC
>          Issue Type: Improvement
>            Reporter: Michael Tsirkin
>            Assignee: Pawel Moll
>
> we are using a 32 bit queuepfn so addresses can't be anywhere
> in 64 bit address space.
> [Re-titling: This already resolved in the draft for PCI.  CCW doesn't use pfns at all, and uses a 64 bit address.  MMIO uses a QueuePFN and a GuestPageSize, meaning it can go to larger addresses by sacrificing alignment.]

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira