From: Avi Kivity <avi@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] pc: add pci64 memory hole
Date: Wed, 02 May 2012 18:52:14 +0300 [thread overview]
Message-ID: <4FA1582E.10503@redhat.com> (raw)
In-Reply-To: <4FA156E8.2040200@redhat.com>
On 05/02/2012 06:46 PM, Gerd Hoffmann wrote:
> On 05/02/12 17:31, Avi Kivity wrote:
> > On 05/02/2012 05:02 PM, Gerd Hoffmann wrote:
> >> This patch adds a address space hole for 64bit PCI ressources.
> >> It starts at 0x8000000000 (512 GB) and ends at 0x10000000000 (1 TB),
> >> thus has 512 GB in size. This matches what the seabios is doing
> >> (latest master branch).
> >
> > We should communicate this to seabios via fwcfg
>
> A dsdt entry is needed for the pci64 window (see
> http://code.coreboot.org/p/seabios/source/commit/482a020ec25f4cec655ddcb16b67c6f38b0844c0/),
> which makes it non-trivial to turn this into a runtime option ...
It's a function, isn't it? So all you need is a ASL driver for fwcfg
and an If().
> > It should also only apply to -M old.
>
> Is this the only reason you want this be runtime-switchable?
No. The BIOS and qemu shouldn't be making too many assumptions.
Certainly for Q35 we'd have the bios program qemu for the 64 bit hole.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2012-05-02 15:52 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 [this message]
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
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=4FA1582E.10503@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).