From: Gerd Hoffmann <kraxel@redhat.com>
To: "Kevin O'Connor" <kevin@koconnor.net>
Cc: Isaku Yamahata <yamahata@valinux.co.jp>,
Jan Kiszka <jan.kiszka@siemens.com>,
Alex Williamson <alex.williamson@redhat.com>,
seabios@seabios.org, kvm@vger.kernel.org
Subject: Re: [SeaBIOS] Graphics card pass-through working with two pass pci-initialization
Date: Mon, 06 Jun 2011 08:30:42 +0200 [thread overview]
Message-ID: <4DEC7412.80506@redhat.com> (raw)
In-Reply-To: <20110601223405.GB18369@morn.localdomain>
Hi,
> As Jan points out though, is a dynamic PCI region really needed?
> Those that need a large PCI region are also likely to need a large
> amount of memory. Maybe the space for PCI should just be increased.
Just changing it will not work as it will break live migration.
I think one option is to keep the piix-based pc as-is, with the address
space above 0xe0000000 being available for PCI, and make the room larger
for the upcoming q35-based pc, say starting at 0xc0000000. That will
give almost 1G address space. 256 MB are used by pci mmconfig though.
The other option is to make it configurable, which in turn requires a
dynamic PCI region.
cheers,
Gerd
next prev parent reply other threads:[~2011-06-06 6:31 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1306227933-4880-1-git-send-email-kraxel@redhat.com>
[not found] ` <1306227933-4880-2-git-send-email-kraxel@redhat.com>
[not found] ` <20110525023406.GG8517@valinux.co.jp>
[not found] ` <20110525043353.GH8517@valinux.co.jp>
[not found] ` <4DDCC7A5.60706@redhat.com>
[not found] ` <4DDCF9ED.5050208@redhat.com>
[not found] ` <4DDDDA8D.6080807@web.de>
[not found] ` <4DDDF62C.2010603@redhat.com>
2011-05-27 5:32 ` Graphics card pass-through working with two pass pci-initialization André Weidemann
2011-05-27 11:09 ` Jan Kiszka
2011-05-27 19:40 ` André Weidemann
2011-05-27 19:50 ` André Weidemann
2011-05-26 21:19 ` André Weidemann
2011-05-28 8:18 ` Jan Kiszka
2010-05-28 18:49 ` André Weidemann
2011-05-29 15:22 ` Jan Kiszka
2011-05-29 15:33 ` Avi Kivity
2011-05-29 19:30 ` André Weidemann
2011-05-29 20:51 ` Jan Kiszka
2011-05-30 7:34 ` Gerd Hoffmann
2011-05-30 9:58 ` Gerd Hoffmann
2011-05-31 2:29 ` [SeaBIOS] " Isaku Yamahata
2011-06-01 7:30 ` Gerd Hoffmann
2011-06-01 9:56 ` Alexander Graf
2011-06-01 10:20 ` Rudolf Marek
2011-06-01 13:47 ` Gerd Hoffmann
2011-06-01 14:40 ` Rudolf Marek
2011-06-01 22:15 ` Kevin O'Connor
2011-06-01 22:22 ` Yushu Yao
2011-06-01 11:13 ` Avi Kivity
2011-06-01 11:16 ` [SeaBIOS] " Alexander Graf
2011-06-01 11:18 ` Avi Kivity
2011-06-01 14:20 ` [SeaBIOS] " Isaku Yamahata
2011-06-01 14:31 ` Jan Kiszka
2011-06-01 14:36 ` Alex Williamson
2011-06-01 22:34 ` Kevin O'Connor
2011-06-06 6:30 ` Gerd Hoffmann [this message]
2011-06-07 8:05 ` Jan Kiszka
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=4DEC7412.80506@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=jan.kiszka@siemens.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=seabios@seabios.org \
--cc=yamahata@valinux.co.jp \
/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