All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave McCracken <dcm@mccr.org>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PROPOSED REMOVAL] PV guest superpage mappings
Date: Wed, 20 Jul 2011 11:13:39 -0500	[thread overview]
Message-ID: <201107201113.40313.dcm@mccr.org> (raw)
In-Reply-To: <CA4C6B79.1E3C9%keir.xen@gmail.com>

On Wednesday, July 20, 2011, Keir Fraser wrote:
> The PV superpage mapping feature has been in the hypervisor for a while
> now, but I'm not away of any use of this feature by an upstream guest
> kernel (e.g., and primarily of interest, pv_ops Linux). Am I mistaken, or
> is anyone looking into or interested in this? If the feature is unused we
> should remove it from the hypervisor in this development cycle, as it's
> untested and is nothing more than a maintenance burden and security risk.
> If the feature is only used by vendor patches, the hypervisor-side
> implementation belongs in that vendor's patch queues too.

I submitted a patch to use this feature to Jeremy for inclusion in the Linux 
kernel tree back when it first went into the hypervisor.  I was under the 
impression it was in his tree, and would eventually make its way into mainline 
Linux.

I must admit I moved on to other projects and did not follow it carefully.  
What is the current path for Xen-specific patches to be included in Linux 
mainline?

This feature is important for hugepages to work well in a Xen guest.

Dave McCracken
Oracle Corp.
dave.mccracken@oracle.com

  reply	other threads:[~2011-07-20 16:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-20 10:24 [PROPOSED REMOVAL] PV guest superpage mappings Keir Fraser
2011-07-20 16:13 ` Dave McCracken [this message]
2011-07-20 16:27   ` Ian Campbell
2011-07-20 16:47   ` Keir Fraser
2011-07-20 16:53     ` 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=201107201113.40313.dcm@mccr.org \
    --to=dcm@mccr.org \
    --cc=keir.xen@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 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.