All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hollis Blanchard <hollisb@us.ibm.com>
To: Keir Fraser <keir@xensource.com>
Cc: xen-ia64-devel <xen-ia64-devel@lists.xensource.com>,
	xen-devel <xen-devel@lists.xensource.com>,
	xen-ppc-devel <xen-ppc-devel@lists.xensource.com>
Subject: Re: dom0 auto-translate mmap()
Date: Mon, 11 Jun 2007 12:50:15 -0500	[thread overview]
Message-ID: <1181584215.20281.41.camel@basalt> (raw)
In-Reply-To: <C2933D88.107B3%keir@xensource.com>

On Mon, 2007-06-11 at 17:57 +0100, Keir Fraser wrote:
> 
> 
> On 11/6/07 17:51, "Keir Fraser" <keir@xensource.com> wrote:
> 
> >> The net is that I would like to remove the above test. I wonder why it
> >> was added in the first place? Somebody has a privileged autotranslate
> >> domain and mistakenly tried to run the domain building tools?
> > 
> > Interesting. How does this work for ia64 currently? I think ia64 always runs
> > in auto-translate mode.
> 
> Oh, I see they have their own mmap function. Yes, I think the test can
> safely be removed.

Hmm, the ia64 privcmd_mmap() is certainly interesting. It is another
approach to the same problem: they explicitly pre-register some of the
gpfn space to the appropriate mfn space.

Long-term, that's probably a better approach, since it only hijacks gpfn
space as needed, rather than halving the physical address space. For the
moment though, it also looks like a fair amount of more code... :)

-- 
Hollis Blanchard
IBM Linux Technology Center

  reply	other threads:[~2007-06-11 17:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-11 16:42 dom0 auto-translate mmap() Hollis Blanchard
2007-06-11 16:51 ` Keir Fraser
2007-06-11 16:57   ` Keir Fraser
2007-06-11 17:50     ` Hollis Blanchard [this message]
2007-06-11 18:14 ` [XenPPC] " Jimi Xenidis

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=1181584215.20281.41.camel@basalt \
    --to=hollisb@us.ibm.com \
    --cc=keir@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-devel@lists.xensource.com \
    --cc=xen-ppc-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.