All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xensource.com>
To: Uli Meis <um@amd64.org>
Cc: xen-devel@lists.xensource.com, "Langsdorf,
	Mark" <mark.langsdorf@amd.com>, Jan Beulich <jbeulich@novell.com>
Subject: Re: [PATCH] Enable K8 GART as an IOMMU
Date: Wed, 14 Feb 2007 14:51:32 +0000	[thread overview]
Message-ID: <C1F8D274.965F%keir@xensource.com> (raw)
In-Reply-To: <20070214143305.GB6490@amd64.org>

On 14/2/07 14:33, "Uli Meis" <um@amd64.org> wrote:

> Usually, yes, the BIOS should allocate the aperture. However, on all
> systems I've tested on the BIOS allocated only 32MB (probably because
> they had no AGP). Sometimes it would even keep the memory location that
> was set on the last boot---potentially pointing to usable RAM.
> 
> The patch will only allocate the aperture from RAM if the BIOS reserved
> less than 64MB. In that case, it will also make the call to
> xen_create_contiguous_region. The memory is lost. There's also a boot
> mesage telling people that.

Might it typically be possible to find some free space in the hole just
below 4GB? I don't believe most BIOSes make effort to keep the RAM hole
small.

Looking back to the particular approach you have taken, expanding the static
argument arrays for this one particular user is not really desirable. It
would be better to do a dynamic GFP_ATOMIC allocation in the case that order
> MAX_CONTIG_ORDER. We want to avoid that in the general case because
GFP_ATOMIC allocations can fail, but this will be happening at start of day
when there should be no memory pressure.

 -- Keir

  reply	other threads:[~2007-02-14 14:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-12 17:47 [PATCH] Enable K8 GART as an IOMMU Langsdorf, Mark
2007-02-13  8:47 ` Jan Beulich
2007-02-13 23:19   ` Langsdorf, Mark
2007-02-14  9:21     ` Jan Beulich
2007-02-14 10:04     ` Keir Fraser
2007-02-14 14:33       ` Uli Meis
2007-02-14 14:51         ` Keir Fraser [this message]
2007-02-13 13:42 ` Muli Ben-Yehuda

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=C1F8D274.965F%keir@xensource.com \
    --to=keir@xensource.com \
    --cc=jbeulich@novell.com \
    --cc=mark.langsdorf@amd.com \
    --cc=um@amd64.org \
    --cc=xen-devel@lists.xensource.com \
    /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.