xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Dave McCracken <dcm@mccr.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Xen Developers List <xen-devel@lists.xensource.com>
Subject: Re: [Linux PATCH] Fix to hugepages to work around new PWT handling
Date: Wed, 9 Jun 2010 14:26:03 -0500	[thread overview]
Message-ID: <201006091426.03926.dcm@mccr.org> (raw)
In-Reply-To: <4C0FE359.1000305@goop.org>

On Wednesday, June 09, 2010, Jeremy Fitzhardinge wrote:
> >>> An additional fix here is to make sure the _PAGE_PRESENT bit is set
> >>> before hugepages does a mk_pte(), since Xen depends on that bit to
> >>> trigger the pfn->mfn translation.
> >>>
> >>>   
> >>>       
> >>>
> >> Why is the kernel creating a non-present mapping?  If it isn't present,
> >> why does it matter whether we do the pfn->mfn conversion?
> >>
> >>     
> >>
> > The hugepage function make_huge_pte() called mk_pte() to turn a page and
> > a  pgprot into a pte before it set PRESENT.  The PRESENT flag was set
> > after the pte was made.  This meant that the Xen version of the macro
> > did not see PRESENT so did not do the pfn_to_mfn().  My patch sets
> > PRESENT first so the right thing will happen.
> >
> >   
> 
> But in general kernel code shouldn't be just nakedly setting present on
> the pte without also remaking the whole thing.  That doesn't happen with
> normal ptes, and it probably shouldn't happen with huge ptes.  Forcing
> present on a pte at this level seems very bogus.   Why not change the
> upper code to set present if that's want it wants?
> 
> I'll skip this chunk for now.

Um, this is the upper level code.  The entire purpose of make_huge_pte is to 
construct a present huge pte from page and pgprot. The problem is that the 
original code makes the pte, then sets the present bit via pte_mkhuge().  This 
means the Xen-specific macro that triggers on present is misled and doesn't do 
the pfn_to_mfn().  Without this patch hugepages is handing pfns to the 
hypervisor to map instead of mfns.

Dave

  reply	other threads:[~2010-06-09 19:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-09 14:02 [Linux PATCH] Fix to hugepages to work around new PWT handling Dave McCracken
2010-06-09 18:21 ` Jeremy Fitzhardinge
2010-06-09 18:35   ` Dave McCracken
2010-06-09 18:54     ` Jeremy Fitzhardinge
2010-06-09 19:26       ` Dave McCracken [this message]
2010-06-24 10:05         ` Jeremy Fitzhardinge
2010-06-24 22:38           ` Dave McCracken

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=201006091426.03926.dcm@mccr.org \
    --to=dcm@mccr.org \
    --cc=jeremy@goop.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 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).