xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Liwei <xieliwei@gmail.com>
To: "Pasi Kärkkäinen" <pasik@iki.fi>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: VGA passthrough on unstable
Date: Fri, 6 May 2011 01:59:29 +0800	[thread overview]
Message-ID: <BANLkTikjgWFbX7bi-B=mrc3=GpAmn4_aAQ@mail.gmail.com> (raw)
In-Reply-To: <20110505170632.GR32595@reaktio.net>

On 6 May 2011 01:06, Pasi Kärkkäinen <pasik@iki.fi> wrote:
>
> Yeah I didn't mean you to post the actual BIOS image file,
> only the Xen patches that support loading the BIOS image from specified file.
> (so that people don't have to hardcode the BIOS image to custom binaries).
>

That I have not started and will probably need some work integrating a
hex converter (or maybe require the user to supply the converted
binary) and finding out how xen/qemu handles the configuration files.

>
> I think other people who tried those patches (and got them working)
> had to modify the vbar/pbar ranges to match their hardware..
>
> btw the error message above mentions alignment.. did you try the
> alignment option for xen-pciback?
>
> -- Pasi
>
>

Where do I modify the ranges? Is it the bunch of DWordMemory macros in
dsdt.asl? And how do I determine the range that I must use?

I did a quick test by appending pci=resource_alignment=[all the
pciback devices] to my boot command, it didn't seem to trigger any
changes in my bootlog nor the guest booting, is that the right option?

Come to think of it, why are there errors for BDF 00:05.0 and 00:06.0
when only 01:00.0 and 01:00.1 is passed in?

  reply	other threads:[~2011-05-05 17:59 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-03  6:29 VGA passthrough on unstable Liwei
2011-05-03 15:20 ` Liwei
2011-05-05 11:33 ` Liwei
2011-05-05 15:20   ` Pasi Kärkkäinen
2011-05-05 16:56     ` Liwei
2011-05-05 17:06       ` Pasi Kärkkäinen
2011-05-05 17:59         ` Liwei [this message]
2011-05-05 18:12           ` Pasi Kärkkäinen
2011-05-05 18:28             ` Liwei
2011-05-05 18:33               ` Pasi Kärkkäinen
2011-05-05 18:42                 ` Liwei
2011-05-05 18:49                   ` Pasi Kärkkäinen
2011-05-09  0:26                     ` Liwei
2011-05-09 17:14     ` Javier
2011-05-10 13:12       ` JavMV
2011-05-10 13:12       ` JavMV
2011-05-10 17:55         ` Konrad Rzeszutek Wilk
2011-05-10 13:12       ` JavMV
  -- strict thread matches above, loose matches on Subject: below --
2011-05-17 23:14 Liwei
2011-05-24 15:35 Liwei
2011-05-24 15:44 ` Liwei
2011-05-31 14:59 Liwei

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='BANLkTikjgWFbX7bi-B=mrc3=GpAmn4_aAQ@mail.gmail.com' \
    --to=xieliwei@gmail.com \
    --cc=pasik@iki.fi \
    --cc=xen-devel@lists.xensource.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).