search for: madat

...atches closely, you will see that we still support the old layout on BAR0. > is a really big > deal and I see no reason to do that unless there's a compelling reason > to. There are many a compelling reasons, and they are well known limitations of virtio PCI: - PCI spec compliance (madates device operation with IO memory disabled). - support 64 bit addressing - add more than 32 feature bits. - individually disable queues. - sanely support cross-endian systems. - support very small (<1 PAGE) for virtio rings. - support a separate page for each vq kick. - make each device place co...

...y TERM is not being set correctly is causing all sorts > of problems. > > This DOES work in OpenSSH 3.0p1, with the same configuration > file. Turning UseLogin OFF in OpenSSH 3.7.1p1 also works; > but causes other issues with Solaris password aging, so isn't > an option (madated by our Information Security people). This > has been tested on the SAME machine in the SAME interactive > session, so I know it isn't an issue with different OS / > build / runtime factors. > > As far as I can tell, the environment etc is all done in > "session.c&...

...support the old layout on BAR0. > > >> is a really big >> deal and I see no reason to do that unless there's a compelling reason >> to. > > There are many a compelling reasons, and they are well known > limitations of virtio PCI: > > - PCI spec compliance (madates device operation with IO memory > disabled). PCI express spec. We are fully compliant with the PCI spec. And what's the user visible advantage of pointing an emulated virtio device behind a PCI-e bus verses a legacy PCI bus? This is a very good example because if we have to disable BAR...

...T and SSH_TTY; but the fact that my TERM is not being set correctly is causing all sorts of problems. This DOES work in OpenSSH 3.0p1, with the same configuration file. Turning UseLogin OFF in OpenSSH 3.7.1p1 also works; but causes other issues with Solaris password aging, so isn't an option (madated by our Information Security people). This has been tested on the SAME machine in the SAME interactive session, so I know it isn't an issue with different OS / build / runtime factors. As far as I can tell, the environment etc is all done in "session.c". I've looked at the cod...

...; > >> is a really big > >> deal and I see no reason to do that unless there's a compelling reason > >> to. > > > > There are many a compelling reasons, and they are well known > > limitations of virtio PCI: > > > > - PCI spec compliance (madates device operation with IO memory > > disabled). > > PCI express spec. We are fully compliant with the PCI spec. And what's > the user visible advantage of pointing an emulated virtio device behind > a PCI-e bus verses a legacy PCI bus? Native hotplug support. > This i...

Anthony Liguori <aliguori at us.ibm.com> writes: > "Michael S. Tsirkin" <mst at redhat.com> writes: >> + case offsetof(struct virtio_pci_common_cfg, device_feature_select): >> + return proxy->device_feature_select; > > Oh dear no... Please use defines like the rest of QEMU. It is pretty ugly. Yet the structure definitions are descriptive,

Anthony Liguori <aliguori at us.ibm.com> writes: > "Michael S. Tsirkin" <mst at redhat.com> writes: >> + case offsetof(struct virtio_pci_common_cfg, device_feature_select): >> + return proxy->device_feature_select; > > Oh dear no... Please use defines like the rest of QEMU. It is pretty ugly. Yet the structure definitions are descriptive,