xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Kaustubh Kabra <kabrakaustubh@gmail.com>
To: xen-devel@lists.xensource.com
Subject: Re: Re: [Linux PATCH] Make hugepages work in current git tree
Date: Thu, 10 Feb 2011 04:51:43 -0800 (PST)	[thread overview]
Message-ID: <1297342303892-3379235.post@n5.nabble.com> (raw)
In-Reply-To: <201004301434.48409.dcm@mccr.org>


Sir, attached two patch files for jeremy-kernel 2.6.32.27 and xen-4.0.1.

Current status ,I have the required huge pages' mfn (reserved before dom 0
boots )which we pass on from hypervisor to domain to enable it to use this
mfn to make required PTE .

The problem lies that domain is unable to modify the PMD (as mentioned in
above conversation) which contains this PTE entry as it lies in guest
read-only memory as shown in xen's  config.h file.

So,we tried passing this PMD entry in a hypercall to the hypervisor to
modify PMD accordingly but while allocation xen crashes.

This is where we are stuck now.
http://xen.1045712.n5.nabble.com/file/n3379235/jeremy2-6-32-27.patch
jeremy2-6-32-27.patch 
http://xen.1045712.n5.nabble.com/file/n3379235/xen-patch.patch
xen-patch.patch 
-- 
View this message in context: http://xen.1045712.n5.nabble.com/Linux-PATCH-Make-hugepages-work-in-current-git-tree-tp2540492p3379235.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

      reply	other threads:[~2011-02-10 12:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-28 14:08 [Linux PATCH] Make hugepages work in current git tree Dave McCracken
2010-04-29 19:30 ` Jeremy Fitzhardinge
2010-04-29 21:43   ` Dave McCracken
2010-04-29 21:51     ` Jeremy Fitzhardinge
2010-04-30 19:34       ` Dave McCracken
2011-02-10 12:51         ` Kaustubh Kabra [this message]

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=1297342303892-3379235.post@n5.nabble.com \
    --to=kabrakaustubh@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).