All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Beulich" <jbeulich@novell.com>
To: Mark Langsdorf <mark.langsdorf@amd.com>,
	Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: RE: [PATCH] Enable K8 GART as an IOMMU
Date: Wed, 14 Feb 2007 09:21:19 +0000	[thread overview]
Message-ID: <45D2E29F.76E4.0078.0@novell.com> (raw)
In-Reply-To: <1449F58C868D8D4E9C72945771150BDFD965F6@SAUSEXMB1.amd.com>

>>> "Langsdorf, Mark" <mark.langsdorf@amd.com> 14.02.07 00:19 >>>
>> >--- a/linux-2.6-xen-sparse/arch/i386/mm/hypervisor.c	Fri Feb 
>> 09 10:48:41 2007 +0000
>> >+++ b/linux-2.6-xen-sparse/arch/i386/mm/hypervisor.c	Fri Feb 
>> 09 16:32:04 2007 -0600
>> >@@ -252,7 +252,7 @@ static void contiguous_bitmap_clear(
>> > }
>> > 
>> > /* Protected by balloon_lock. */
>> >-#define MAX_CONTIG_ORDER 9 /* 2MB */
>> >+#define MAX_CONTIG_ORDER 16 /* 256MB */
>> > static unsigned long discontig_frames[1<<MAX_CONTIG_ORDER];
>> > static multicall_entry_t cr_mcl[1<<MAX_CONTIG_ORDER];
>> 
>> This seems dangerous to me.
>
>We need at least 64MB of contiguous memory for the aperture.

I think this should then be established by some other means. 256Mb
(and even the minimum of 64Mb that you say you need) is, for
contiguous memory, almost as good as no limit at all. Among other
reservations I have - how do you intend to make sure the hypervisor
even has a chance of fulfilling this big a request?

But I would certainly like to know Keir's opinion here, too.

Jan

  reply	other threads:[~2007-02-14  9:21 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 [this message]
2007-02-14 10:04     ` Keir Fraser
2007-02-14 14:33       ` Uli Meis
2007-02-14 14:51         ` Keir Fraser
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=45D2E29F.76E4.0078.0@novell.com \
    --to=jbeulich@novell.com \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=mark.langsdorf@amd.com \
    --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.