All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Scott Parish" <srparish@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com
Subject: Re: Xen 3.0 Status update
Date: Thu, 28 Jul 2005 21:43:20 +0000	[thread overview]
Message-ID: <20050728214320.GH4224@us.ibm.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D282829@liverpoolst.ad.cl.cam.ac.uk>

On Thu, Jul 28, 2005 at 11:39:46PM +0100, Ian Pratt wrote:

> > 
> > >  * Intel would get the standard s/w iommu working (just a case of 
> > > ensuring we have a machine contiguous aperture beloe 4GB -- 
> > the Linux 
> > > code currently uses the boot mem allocator rather than using 
> > > alloc_coherent, so it will need a little tweaking)
> > 
> > Yeah, i haven't had much luck so far.
> 
> I don't really understand why the aperture is allocated so early. I
> suspect its not actually used until the normal bootmem allocator is up. 
> 
> The slightly more fundamental problem is that we need a <4GB allocation
> zone in Xen, but since allocating the apperture is only currently an
> issue for dom0 it won't actually be a problem in practice. (something we
> need to address before driver domains come back)

I have a patch that introduces zones into xen, and a hypercall to
request dmaable memory, which i've made xen_contig_memory() use.
Unfortunately, there still seems to be some places where kmallocs are
done for dma buffers. (i tried putting all linux memory into ZONE_NORMAL
and caught a couple of these places)

If the zones patch would be helpful i could clean it up and post it.

sRp

-- 
Scott Parish
Signed-off-by: srparish@us.ibm.com

  reply	other threads:[~2005-07-28 21:43 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-28 22:39 Xen 3.0 Status update Ian Pratt
2005-07-28 21:43 ` Scott Parish [this message]
2005-07-28 22:57   ` Mark Williamson
2005-07-28 21:55     ` Scott Parish
  -- strict thread matches above, loose matches on Subject: below --
2005-07-29 11:16 Ian Pratt
2005-07-29 12:58 ` Gerd Knorr
2005-07-28 23:31 Ian Pratt
2005-07-28 23:05 Ian Pratt
2005-07-28 21:59 ` Scott Parish
2005-07-29  9:06 ` Gerd Knorr
2005-07-29 10:17   ` Keir Fraser
2005-07-28 21:35 Ian Pratt
2005-07-28 20:30 ` Scott Parish
2005-07-28 21:15 Ian Pratt
2005-07-28 20:09 ` Scott Parish
2005-07-28 21:01 Walker, Bruce J (HP-Labs)
2005-07-28 11:52 Ian Pratt
2005-07-29  2:30 ` aq
2005-07-27 23:34 Ian Pratt
2005-07-28  4:28 ` aq

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=20050728214320.GH4224@us.ibm.com \
    --to=srparish@us.ibm.com \
    --cc=m+Ian.Pratt@cl.cam.ac.uk \
    --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.