All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Brad Plant <bplant@iinet.net.au>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>
Subject: Re: Xen dev help required
Date: Wed, 18 Feb 2009 17:42:49 -0800	[thread overview]
Message-ID: <499CB919.3020801@goop.org> (raw)
In-Reply-To: <20090219104935.1a22464b@daedalus>

Brad Plant wrote:
> Hi list,
>
> I was hoping some people "in the know" about how the hypervisor works etc could take a look at the thread below and hopefully offer some advice.
>
> http://forums.grsecurity.net/viewtopic.php?f=1&t=2063&p=8759#p8745
>
> The PaX developers are trying to get their patch to work on a 2.6.28 paravirt_ops kernel. They already have PaX working with a 2.6.27 paravirt_ops kernel, but a recent change to the PaX patch, specifically to map up to 4GB initially in the identity map is causing the kernel to panic when booted under xen.
>
> Any help on the matter would be greatly appreciated by all.
>   

Looks like what they're trying to do is pretty redundant; Xen is pretty 
good at protecting the kernel's pagetables for it.  From just looking at 
that piece of thread, I'm guessing they're creating writeable aliases of 
the pagetable pages, which Xen won't allow.

Yeah, this one:
|(XEN) mm.c:794:d35 Attempt to create linear p.t. with write perms

|    J

  reply	other threads:[~2009-02-19  1:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 23:49 Xen dev help required Brad Plant
2009-02-19  1:42 ` Jeremy Fitzhardinge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-18 23:41 Brad Plant

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=499CB919.3020801@goop.org \
    --to=jeremy@goop.org \
    --cc=bplant@iinet.net.au \
    --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.