From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas K Lengyel Subject: Re: [RFC PATCH V3 11/12] xen/vm_event: Decouple vm_event and mem_access. Date: Fri, 6 Feb 2015 17:12:30 +0100 Message-ID: References: <1422567998-29995-1-git-send-email-tamas.lengyel@zentific.com> <1422567998-29995-12-git-send-email-tamas.lengyel@zentific.com> <54D1F8A6020000780005CB47@mail.emea.novell.com> <54D4DBC2020000780005DC21@mail.emea.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <54D4DBC2020000780005DC21@mail.emea.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Jan Beulich Cc: Tim Deegan , Kevin Tian , "wei.liu2@citrix.com" , Ian Campbell , Razvan Cojocaru , Stefano Stabellini , Eddie Dong , Ian Jackson , "xen-devel@lists.xen.org" , Steven Maresca , Andres Lagar-Cavilla , Jun Nakajima , "rshriram@cs.ubc.ca" , Keir Fraser , Daniel De Graaf , "yanghy@cn.fujitsu.com" List-Id: xen-devel@lists.xenproject.org On Fri, Feb 6, 2015 at 3:20 PM, Jan Beulich wrote: >>>> On 06.02.15 at 14:10, wrote: >> On Wed, Feb 4, 2015 at 10:47 AM, Jan Beulich wrote: >>>>>> On 29.01.15 at 22:46, wrote: >>>> --- a/xen/common/Makefile >>>> +++ b/xen/common/Makefile >>>> @@ -52,9 +52,10 @@ obj-y += tmem_xen.o >>>> obj-y += radix-tree.o >>>> obj-y += rbtree.o >>>> obj-y += lzo.o >>>> +obj-y += vm_event.o >>>> +obj-y += monitor.o >>> >>> Please make the (not) sorting situation worse than it already is - the >>> original intention was for entries to be alphabetically sorted here. >> >> I'm just going to sort the list in this patch to have everything in >> alphabetic order. > > In a prereq patch then you (hopefully) mean? Does reordering the already out-of-whack list worth its own patch? I just reordered it as part of this patch that adds to it. > >>>> +#include >>> >>> This can't be enough (nor can I see why it's needed here), or else ... >>> >>>> +/* Resumes the running of the VCPU, restarting the last instruction */ >>>> +void monitor_resume(struct domain *d); >>> >>> ... struct domain may end up being a forward reference (with scope >>> restricted to monitor_resume()). >> >> I'll revisit the headers needed for this one but it did build fine. > > Sure - presumably because the including sites included what is needed > up front. Probably. Looking at this header all it would need is xen/sched.h for the definition of struct domain. > Jan Thanks, Tamas