xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Gennady Marchenko <gennady.marchenko@gmail.com>
To: Liwei <xieliwei@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen, ustable and VGA passthrough
Date: Sat, 21 May 2011 19:58:19 +0400	[thread overview]
Message-ID: <BANLkTimiyKZTdYd4phbe4x45kn_SfS+16Q@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimWhPxQUaB0PMbC7bhaZ1PnUDBBDw@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 4170 bytes --]

Hello again Liwei!

Thanks for your patch it applied good :)

With your patch I can run my ATI 5450 as primary GPU (I have no secondary at
all) as basic VGA:

Windows XP can start and show the desktop if it has no installed drivers. It
is very big progress for me :)

After I installed drivers it can't init the GPU. I think when you tries to
install Win7 you got same - because it already have buildin drivers and
tries to init extended display mode.
My logs is:

root@xen:/var/log/xen# tail -f /var/log/xen/qemu-dm-winxp.log
(here domU started up)
pt_iomem_map: e_phys=d0000000 maddr=d0000000 type=8 len=268435456 index=0
first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_iomem_map: e_phys=febc0000 maddr=febc0000 type=0 len=131072 index=2
first_map=1
pt_bar_reg_read: first read BARs of gfx
pt_bar_reg_read: first read BARs of gfx
pt_ioport_map: e_phys=e000 pio_base=e000 len=256 index=4 first_map=1
pt_iomem_map: e_phys=f1000000 maddr=febfc000 type=0 len=16384 index=0
first_map=1
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is rw
state.
platform_fixed_ioport: changed ro/rw state of ROM memory area. now is ro
state.




(here I see windows xp 'load' progress with logo, mayb it tries to init vga)
pt_iomem_map: e_phys=ffffffff maddr=d0000000 type=8 len=268435456 index=0
first_map=0
pt_iomem_map: e_phys=ffffffff maddr=febc0000 type=0 len=131072 index=2
first_map=0
pt_ioport_map: e_phys=ffff pio_base=e000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=d0000000 maddr=d0000000 type=8 len=268435456 index=0
first_map=0
pt_iomem_map: e_phys=febc0000 maddr=febc0000 type=0 len=131072 index=2
first_map=0
pt_ioport_map: e_phys=e000 pio_base=e000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=ffffffff maddr=febfc000 type=0 len=16384 index=0
first_map=0
pt_pci_write_config: Warning: Guest attempt to set address to unused Base
Address Register. [00:06.0][Offset:30h][Length:4]
pt_iomem_map: e_phys=f1000000 maddr=febfc000 type=0 len=16384 index=0
first_map=0


(here it must start to show the desktop)
pt_iomem_map: e_phys=ffffffff maddr=d0000000 type=8 len=268435456 index=0
first_map=0
pt_iomem_map: e_phys=ffffffff maddr=febc0000 type=0 len=131072 index=2
first_map=0
pt_ioport_map: e_phys=ffff pio_base=e000 len=256 index=4 first_map=0
pt_iomem_map: e_phys=e0000000 maddr=d0000000 type=8 len=268435456 index=0
first_map=0
pt_iomem_map: e_phys=fbfe0000 maddr=febc0000 type=0 len=131072 index=2
first_map=0
pt_ioport_map: e_phys=e000 pio_base=e000 len=256 index=4 first_map=0

(but something goes wrong :))
reset requested in cpu_handle_ioreq.
Issued domain 6 reboot

It may be problem with memory map in dsdt.asl but I don't know how it may
fix. :(

Thanks a lot for your patch.

Gennady.


On Fri, May 20, 2011 at 10:08 AM, Liwei <xieliwei@gmail.com> wrote:

> Hello Gennady!
>    Wasn't planning on posting the patch until it works. Also not sure
> if it'll end up destroying stuff so, do take care! Not my fault if
> unfortunate stuff happens!
>    The patch was hastily created on a separate Ubuntu machine with
> the source partition mounted, so I couldn't do a compile test nor am I
> sure if all the changes I made are in the patch. Tell me if it doesn't
> compile after applying the patch, I probably missed a file or two.
>    Patch is based on the original VGA passthrough patches posted by
> Weidong, modified to account for the ROMBIOS code being moved to its
> own file. It includes the claim cycle patch for secondary graphics
> card passthrough as well.
>    Remember to place your graphics card's firmware into
> tools/firmware/vgabios/ after each "make clean".
>
> Regards,
> Liwei
>
>
> On 20 May 2011 08:11, Gennady Marchenko <gennady.marchenko@gmail.com>
> wrote:
> > Hi Liwei!
> > Some days ago you post a report to xen-devel about your tries to run your
> > vga in pt mode on xen unstable.So could you share the last patched
> sources
> > are you tried to work?
> > Because I can't apply several patch to current unstable could you share
> it
> > please?
> > I'm already have done about IGD but can't PT the primary ati 5450 at all
> :(
> > Best wishes,
> > Gennady.
>

[-- Attachment #1.2: Type: text/html, Size: 5366 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2011-05-21 15:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BANLkTim7Ly7FB1V7GMZLyH=-wVMSdjzY8A@mail.gmail.com>
2011-05-20  6:08 ` Xen, ustable and VGA passthrough Liwei
2011-05-21 15:58   ` Gennady Marchenko [this message]
2011-05-22 11:28     ` Pavel Matěja
2011-05-23 13:20     ` Liwei
2011-05-22 12:00   ` Pavel Matěja

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=BANLkTimiyKZTdYd4phbe4x45kn_SfS+16Q@mail.gmail.com \
    --to=gennady.marchenko@gmail.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xieliwei@gmail.com \
    /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).