All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@citrix.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: stefano.stabellini@citrix.com, dgdegra@tycho.nsa.gov,
	tim@xen.org, Tamas K Lengyel <tklengyel@sec.in.tum.de>,
	xen-devel@lists.xen.org
Subject: Re: [PATCH for-4.5 v12 0/3] Refactoring for future mem_event and mem_access support on ARM
Date: Mon, 6 Oct 2014 14:50:50 +0100	[thread overview]
Message-ID: <1412603450.14255.13.camel@citrix.com> (raw)
In-Reply-To: <20141002155056.GB1715@laptop.dumpdata.com>

On Thu, 2014-10-02 at 11:50 -0400, Konrad Rzeszutek Wilk wrote:
> On Wed, Oct 01, 2014 at 11:59:07AM +0100, Ian Campbell wrote:
> > On Mon, 2014-09-29 at 17:55 +0200, Tamas K Lengyel wrote:
> > > These patches are the refactoring and minor patches that will be required
> > > for future mem_access support on ARM that could be merged now.
> > 
> > Needs a release exception.
> > 
> > Konrad,
> > 
> > We'd like to get some of these into 4.5 so as to ease life for people
> > who want to backport ARM xenaccess and/or continue developing it for
> > 4.6.
> 
> Right.
> > 
> > I'm in favour of only "xen/xsm: Wrap mem_access blocks into
> > HAS_MEM_ACCESS ifdefs" and "xen/arm: Add p2m_set_permission and
> > p2m_shatter_page helpers." for now IMO, the new hypercall can/should
> > wait and come along with the user in 4.6.
> 
> OK.
> > 
> > Those two patches are a slight refactoring and a refactoring+ifdeffing
> > (refactorings/movements painful to rebase without introducing errors).
> > IMHO if they build then the risk of other regressions is slight.
> 
> Release-Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>

Thanks. I applied the p2m_set_perms one. Turns out the HAS_MEM_ACCESS
one was already in courtesy of Jan.

Ian.

      reply	other threads:[~2014-10-06 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-29 15:55 [PATCH for-4.5 v12 0/3] Refactoring for future mem_event and mem_access support on ARM Tamas K Lengyel
2014-09-29 15:55 ` [PATCH for-4.5 v12 1/3] xen/xsm: Wrap mem_access blocks into HAS_MEM_ACCESS ifdefs Tamas K Lengyel
2014-09-29 15:55 ` [PATCH for-4.5 v12 2/3] xen/arm: Implement domain_get_maximum_gpfn Tamas K Lengyel
2014-09-29 15:55 ` [PATCH for-4.5 v12 3/3] xen/arm: Add p2m_set_permission and p2m_shatter_page helpers Tamas K Lengyel
2014-10-01 10:59 ` [PATCH for-4.5 v12 0/3] Refactoring for future mem_event and mem_access support on ARM Ian Campbell
2014-10-02 15:50   ` Konrad Rzeszutek Wilk
2014-10-06 13:50     ` Ian Campbell [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=1412603450.14255.13.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=konrad.wilk@oracle.com \
    --cc=stefano.stabellini@citrix.com \
    --cc=tim@xen.org \
    --cc=tklengyel@sec.in.tum.de \
    --cc=xen-devel@lists.xen.org \
    /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.