xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: Stefano Stabellini <sstabellini@kernel.org>,
	George Dunlap <george.dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Julien Grall <julien.grall@arm.com>,
	Jan Beulich <jbeulich@suse.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2 2/2] p2m: split mem_access into separate files
Date: Wed, 11 Jan 2017 11:33:02 -0500	[thread overview]
Message-ID: <20170111163302.GB2266@char.us.oracle.com> (raw)
In-Reply-To: <CAErYnsi5AJ8xmzjdw-kKWByF3pfrx8Gmn_wcCV=U7JkN+gJGkw@mail.gmail.com>

On Tue, Jan 03, 2017 at 08:31:25AM -0700, Tamas K Lengyel wrote:
> On Fri, Dec 9, 2016 at 12:59 PM, Tamas K Lengyel
> <tamas.lengyel@zentific.com> wrote:
> > This patch relocates mem_access components that are currently mixed with p2m
> > code into separate files. This better aligns the code with similar subsystems,
> > such as mem_sharing and mem_paging, which are already in separate files. There
> > are no code-changes introduced, the patch is mechanical code movement.
> >
> > On ARM we also relocate the static inline gfn_next_boundary function to p2m.h
> > as it is a function the mem_access code needs access to.
> >
> > Signed-off-by: Tamas K Lengyel <tamas.lengyel@zentific.com>
> > Acked-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> 
> Acked-by: George Dunlap <george.dunlap@citrix.com>

Acked-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-01-11 16:33 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 19:59 [PATCH v2 1/2] arm/mem_access: adjust check_and_get_page to not rely on current Tamas K Lengyel
2016-12-09 19:59 ` [PATCH v2 2/2] p2m: split mem_access into separate files Tamas K Lengyel
2017-01-03 15:31   ` Tamas K Lengyel
2017-01-11 16:33     ` Konrad Rzeszutek Wilk [this message]
2017-01-30 21:11   ` Stefano Stabellini
2016-12-12  7:42 ` [PATCH v2 1/2] arm/mem_access: adjust check_and_get_page to not rely on current Jan Beulich
2016-12-12  7:47   ` Tamas K Lengyel
2016-12-12 11:46     ` Julien Grall
2016-12-12 18:42       ` Tamas K Lengyel
2016-12-12 19:11         ` Julien Grall
2016-12-12 19:41           ` Tamas K Lengyel
2016-12-12 21:28             ` Julien Grall
2016-12-12 23:47               ` Tamas K Lengyel
2016-12-13 12:50                 ` Julien Grall
2016-12-13 18:03                   ` Tamas K Lengyel
2016-12-13 18:39                   ` Tamas K Lengyel
2016-12-13 18:28                 ` Andrew Cooper
2016-12-13 18:41                   ` Julien Grall
2016-12-13 19:39                     ` Andrew Cooper
2016-12-14 12:05                       ` Julien Grall
2016-12-15  4:54                         ` George Dunlap
2016-12-15 16:16                           ` Julien Grall
2017-01-03 15:29 ` Tamas K Lengyel
2017-01-30 21:11 ` Stefano Stabellini

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=20170111163302.GB2266@char.us.oracle.com \
    --to=konrad.wilk@oracle.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --cc=tamas.lengyel@zentific.com \
    --cc=xen-devel@lists.xenproject.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 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).