linux-kernel - Re: [Qemu-devel] Re: ACPI error when mapping a 2GB BAR w/ 4GB of RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4C964382.9000602@redhat.com>
Date:	Sun, 19 Sep 2010 19:08:18 +0200
From:	Avi Kivity <avi@...hat.com>
To:	Cam Macdonell <cam@...ualberta.ca>
CC:	Chris Wright <chrisw@...hat.com>,
	"qemu-devel@...gnu.org Developers" <qemu-devel@...gnu.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [Qemu-devel] Re: ACPI error when mapping a 2GB BAR w/ 4GB of
 RAM

  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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/