All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: xen-devel@lists.xensource.com
Subject: PAE & hypercall interfaces
Date: Wed, 18 May 2005 21:23:53 +0200	[thread overview]
Message-ID: <20050518192353.GA7474@bytesex> (raw)

  Hi folks,

As mentioned already in the pae patch mail, the xen hypercall
interfaces needs some changes.  The affected calls (hope I
didn't miss one) are:

 * do_mmuext_op
 * do_update_va_mapping & friends

The problem is that in PAE mode the page table entries are
64bit-sized instead of 32bit, and the current hypercall
interfaces allow to pass 32bit values only.

Current state is that the PAE code simply passes the lower
32 bits only, which will work fine as long as nobody attempts
to address memory above 4GB.  That obviously isn't an option,
the whole point of the PAE attempts is to use the memory above
4GB ;)

The options we have are:

  (1) make page table entrys 64bit wide everythere.
  (2) make page table entrys 64bit wide in PAE mode only.
  (3) pass two values: 32bit page frame number & flags.
  (4) others?

I'd prefeare option (1), option (3) is reasonable as well I
think.  I don't think (2) is a good idea, that will cause some
very nasty problems in case we'll try to allow non-PAE guests in
PAE mode.

Comments?

  Gerd

-- 
-mm seems unusually stable at present.
	-- akpm about 2.6.12-rc3-mm3

             reply	other threads:[~2005-05-18 19:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-18 19:23 Gerd Knorr [this message]
2005-05-19  8:20 ` PAE & hypercall interfaces Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-05-19  8:20 Ian Pratt

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=20050518192353.GA7474@bytesex \
    --to=kraxel@bytesex.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.