From: Ian Campbell <ian.campbell@citrix.com>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: Tim Deegan <tim@xen.org>, Julien Grall <julien.grall@linaro.org>,
Ian Jackson <ian.jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Andres Lagar-Cavilla <andres@lagarcavilla.org>,
Jan Beulich <JBeulich@suse.com>,
Daniel De Graaf <dgdegra@tycho.nsa.gov>,
Tamas K Lengyel <tklengyel@sec.in.tum.de>
Subject: Re: [PATCH v5 00/17] Mem_event and mem_access for ARM
Date: Mon, 15 Sep 2014 23:26:31 +0100 [thread overview]
Message-ID: <1410819991.6908.9.camel@hastur.hellion.org.uk> (raw)
In-Reply-To: <CAErYnsgx4mJfK7fnn1XXRgOqur1TAsNYAXga7Hn+3pxKvcT69A@mail.gmail.com>
On Wed, 2014-09-10 at 16:01 +0200, Tamas K Lengyel wrote:
> So I think up to here the series could go in afaic. Question
> is - does
> this make sense without the ARM parts?
>
> Thanks, Jan
>
>
> Without the ARM parts there is no technical need for it. On the other
> hand, there are many other series pending in the same general area so
> having this part merged would put everyone on the same footing to
> resolve conflicts and to move forward from.
I think it would be perfectly fine/useful for the generic parts to go in
before the ARM part is ready, it's harmless refactoring and it will
reduce the amount of stuff which is being needlessly resent as later
patches get reviewed (since this is quite a long series that's pretty
significant IMHO).
Also A series which moves code around can be a pain to rebase,
especially if other changes are happening in the surrounding code, I
think if it is ready it should go in.
Plus as you say it forms a basis for your's and other's ongoing
development.
Ian.
next prev parent reply other threads:[~2014-09-15 22:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 13:28 [PATCH v5 00/17] Mem_event and mem_access for ARM Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 01/17] xen: Relocate mem_access and mem_event into common Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 02/17] xen: Relocate p2m_mem_access_resume to mem_access common Tamas K Lengyel
2014-09-11 20:16 ` Julien Grall
2014-09-12 8:56 ` Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 03/17] xen: Relocate struct npfec definition into common Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 04/17] xen: Relocate mem_event_op domctl and access_op memop " Tamas K Lengyel
2014-09-10 13:44 ` Jan Beulich
2014-09-10 13:28 ` [PATCH v5 05/17] xen/mem_event: Clean out superfluous white-spaces Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 06/17] xen/mem_event: Relax error condition on debug builds Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 07/17] xen/mem_event: Abstract architecture specific sanity checks Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 08/17] xen/mem_access: Abstract architecture specific sanity check Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 09/17] xen/arm: p2m type definitions and changes Tamas K Lengyel
2014-09-11 20:25 ` Julien Grall
2014-09-12 8:15 ` Tamas K Lengyel
2014-09-12 19:23 ` Julien Grall
2014-09-12 20:25 ` Tamas K Lengyel
2014-09-11 20:49 ` Julien Grall
2014-09-12 8:31 ` Tamas K Lengyel
2014-09-12 19:41 ` Julien Grall
2014-09-12 20:20 ` Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 10/17] xen/arm: Add set access required domctl Tamas K Lengyel
2014-09-11 20:26 ` Julien Grall
2014-09-10 13:28 ` [PATCH v5 11/17] xen/arm: Implement domain_get_maximum_gpfn Tamas K Lengyel
2014-09-11 20:28 ` Julien Grall
2014-09-12 8:58 ` Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 12/17] xen/arm: Data abort exception (R/W) mem_events Tamas K Lengyel
2014-09-11 21:19 ` Julien Grall
2014-09-12 8:46 ` Tamas K Lengyel
2014-09-12 20:35 ` Julien Grall
2014-09-12 20:48 ` Tamas K Lengyel
2014-09-12 21:04 ` Julien Grall
2014-09-10 13:28 ` [PATCH v5 13/17] xen/arm: Instruction prefetch abort (X) mem_event handling Tamas K Lengyel
2014-09-11 21:23 ` Julien Grall
2014-09-12 8:34 ` Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 14/17] xen/arm: Enable the compilation of mem_access and mem_event on ARM Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 15/17] xen: Extend getdomaininfo to return the domain's max_gpfn Tamas K Lengyel
2014-09-10 13:48 ` Jan Beulich
2014-09-10 13:55 ` Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 16/17] tools/libxc: Allocate magic page for mem access on ARM Tamas K Lengyel
2014-09-10 13:28 ` [PATCH v5 17/17] tools/tests: Enable xen-access " Tamas K Lengyel
2014-09-11 21:29 ` Julien Grall
2014-09-12 8:50 ` Tamas K Lengyel
2014-09-12 9:01 ` Tamas K Lengyel
2014-09-10 13:51 ` [PATCH v5 00/17] Mem_event and mem_access for ARM Jan Beulich
2014-09-10 14:01 ` Tamas K Lengyel
2014-09-15 22:26 ` Ian Campbell [this message]
2014-09-16 8:00 ` Jan Beulich
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=1410819991.6908.9.camel@hastur.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=andres@lagarcavilla.org \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@citrix.com \
--cc=tamas.lengyel@zentific.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 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).