xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: "Jan Beulich" <JBeulich@suse.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: keir@xen.org, ian.campbell@citrix.com, tim@xen.org,
	ian.jackson@eu.citrix.com, xen-devel@lists.xen.org,
	stefano.stabellini@citrix.com, andres@lagarcavilla.org,
	dgdegra@tycho.nsa.gov
Subject: Re: [PATCH RFC 1/7] xen: Relocate mem_access and mem_event into common.
Date: Tue, 26 Aug 2014 14:34:05 +0100	[thread overview]
Message-ID: <53FCA8ED020000780002DA05@mail.emea.novell.com> (raw)
In-Reply-To: <1408699832-13325-2-git-send-email-tamas.lengyel@zentific.com>

>>> On 22.08.14 at 11:30, <tamas.lengyel@zentific.com> wrote:
> In preparation to add support for ARM LPAE mem_event, relocate mem_access
> and mem_event into common Xen code. This patch makes no functional changes
> to the X86 side, for ARM mem_event and mem_access functions are just
> placeholder stubs.

"Makes no functional changes" is a little too weak a statement to
efficiently review such a big patch: Please clarify how much of the
non-benign changes (like asm/ -> xen/ include file path adjustments)
is really just code movement vs. where you needed to actually alter
the code.

>  xen/arch/x86/domctl.c            |   2 +-
>  xen/arch/x86/hvm/hvm.c           |  61 +---
>  xen/arch/x86/mm/Makefile         |   2 -
>  xen/arch/x86/mm/hap/nested_ept.c |   2 +-
>  xen/arch/x86/mm/hap/nested_hap.c |   2 +-
>  xen/arch/x86/mm/mem_access.c     | 133 --------
>  xen/arch/x86/mm/mem_event.c      | 705 --------------------------------------
>  xen/arch/x86/mm/mem_paging.c     |   2 +-
>  xen/arch/x86/mm/mem_sharing.c    |   2 +-
>  xen/arch/x86/mm/p2m-pod.c        |   2 +-
>  xen/arch/x86/mm/p2m-pt.c         |   2 +-
>  xen/arch/x86/mm/p2m.c            |   2 +-
>  xen/arch/x86/x86_64/compat/mm.c  |   4 +-
>  xen/arch/x86/x86_64/mm.c         |   4 +-
>  xen/common/Makefile              |   2 +
>  xen/common/domain.c              |   1 +
>  xen/common/mem_access.c          | 137 ++++++++
>  xen/common/mem_event.c           | 707 +++++++++++++++++++++++++++++++++++++++
>  xen/common/memory.c              |  62 ++++
>  xen/include/asm-arm/mm.h         |   1 -
>  xen/include/asm-x86/hvm/hvm.h    |   6 -
>  xen/include/asm-x86/mem_access.h |  39 ---
>  xen/include/asm-x86/mem_event.h  |  82 -----
>  xen/include/asm-x86/mm.h         |   2 -
>  xen/include/xen/mem_access.h     |  58 ++++
>  xen/include/xen/mem_event.h      | 141 ++++++++
>  xen/include/xen/mm.h             |   6 +
>  27 files changed, 1128 insertions(+), 1041 deletions(-)

This changes maintainership of a couple of files without also
adjusting ./MAINTAINERS.

>  delete mode 100644 xen/arch/x86/mm/mem_access.c
>  delete mode 100644 xen/arch/x86/mm/mem_event.c
>  create mode 100644 xen/common/mem_access.c
>  create mode 100644 xen/common/mem_event.c
>  delete mode 100644 xen/include/asm-x86/mem_access.h
>  delete mode 100644 xen/include/asm-x86/mem_event.h
>  create mode 100644 xen/include/xen/mem_access.h
>  create mode 100644 xen/include/xen/mem_event.h

Doesn't git have a mode where moves can be reflected as ordinary
diffs rather than as deletes/creates? While I'm not sure my scripts
would cope with applying such a patch, it surely would make review
easier (and perhaps even eliminate the question raised at the top).

Jan

  parent reply	other threads:[~2014-08-26 13:34 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22  9:30 [PATCH RFC 0/7] Mem_event and mem_access for ARM Tamas K Lengyel
2014-08-22  9:30 ` [PATCH RFC 1/7] xen: Relocate mem_access and mem_event into common Tamas K Lengyel
2014-08-25 17:19   ` Andres Lagar Cavilla
2014-08-26 10:52     ` Tamas K Lengyel
2014-08-26 12:42       ` Jan Beulich
2014-08-26 13:25         ` Tamas K Lengyel
2014-08-26 13:34   ` Jan Beulich [this message]
2014-08-26 14:42     ` Tamas K Lengyel
2014-08-26 15:32       ` Jan Beulich
2014-08-26 16:30         ` Tamas K Lengyel
2014-08-27  6:29           ` Jan Beulich
2014-08-22  9:30 ` [PATCH RFC 2/7] xen/mem_event: Clean out superflous white-spaces Tamas K Lengyel
2014-08-25 17:20   ` Andres Lagar Cavilla
2014-08-26 13:35   ` Jan Beulich
2014-08-26 13:59     ` Tamas K Lengyel
2014-08-22  9:30 ` [PATCH RFC 3/7] xen/arm: Enable the compilation of mem_access and mem_event on ARM Tamas K Lengyel
2014-08-25 17:25   ` Andres Lagar Cavilla
2014-08-26  8:32     ` Tamas K Lengyel
2014-08-26 13:51   ` Jan Beulich
     [not found]     ` <CAErYnshbvgxzBVSPu0mM3UUc0kr_zfENiHw9KmT=30-kpy_DZA@mail.gmail.com>
2014-08-26 14:38       ` Jan Beulich
2014-08-26 15:21         ` Tamas K Lengyel
2014-08-26 15:33           ` Jan Beulich
2014-08-22  9:30 ` [PATCH RFC 4/7] tools/libxc: Allocate magic page for mem access " Tamas K Lengyel
2014-08-22  9:30 ` [PATCH RFC 5/7] xen/arm: Data abort exception (R/W) mem_events Tamas K Lengyel
2014-08-22  9:30 ` [PATCH RFC 6/7] xen/arm: Instruction prefetch abort (X) mem_event handling Tamas K Lengyel
2014-08-22  9:30 ` [PATCH RFC 7/7] tools/tests: Enable xen-access on ARM Tamas K Lengyel

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=53FCA8ED020000780002DA05@mail.emea.novell.com \
    --to=jbeulich@suse.com \
    --cc=andres@lagarcavilla.org \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=keir@xen.org \
    --cc=stefano.stabellini@citrix.com \
    --cc=tamas.lengyel@zentific.com \
    --cc=tim@xen.org \
    --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 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).