Hi,
Hmm, wait, we could go 32 bit, then we are not limited to 32
bridges anymore, right? Does our bios support that?
How you want go to 32bit? io space (not mmio) is fixed at 16bit in x86,
isn't it?
cheers,
Gerd
--
To unsubscribe from this list: send the line unsubscribe kvm in
the
On Thu, Jun 02, 2011 at 11:19:35AM +0930, Rusty Russell wrote:
On Wed, 1 Jun 2011 13:25:48 +0300, Michael S. Tsirkin m...@redhat.com
wrote:
Add an option to modify the notificatin
hand-off in virtio to be basically like Xen:
each side published an index, the other side only triggers
an
Hi,
E.g. with 32 bridges, and 32 devices behind each one,
the available 64K space gets us only 64 bytes per device.
15 bridges (with io window enabled) max, the smallest io window you can
assign to a bridge is 4k, and you need some space for the devices on the
root bus ...
cheers,
On Wed, Aug 03, 2011 at 06:15:33PM +0200, Gerd Hoffmann wrote:
Hi,
E.g. with 32 bridges, and 32 devices behind each one,
the available 64K space gets us only 64 bytes per device.
15 bridges (with io window enabled) max, the smallest io window you
can assign to a bridge is 4k,
Hmm true,
On Wed, Aug 03, 2011 at 06:15:33PM +0200, Gerd Hoffmann wrote:
Hi,
E.g. with 32 bridges, and 32 devices behind each one,
the available 64K space gets us only 64 bytes per device.
15 bridges (with io window enabled) max, the smallest io window you
can assign to a bridge is 4k, and you
Add an option to modify the notificatin
hand-off in virtio to be basically like Xen:
each side published an index, the other side only triggers
an event when it crosses that index value
(Xen event indexes start at 1, ours start at 0 for
backward-compatiblity, but that's minor).
Since we've run
On Wed, 1 Jun 2011 13:25:48 +0300, Michael S. Tsirkin m...@redhat.com wrote:
Add an option to modify the notificatin
hand-off in virtio to be basically like Xen:
each side published an index, the other side only triggers
an event when it crosses that index value
(Xen event indexes start at 1,
