Displaying 7 results from an estimated 7 matches for "madated".
Did you mean:
mandated
2013 May 29
7
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Wed, May 29, 2013 at 07:52:37AM -0500, Anthony Liguori wrote:
> Rusty Russell <rusty at rustcorp.com.au> writes:
>
> > 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
2003 Oct 07
0
FW: Environment passing in Solaris 8 with later versions of SSH a nd UseLogin=yes
...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&qu...
2013 May 29
0
[PATCH RFC] virtio-pci: new config layout: using memory BAR
"Michael S. Tsirkin" <mst at redhat.com> writes:
> On Wed, May 29, 2013 at 07:52:37AM -0500, Anthony Liguori wrote:
>> 1) C makes no guarantees about structure layout beyond the first
>> member. Yes, if it's naturally aligned or has a packed attribute,
>> GCC does the right thing. But this isn't kernel land anymore,
>> portability
2003 Sep 29
1
Environment passing in Solaris 8 with later versions of SSH and U seLogin=yes
...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 code...
2013 May 29
5
[PATCH RFC] virtio-pci: new config layout: using memory BAR
On Wed, May 29, 2013 at 09:16:39AM -0500, Anthony Liguori wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
>
> > On Wed, May 29, 2013 at 07:52:37AM -0500, Anthony Liguori wrote:
> >> 1) C makes no guarantees about structure layout beyond the first
> >> member. Yes, if it's naturally aligned or has a packed attribute,
> >>
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,