All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: Status IGD pass-through with QEMU/KVM
Date: Wed, 28 Jan 2015 16:43:47 +0100	[thread overview]
Message-ID: <54C903B3.8070104@siemens.com> (raw)
In-Reply-To: <1422459387.22865.105.camel@redhat.com>

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

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Status IGD pass-through with QEMU/KVM
Date: Wed, 28 Jan 2015 16:43:47 +0100	[thread overview]
Message-ID: <54C903B3.8070104@siemens.com> (raw)
In-Reply-To: <1422459387.22865.105.camel@redhat.com>

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

  reply	other threads:[~2015-01-28 15:43 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-28 15:02 Status IGD pass-through with QEMU/KVM Jan Kiszka
2015-01-28 15:02 ` [Qemu-devel] " Jan Kiszka
2015-01-28 15:36 ` Alex Williamson
2015-01-28 15:36   ` [Qemu-devel] " Alex Williamson
2015-01-28 15:43   ` Jan Kiszka [this message]
2015-01-28 15:43     ` Jan Kiszka
2015-02-10  7:36     ` Jan Kiszka
2015-02-10  7:36       ` [Qemu-devel] " Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=54C903B3.8070104@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.