From: Avi Kivity <avi@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: Chris Wright <chrisw@redhat.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Qemu-devel] Re: ACPI error when mapping a 2GB BAR w/ 4GB of RAM
Date: Sun, 19 Sep 2010 19:08:18 +0200 [thread overview]
Message-ID: <4C964382.9000602@redhat.com> (raw)
In-Reply-To: <AANLkTikr7of6M142qTDkUx=2z-SUHWqOZd6hnC+BnEG4@mail.gmail.com>
On 09/17/2010 11:45 PM, Cam Macdonell wrote:
> > It seems most likely...< 2GB also means<= 1GB (which would fit in
> > the hole). Although, I have to admit, I'm not sure how seabios handles
> > the hole nowadays.
> >
> > What about 2GB with 32bit BAR?
>
> The bios seems to ignore it and the guest can't map it as it cannot
> find an alignment for it. Seems strange since with 1GB of RAM and 2GB
> BAR, everything should map below 4GB.
>
There are only two possible locations, 0-2GB and 2-4GB. The first
clashes with RAM, the second clashes with the bios and fixed-function
devices.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-09-19 17:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-17 20:00 ACPI error when mapping a 2GB BAR w/ 4GB of RAM Cam Macdonell
2010-09-17 20:00 ` [Qemu-devel] " Cam Macdonell
2010-09-17 20:04 ` Chris Wright
2010-09-17 20:04 ` [Qemu-devel] " Chris Wright
2010-09-17 20:52 ` Cam Macdonell
2010-09-17 20:53 ` Cam Macdonell
2010-09-17 21:15 ` Chris Wright
2010-09-17 21:45 ` Cam Macdonell
2010-09-19 17:08 ` Avi Kivity [this message]
2010-09-19 17:15 ` [Qemu-devel] " Avi Kivity
2010-09-19 17:15 ` Avi Kivity
2010-09-22 1:19 ` Robert Hancock
2010-09-22 1:19 ` Robert Hancock
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=4C964382.9000602@redhat.com \
--to=avi@redhat.com \
--cc=cam@cs.ualberta.ca \
--cc=chrisw@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.