Re: [Xen-devel] ATI/AMD VGA passthru report

[Pavel MatÄja <pavel@xxxxxxxxxx>]

On Tue 8. of May 2012 01:07:07 Konrad Rzeszutek Wilk wrote:
> On Tue, May 08, 2012 at 01:10:32AM +0200, Pavel Mateja wrote:
> > > On Mon, May 07, 2012 at 01:45:23PM +0200, Pavel MatÄ?ja wrote:
> > >> Hi,
> > >> I'm trying to run AMD VGA passthru on latest XEN unstable with latest
> > >> kernel.
> > >> I already have working setup with ancient xen-devel 4.2 and 2.6.32.x
> > >> xenified
> > >> kernel. See attached log.
> > >> 
> > >> So I tried just to update and patch xen and kernel, but I had no luck
> > >> so far.
> > >> 
> > >> Xen has ati_vbios_patch_respin.txt sent to xen-devel by Wei Huang
> > >> recently.
> > >> http://lists.xen.org/archives/html/xen-devel/2012-04/msg00291.html
> > >> 
> > >> I tried two kernels
> > >> testing-3.5-with-extra and xen/next-3.2 from
> > >> git://git.kernel.org/pub/scm/linux/kernel/git/konrad/xen.git
> > >> and
> > >> git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git
> > >> Both with ioperm opcode patch which is required by the ATI patch. See
> > >> attachement.
> > >> 
> > >> The xen/next-3.2 branch kernel was able to start booting windows.
> > >> With Catalyst driver installed I just saw bluescreen during Windows
> > >> boot.
> > >> Without Catalyst driver Windows were able to boot but Windows ended
> > >> frozen or
> > >> USB was not working. It was hard to tell because input devices had no
> > >> response
> > >> at all.
> > >> 
> > >> The testing-3.5-with-extra (reported as 3.4.0-rc4) just crashed dom0
> > >> kernel
> > >> during Windows boot. I guess I have to rework the io_bitmap patch
> > >> somehow.
> > > 
> > > When you say 'io_bitmap' patch are you referring to these ones:
> > > 
> > > 70a357d xen: implement IO permission bitmap
> > > 0c596c5 x86/paravirt: paravirtualize IO permission bitmap
> > > 93b7a2a x86: demacro set_iopl_mask()
> > > 
> > > ? I don't think those are in that tag. They are in the kitchensink -
> > > #testing
> > > - does it work with that branch?
> > > 
> > > The next-3.2 is a bit old. I should actually delete it.
> > 
> > Hi,
> > I mean this patch below.
> > I think it was originally here:
> > http://old-list-archives.xen.org/archives/html/xen-devel/2009-05/msg01139
> > .html Then I was told by you to use devel/ioperm branch which I think
> > doesn't exist anymore:
> > http://old-list-archives.xen.org/archives/html/xen-devel/2011-11/msg01213
> > .html
> 
> It certainly does :-)
> 
> > I'm too tired to test #testing branch now. I'll try it tomorrow after
> > some sleep.
> 
> OK, take your time.

Hi again!
I did first tests with xen-unstable and the #testing kernel.

Windows showed blue screen during boot with xm toolstack.

But I had luck with xl. Windows booted succesfully so I ran the experience 
index tests:
kernel: 2.6.32.57       #testing
CPU             7,4             7,4
RAM             7,4             5,5
Aero            7,1             7,1
Gr.card 7,1             7,1
Disk            7,3             7,5
I tried to run some games as well but the feeling is much worse compared to 
older configuration. Like lags..

Are there some older branches which are supposed to work?

I tried xen-4.1.3-rc1 with #testing kernel but it just freezes after while 
even with Dom0 running. Only sys-rq worked.

I have second slightly newer system too so I'll retest that one later.
-- 
Pavel Mateja

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel