From: "G.R." <firemeteor@users.sourceforge.net>
To: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Ross Philipson <Ross.Philipson@citrix.com>,
Jean Guyader <jean.guyader@gmail.com>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: Need help to debug win7 BSOD on IGD passthrough
Date: Wed, 9 Jan 2013 23:07:27 +0800 [thread overview]
Message-ID: <CAKhsbWbGRpGNcJ_bnuN6YRVC4v3HyLZRCg4z3XRJ+YJv5MNEdQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1301071035350.4981@kaball.uk.xensource.com>
>> So I've accumulated many local fixes to make intel gpu passthrough work.
>> If you believe they are worthwhile, I'll clean up the fix and submit the patch.
>>
>> List of local fixes:
>> 1. Stefano's intel pch init fix, patch submitted and acked by Stefano.
>> Not sure if accepted && submitted.
>> 2. Patch for un-aligned OpRegion. Got feedback on security concern.
>> The impact is not yet clear.
>> 3. Vendor cap fix. Jean && Ross's patch about one year ago, lost in
>> the devel list.
>> 4. igfx reset fix. Jean's patch about one year ago, lost in the devel list.
>>
>> I think devel list is not the best way to track issue && fixes. I
>> wounder if there are public bug tracking systems.
>
> Ian Jackson is responsible for applying patches to the
> qemu-xen-traditional tree.
>
> However if you care to forward port the patches to upstream QEMU, that
> now has PCI passthrough support but it is still completely missing gfx
> passthrough, I would be happy to commit them and send them upstream.
Let me start with the qemu-xen-traditional tree, which I'm currently using.
I'll consider porting them to upstream QEMU once they are accepted.
Just some questions first:
1. Do I need to switch to the unstable tree? I'm currently on 4.2.1.
2. Any guide to generate patch series in git?
The wiki has a tutorial for Mercurial, but not git.
Generating well-formed patch series from a single file manually is not
a pleasant task.
next prev parent reply other threads:[~2013-01-09 15:07 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-11 9:26 Need help to debug win7 BSOD on IGD passthrough G.R.
2013-01-04 13:49 ` G.R.
2013-01-04 15:53 ` Ross Philipson
2013-01-04 16:30 ` G.R.
2013-01-04 18:14 ` Jean Guyader
2013-01-05 5:08 ` G.R.
2013-01-06 14:16 ` G.R.
2013-01-06 15:32 ` Pasi Kärkkäinen
2013-01-07 10:38 ` Stefano Stabellini
2013-01-09 15:07 ` G.R. [this message]
2013-01-09 16:12 ` Stefano Stabellini
2013-01-09 16:21 ` Ian Jackson
2013-01-07 15:51 ` Ross Philipson
2013-01-09 16:37 ` Stefano Stabellini
2013-01-10 10:18 ` G.R.
2013-01-10 10:31 ` Stefano Stabellini
2013-01-10 15:51 ` G.R.
2013-01-11 12:56 ` Stefano Stabellini
2013-01-15 17:12 ` G.R.
2013-01-15 18:40 ` Stefano Stabellini
2013-01-20 16:26 ` G.R.
2013-01-21 10:35 ` Stefano Stabellini
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=CAKhsbWbGRpGNcJ_bnuN6YRVC4v3HyLZRCg4z3XRJ+YJv5MNEdQ@mail.gmail.com \
--to=firemeteor@users.sourceforge.net \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Ross.Philipson@citrix.com \
--cc=jean.guyader@gmail.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).