All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell@eu.citrix.com>
To: avanzini.arianna@gmail.com
Cc: paolo.valente@unimore.it, stefano.stabellini@eu.citrix.com,
	dario.faggioli@citrix.com, xen-devel@lists.xen.org,
	julien.grall@citrix.com, etrudeau@broadcom.com,
	dgdegra@tycho.nsa.gov, viktor.kleinik@globallogic.com,
	andrii.tseglytskyi@globallogic.com
Subject: Re: [PATCH] xsm/flask: handle XEN_DOMCTL_memory_mapping for all architectures
Date: Tue, 9 Sep 2014 15:45:05 +0100	[thread overview]
Message-ID: <1410273905.8217.217.camel@kazak.uk.xensource.com> (raw)
In-Reply-To: <20140909131302.GA961@gmail.com>

On Tue, 2014-09-09 at 15:13 +0200, Arianna Avanzini wrote:
> On Tue, Sep 09, 2014 at 01:35:29PM +0100, Ian Campbell wrote:
> > On Mon, 2014-09-08 at 14:50 +0200, Arianna Avanzini wrote:
> > > On Mon, Sep 08, 2014 at 01:38:43PM +0100, Ian Campbell wrote:
> > > > On Mon, 2014-09-08 at 14:24 +0200, Arianna Avanzini wrote:
> > > > > On Mon, Sep 08, 2014 at 11:11:25AM +0100, Ian Campbell wrote:
> > > > > > On Thu, 2014-09-04 at 13:49 +0200, Arianna Avanzini wrote:
> > > > > > >         - Reworded commit message so that it explains what the patch does and
> > > > > > >           not the side effects of its absence.
> > > > > > 
> > > > > > Thanks.
> > > > > > 
> > > > > > Am I correct in assuming that this is replacing the previous #10/14 in
> > > > > > v12 but that a v13 is not on its way. IOW I can do the switcharoo during
> > > > > > commit (assuming the rest is acked, I didn't check yet)?
> > > > > 
> > > > > Yes, this patch is replacing #10/14. Unfortunately patches #11 to #14 still
> > > > > have to be acked. I was waiting for Andrii's feedback on Daniel De Graaf's
> > > > > comments about patch #11, and I'll resend patches from #12 to #14 (with
> > > > > your comments addressed) within today.
> > > > 
> > > > Thanks, it looks to me like #12-#14 can (once resent) go ahead without
> > > > #11 for the time being, is that right?
> > > 
> > > Yes exactly, that's what I thought too.
> > 
> > I've now applied this new replacement #10 plus the little three patch
> > series you sent corresponding to #12-#14 in this one.
> > 
> 
> Thank you for taking the time to review them!

Thanks for the contribution (and commitment!), I hadn't realised when I
committed that batch that it was effectively everything but some
xsm/flask loose ends, congrats!

Ian.

  reply	other threads:[~2014-09-09 14:45 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-30 16:29 [PATCH v12 00/14] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 01/14] arch/arm: add consistency check to REMOVE p2m changes Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 02/14] arch/arm: unmap partially-mapped memory regions Arianna Avanzini
2014-09-01 17:53   ` Julien Grall
2014-09-01 20:13     ` Arianna Avanzini
2014-09-01 23:47     ` [PATCH] " Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 03/14] arch/x86: warn if to-be-removed mapping does not exist Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 04/14] arch/x86: cleanup memory_mapping DOMCTL Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 05/14] xen/common: add ARM stub for the function memory_type_changed() Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 06/14] xen/x86: factor out map and unmap from the memory_mapping DOMCTL Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 07/14] xen/common: move the memory_mapping DOMCTL hypercall to common code Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 08/14] tools/libxl: parse optional start gfn from the iomem config option Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 09/14] tools/libxl: handle the iomem parameter with the memory_mapping hcall Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 10/14] xsm/flask: avoid spurious error messages when mapping I/O-memory Arianna Avanzini
2014-09-03 11:22   ` Ian Campbell
2014-09-03 11:30     ` Ian Campbell
2014-09-03 14:41   ` Daniel De Graaf
2014-09-04 11:49     ` [PATCH] xsm/flask: handle XEN_DOMCTL_memory_mapping for all architectures Arianna Avanzini
2014-09-08 10:11       ` Ian Campbell
2014-09-08 12:24         ` Arianna Avanzini
2014-09-08 12:38           ` Ian Campbell
2014-09-08 12:50             ` Arianna Avanzini
2014-09-09 12:35               ` Ian Campbell
2014-09-09 13:13                 ` Arianna Avanzini
2014-09-09 14:45                   ` Ian Campbell [this message]
2014-09-10 20:07                     ` Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 11/14] flask/policy: allow domU to use previously-mapped I/O-memory Arianna Avanzini
2014-09-03 11:21   ` Ian Campbell
2014-09-03 14:45     ` Daniel De Graaf
2014-09-05 23:25       ` Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 12/14] tools/libxl: explicitly grant access to needed I/O-memory ranges Arianna Avanzini
2014-09-03 11:26   ` Ian Campbell
2014-09-08 15:05     ` [PATCH 0/3] Separate the functions of the memory_mapping and iomem_permission DOMCTLs Arianna Avanzini
2014-09-08 15:05       ` [PATCH 1/3] tools/libxl: explicitly grant access to needed I/O-memory ranges Arianna Avanzini
2014-09-08 15:05       ` [PATCH 2/3] tools/libxl: cleanup the do_pci_add() function Arianna Avanzini
2014-09-08 15:05       ` [PATCH 3/3] xen/common: do not implicitly permit access to mapped I/O memory Arianna Avanzini
2014-08-30 16:29 ` [PATCH v12 13/14] tools/libxl: cleanup the do_pci_add() function Arianna Avanzini
2014-09-03 11:27   ` Ian Campbell
2014-08-30 16:29 ` [PATCH v12 14/14] xen/common: do not implicitly permit access to mapped I/O memory Arianna Avanzini
2014-09-03 12:15 ` [PATCH v12 00/14] Implement the XEN_DOMCTL_memory_mapping hypercall for ARM Ian Campbell
2014-09-03 13:55   ` Arianna Avanzini

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=1410273905.8217.217.camel@kazak.uk.xensource.com \
    --to=ian.campbell@eu.citrix.com \
    --cc=andrii.tseglytskyi@globallogic.com \
    --cc=avanzini.arianna@gmail.com \
    --cc=dario.faggioli@citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=etrudeau@broadcom.com \
    --cc=julien.grall@citrix.com \
    --cc=paolo.valente@unimore.it \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=viktor.kleinik@globallogic.com \
    --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.