xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Andres Lagar Cavilla <andres@lagarcavilla.org>
To: Tamas K Lengyel <tamas.lengyel@zentific.com>
Cc: keir@xen.org, Ian Campbell <ian.campbell@citrix.com>,
	Tim Deegan <tim@xen.org>, Ian Jackson <ian.jackson@eu.citrix.com>,
	Xen-devel <xen-devel@lists.xen.org>,
	stefano.stabellini@citrix.com, Jan Beulich <jbeulich@suse.com>,
	dgdegra@tycho.nsa.gov
Subject: Re: [PATCH RFC 1/7] xen: Relocate mem_access and mem_event into common.
Date: Mon, 25 Aug 2014 10:19:38 -0700	[thread overview]
Message-ID: <CADzFZPtj6P-Sb1KN9j-ia6RPiYFSb5JOPiW5y7AbcOawWks4jQ@mail.gmail.com> (raw)
In-Reply-To: <1408699832-13325-2-git-send-email-tamas.lengyel@zentific.com>


[-- Attachment #1.1: Type: text/plain, Size: 2242 bytes --]

On Fri, Aug 22, 2014 at 2:30 AM, Tamas K Lengyel <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.
>
> Signed-off-by: Tamas K Lengyel <tamas.lengyel@zentific.com>
>
Big patch and assuming code motion LGTM. Couple of observations though.

Snip...


> -        req->flags |= MEM_EVENT_FLAG_FOREIGN;
> -        ASSERT( !(req->flags & MEM_EVENT_FLAG_VCPU_PAUSED) );
>
Take the opportunity to downgrade the aggressiveness of this at some point
in this series. (I'd prefer to keep code motion patches as purely code
motion).

A faulty tool stack can brick a debug hypervisor. Unpleasant while dev/test.

Snip ...

>
> +++ b/xen/common/mem_access.c
> @@ -0,0 +1,137 @@
>
> +/******************************************************************************
> + * mem_access.c
> + *
> + * Memory access support.
> + *
> + * Copyright (c) 2011 Virtuata, Inc.
> + *
> + * This program is free software; you can redistribute it and/or modify
> + * it under the terms of the GNU General Public License as published by
> + * the Free Software Foundation; either version 2 of the License, or
> + * (at your option) any later version.
> + *
> + * This program is distributed in the hope that it will be useful,
> + * but WITHOUT ANY WARRANTY; without even the implied warranty of
> + * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
> + * GNU General Public License for more details.
> + *
> + * You should have received a copy of the GNU General Public License
> + * along with this program; if not, write to the Free Software
> + * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307
> USA
> + */
> +
> +
> +#include <xen/sched.h>
> +#include <xen/guest_access.h>
> +#include <xen/hypercall.h>
> +#include <asm/p2m.h>
> +#include <public/memory.h>
> +#include <xen/mem_event.h>
> +#include <xsm/xsm.h>
> +
> +#ifdef CONFIG_X86
>

Presumably this [will later be|should be] changed to consider CONFIG_ARM?

Many more like that one below with the same comment.

Thanks
Andres

>
> --
> 2.0.1
>
>

[-- Attachment #1.2: Type: text/html, Size: 3382 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2014-08-25 17:19 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 [this message]
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
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=CADzFZPtj6P-Sb1KN9j-ia6RPiYFSb5JOPiW5y7AbcOawWks4jQ@mail.gmail.com \
    --to=andres@lagarcavilla.org \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.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).