Displaying 8 results from an estimated 8 matches for "atternative".
Did you mean:
alternative
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 solution.
T...
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 solution.
T...
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 compromise giv...
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 proposes a...
2009 Oct 12
1
How to force winbind (3.4.1) to talk to a certain AD-server?
Hello,
how can I force winbind to talk to a certain AD-controller?
I run version 3.4.1 and winbind is joined to the Win2k3/2k8 domain, with
security = ADS. It seems as if winbind always sticks to the last successfully
contacted server. That server has bad performance and I want winbind to use
another server for NTLM-authentication. It seems to ignore the "password
server" setting.
2005 Nov 26
1
Tomb Raider 4 and wine 0.9.1(DirectX 6.1)
Hi!
I've just installed wine-0.9.1 on my Fedora Core 3 system (Radeon 9600XT
- fglrx-8.19.10).
While TR3(demo) setup & gameplay runs okay, TR4 breaks and gives me this
error output after the setup screen is thru:
ALSA lib seq_hw.c:446:(snd_seq_hw_open) open /dev/snd/seq failed: No
such file or dir
ectory
err:int:INSTR_EmulateInstruction mov cr4,eax at 0x0048da53