Displaying 7 results from an estimated 7 matches for "madates".
Did you mean:
mandates
2013 May 29
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...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 conf...
2003 Oct 07
0
FW: Environment passing in Solaris 8 with later versions of SSH a nd UseLogin=yes
Hi,
I'm still hoping that some-one can offer a solution to this issue....
Anyone?
> I've got the following issue, which I'm unable to resolve by
> myself. Hopefully, someone on the list will be able to guide
> me, or provide more information towards resolving this.
>
> We've compiled OpenSSH v3.7.1p1 (which I know is not the most
> recent version) on
2013 May 29
0
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...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 BAR0,...
2003 Sep 29
1
Environment passing in Solaris 8 with later versions of SSH and U seLogin=yes
Hi,
I've got the following issue, which I'm unable to resolve by myself.
Hopefully, someone on the list will be able to guide me, or provide more
information towards resolving this.
We've compiled OpenSSH v3.7.1p1 (which I know is not the most recent
version) on Solaris 8 SPARC, and have noticed that when the "UseLogin=yes"
parameter is set in the sshd_config file, the
2013 May 29
5
[PATCH RFC] virtio-pci: new config layout: using memory BAR
...;
> >> 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 is...
2013 May 29
6
[PATCH RFC] virtio-pci: new config layout: using memory BAR
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,
2013 May 29
6
[PATCH RFC] virtio-pci: new config layout: using memory BAR
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,