Displaying 8 results from an estimated 8 matches for "attern".
Did you mean:
altern
2020 Mar 02
3
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
On Fri, Feb 28, 2020 at 06:25:36PM +0100, Jean-Philippe Brucker wrote:
> This solution isn't elegant nor foolproof, but is the best we can do at
> the moment and works with existing virtio-iommu implementations. It also
> enables an IOMMU for lightweight hypervisors that do not rely on
> firmware methods for booting.
I appreciate the enablement on x86, but putting the
2020 Mar 02
3
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
On Fri, Feb 28, 2020 at 06:25:36PM +0100, Jean-Philippe Brucker wrote:
> This solution isn't elegant nor foolproof, but is the best we can do at
> the moment and works with existing virtio-iommu implementations. It also
> enables an IOMMU for lightweight hypervisors that do not rely on
> firmware methods for booting.
I appreciate the enablement on x86, but putting the
2020 Mar 03
2
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...if it is not possible
ther can be a new table-type for Virtio-iommu. That would still follow
platform best practices.
> x86 ACPI integration was suggested with IORT. But it seems ARM is
> reluctant to extend IORT to support para-virtualized IOMMU. So the VIOT
> was proposed as a different atternative in "[RFC 00/13] virtio-iommu on
> non-devicetree platforms"
> (https://patchwork.kernel.org/cover/11257727/). Proposing a table that
> may be used by different vendors seems to be a challenging issue here.
Yeah, if I am reading that right this proposes a one-fits-all soluti...
2020 Mar 03
2
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...if it is not possible
ther can be a new table-type for Virtio-iommu. That would still follow
platform best practices.
> x86 ACPI integration was suggested with IORT. But it seems ARM is
> reluctant to extend IORT to support para-virtualized IOMMU. So the VIOT
> was proposed as a different atternative in "[RFC 00/13] virtio-iommu on
> non-devicetree platforms"
> (https://patchwork.kernel.org/cover/11257727/). Proposing a table that
> may be used by different vendors seems to be a challenging issue here.
Yeah, if I am reading that right this proposes a one-fits-all soluti...
2020 Mar 03
0
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...not need ACPI
description
Another issue with ACPI integration is we have different flavours of
tables that exist: IORT, DMAR, IVRS
x86 ACPI integration was suggested with IORT. But it seems ARM is
reluctant to extend IORT to support para-virtualized IOMMU. So the VIOT
was proposed as a different atternative in "[RFC 00/13] virtio-iommu on
non-devicetree platforms"
(https://patchwork.kernel.org/cover/11257727/). Proposing a table that
may be used by different vendors seems to be a challenging issue here.
So even if the above solution does not look perfect, it looked a
sensible compromis...
2020 Mar 03
0
[PATCH v2 1/3] iommu/virtio: Add topology description to virtio-iommu config space
...r can be a new table-type for Virtio-iommu. That would still follow
> platform best practices.
>
> > x86 ACPI integration was suggested with IORT. But it seems ARM is
> > reluctant to extend IORT to support para-virtualized IOMMU. So the VIOT
> > was proposed as a different atternative in "[RFC 00/13] virtio-iommu on
> > non-devicetree platforms"
> > (https://patchwork.kernel.org/cover/11257727/). Proposing a table that
> > may be used by different vendors seems to be a challenging issue here.
>
> Yeah, if I am reading that right this propo...
2009 Oct 12
1
How to force winbind (3.4.1) to talk to a certain AD-server?
...at an I do?
Greets
Malte Schr?der
#======================================================================#
Vattenfall Europe Information Services GmbH, Hamburg, Amtsgericht Hamburg - HRB 86516
Vorsitzender des Aufsichtsrates: Dr. Stefan Keese
Gesch?ftsf?hrer: Ernst Wudtke, Armin Fischer, Lennart Attern?s
2005 Nov 26
1
Tomb Raider 4 and wine 0.9.1(DirectX 6.1)
...Draw_SetCooperativeLevel (0x7fef1a18)->((nil),00000008)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x7fef1a18)->((nil),0000004d)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x7fef1a18)->(0x10022,00000015)
err:ddraw:set_render_state Unhandled dwRenderStateType D3DRENDERSTATE_LINEPATTERN (00
00000a) value : 00000000 !
err:ddraw:set_render_state Unhandled dwRenderStateType D3DRENDERSTATE_MONOENABLE (000
0000b) value : 00000000 !
err:ddraw:set_render_state Unhandled dwRenderStateType D3DRENDERSTATE_ROP2 (0000000c)
value : 0000000d !
err:ddraw:set_render_state Unhandled dwRenderState...