From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] pci: 64bit bits
Date: Wed, 02 May 2012 18:57:23 +0300 [thread overview]
Message-ID: <4FA15963.7060608@redhat.com> (raw)
In-Reply-To: <4FA158CA.8060808@redhat.com>
On 05/02/2012 06:54 PM, Gerd Hoffmann wrote:
> On 05/02/12 17:33, Avi Kivity wrote:
> > On 05/02/2012 05:02 PM, Gerd Hoffmann wrote:
> >> Hi,
> >>
> >> seabios (master branch) just got 64bit pci support. When running out of
> >> address space in the pci memory window below 4G (0xe0000000+) seabios
> >> will map 64bit pci bars above 4G to make room below 4G.
> >>
> >> This patch series carries two little patches for qemu to adapt it to the
> >> seabios changes. First patch creates a memory window for the 64bit pci
> >> bars. Second patch adds a 64bit option to the ivshmem driver, which
> >> allows to use huge shared memory chunks.
> >
> > What happens if a pre-64-bit-pci guest boots on such a setup?
>
> If it worked before it should continue to work just fine. Note that the
> 64bit bars are only mapped above 4G in case there is not enough address
> space below 4G, so existing setups should never ever see bars mapped high.
I see. I guess it depends on the algorithm for selecting the BAR to be
evicted, but if everything fitted before, it should fit now as well. If
it didn't, then a different device may break in each of the two cases.
--
error compiling committee.c: too many arguments to function
prev parent reply other threads:[~2012-05-02 15:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 14:02 [Qemu-devel] [PATCH 0/2] pci: 64bit bits Gerd Hoffmann
2012-05-02 14:02 ` [Qemu-devel] [PATCH 1/2] pc: add pci64 memory hole Gerd Hoffmann
2012-05-02 15:31 ` Avi Kivity
2012-05-02 15:46 ` Gerd Hoffmann
2012-05-02 15:52 ` Avi Kivity
2012-05-02 14:02 ` [Qemu-devel] [PATCH 2/2] ivshmem: add 64bit option Gerd Hoffmann
2012-05-02 15:33 ` Avi Kivity
2012-05-02 15:33 ` [Qemu-devel] [PATCH 0/2] pci: 64bit bits Avi Kivity
2012-05-02 15:54 ` Gerd Hoffmann
2012-05-02 15:57 ` Avi Kivity [this message]
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=4FA15963.7060608@redhat.com \
--to=avi@redhat.com \
--cc=kraxel@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).