[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] Status IGD pass-through with QEMU/KVM
From: |
Jan Kiszka |
Subject: |
Re: [Qemu-devel] Status IGD pass-through with QEMU/KVM |
Date: |
Wed, 28 Jan 2015 16:43:47 +0100 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 |
On 2015-01-28 16:36, Alex Williamson wrote:
> On Wed, 2015-01-28 at 16:02 +0100, Jan Kiszka wrote:
>> Hi Alex,
>>
>> before getting dirty fingers in vain: what is the current status of
>> handing an IGD GPU to a KVM guest, specifically Windows? I found some
>> related QEMU patches from last year on the list, but it seems they
>> didn't progress. Are there open issues without known solutions or is it
>> "just" about putting pieces together - given that there related patches
>> for Xen floating around?
>
> Hi Jan,
>
> The patches submitted last year by Andrew Barnes are functional (AFAIK),
> but mostly proof-of-concept quality. They make use of /dev/mem in place
> of designing VFIO interfaces, they hack into various chipset code, etc.
> Based on the attempts to port the Xen IGD code into QEMU, I think Intel
> was working on reducing the machine level impact of IGD assignment with
> a "universal" driver, but I haven't seen any status updates on that for
> some time. If Intel is successful in creating such a driver, then IGD
> assignment may be no more complicated that discrete assignment (but
> might only support very new HW). To support current hardware and
> drivers, we need to expose not only the IGD device, but manipulate
> chispet device IDs and punch through registers and opregions on other
> devices. Andrew's patches do this, but need help to architect
> interfaces and break down the code into upstream-able chunks. Thanks,
OK, thanks. Need to study more details then.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux