From: Ian Campbell <ian.campbell@citrix.com>
To: CORNELIU ZUZU <czuzu@bitdefender.com>, xen-devel@lists.xen.org
Cc: Tamas K Lengyel <tamas@tklengyel.com>,
Stefano Stabellini <stefano.stabellini@citrix.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Subject: Re: [PATCH] ARM: Support for guest-request vm-events
Date: Thu, 28 Jan 2016 12:45:01 +0000 [thread overview]
Message-ID: <1453985101.26591.74.camel@citrix.com> (raw)
In-Reply-To: <56AA0B3E.9030106@bitdefender.com>
On Thu, 2016-01-28 at 14:36 +0200, CORNELIU ZUZU wrote:
> On 1/28/2016 1:23 PM, Ian Campbell wrote:
> > On Thu, 2016-01-28 at 13:17 +0200, Corneliu ZUZU wrote:
> > > This patch implements ARM support for guest-request vm-events.
> > > The code has been ported from x86 side w/ minor adjustments.
> > I've not looked at the patch yet, but if it only involves minor
> > adjustments
> > from the x86 side can some amount of it not be refactored into common
> > code?
> >
> > Ian.
> >
>
> At a first glance it seems to me that parts of monitor vm-events code
> could be moved to common.
> But it also seems that it would require a bit of effort and I'm not sure
> yet if the end result
> won't actually complicate implementation of monitor vm-events for other
> architectures in the future.
> Some of the monitor vm-events implemented are strictly architecture
> specific,
> e.g. VM_EVENT_REASON_MOV_TO_MSR will always be an x86-only vm-event, unless
> it is somehow generalized (maybe somehow merged w/
> VM_EVENT_REASON_WRITE_CTRLREG?).
> But *most* of them indeed don't directly have this kind of specificity,
> so it would make sense to make
> most of the code common, if possible.
That the sort of thing we would usually handle by having the common code
call into a arch_foo() to decode any non-common options.
> To me personally this seems like a good idea and I'd be willing to give
> it a try, but as I said,
> it might require some other changes of the code, including x86 changes.
> I was about to release another patch after this one to implement
> control-register writes
> vm-events for ARM, but I anticipate that doing this move first will
> actually benefit my effort in that
> direction as well (I think the patch code will get to be cleaner).
>
> So, shall I try it?
From my POV as an ARM maintainer I think this is the way to go. I've also
copied the VM EVENT maintainers in case they object for some reason.
I'd recommend always CCing Razvan and Tamas on this series, and considering
adding any new ARM files to the entry in MAINTAINERS (assuming they don't
object of course)
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-28 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 11:17 [PATCH] ARM: Support for guest-request vm-events Corneliu ZUZU
2016-01-28 11:23 ` Ian Campbell
2016-01-28 12:36 ` CORNELIU ZUZU
2016-01-28 12:45 ` Ian Campbell [this message]
2016-01-28 12:49 ` Razvan Cojocaru
2016-01-28 12:57 ` Corneliu ZUZU
2016-01-28 13:03 ` Ian Campbell
2016-01-28 14:10 ` Razvan Cojocaru
2016-01-31 0:12 ` 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=1453985101.26591.74.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=czuzu@bitdefender.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@citrix.com \
--cc=tamas@tklengyel.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.