public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: Lennert Buytenhek <buytenh@wantstofly.org>,
	kvm@vger.kernel.org, Dirk Teurlings <dirk@upexia.nl>
Subject: Re: graphics card pci passthrough success report
Date: Thu, 13 Sep 2012 10:39:57 +0200	[thread overview]
Message-ID: <50519BDD.2020200@siemens.com> (raw)
In-Reply-To: <50517534.9030304@redhat.com>

On 2012-09-13 07:55, Gerd Hoffmann wrote:
>   Hi,
> 
>> - Apply the patches at the end of this mail to kvm and SeaBIOS to
>>   allow for more BAR space under 4G.  (The relevant BARs on the
>>   graphics cards _are_ 64 bit BARs, but kvm seemed to turn those
>>   into 32 bit BARs in the guest.)
> 
> Which qemu/seabios versions have you used?
> 
> qemu-1.2 (+ bundled seabios) should handle that just fine without
> patching.  There is no fixed I/O window any more, all memory space above
> lowmem is available for pci, i.e. if you give 2G to your guest
> everything above 0x80000000.
> 
> And if there isn't enougth address space below 4G (if you assign lot of
> memory to your guest so qemu keeps only the 0xe0000000 - 0xffffffff
> window free) seabios should try to map 64bit bars above 4G.
> 
>> - Apply the hacky patch at the end of this mail to SeaBIOS to
>>   always skip initialising the Radeon's option ROMs, or the VM
>>   would hang inside the Radeon option ROM if you boot the VM
>>   without the default cirrus video.
> 
> A better way to handle that would probably be to add an pci passthrough
> config option to not expose the rom to the guest.

-device pci-assign,option-rom=,...

> 
> Any clue *why* the rom doesn't run?

Maybe because we are not passing through the legacy VGA I/O ranges,
maybe because the card is accessing one of the famous side channels to
configure its mappings, and we do not virtualize them (as we usually do
not know them).

Jan

-- 
Siemens AG, Corporate Technology, CT RTC ITP SDP-DE
Corporate Competence Center Embedded Linux

  reply	other threads:[~2012-09-13  8:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12 15:50 graphics card pci passthrough success report Lennert Buytenhek
2012-09-13  5:55 ` Gerd Hoffmann
2012-09-13  8:39   ` Jan Kiszka [this message]
2012-09-13  9:40   ` Lennert Buytenhek
2012-09-13 17:05     ` Alex Williamson
2012-09-13 17:22       ` Lennert Buytenhek
2012-11-12 15:19 ` Vince Scott

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=50519BDD.2020200@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=buytenh@wantstofly.org \
    --cc=dirk@upexia.nl \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.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