From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tamas K Lengyel Subject: Re: [PATCH] arm/monitor vm-events: Implement guest-request support Date: Fri, 19 Feb 2016 09:02:59 -0700 Message-ID: References: <1455824116-13783-1-git-send-email-czuzu@bitdefender.com> <56C7341402000078000D427C@prv-mh.provo.novell.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============5035825211187680118==" Return-path: In-Reply-To: <56C7341402000078000D427C@prv-mh.provo.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: Keir Fraser , Ian Campbell , Razvan Cojocaru , Andrew Cooper , Xen-devel , Stefano Stabellini , Corneliu ZUZU List-Id: xen-devel@lists.xenproject.org --===============5035825211187680118== Content-Type: multipart/alternative; boundary=001a114e6724fc7f4c052c219d8f --001a114e6724fc7f4c052c219d8f Content-Type: text/plain; charset=UTF-8 On Fri, Feb 19, 2016 at 7:26 AM, Jan Beulich wrote: > >>> On 18.02.16 at 20:35, wrote: > > --- > > MAINTAINERS | 1 + > > xen/arch/arm/hvm.c | 8 +++ > > xen/arch/x86/hvm/event.c | 116 > ++++++---------------------------------- > > xen/arch/x86/hvm/hvm.c | 1 + > > xen/arch/x86/monitor.c | 14 ----- > > xen/arch/x86/vm_event.c | 1 + > > xen/common/Makefile | 2 +- > > xen/common/hvm/Makefile | 3 +- > > xen/common/hvm/event.c | 96 +++++++++++++++++++++++++++++++++ > > So here you _again_ try to introduce something HVM-ish for ARM. > Why? Why can't this code live in common/vm_event.c? > I too am wondering if this is the right way to architect this. It would be better to move the guest-requested stuff into the generic vm_event component as it doesn't seem to be HVM specific other then it using an HVMOP hypercall to be triggered. Tamas --001a114e6724fc7f4c052c219d8f Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, Feb 19, 2016 at 7:26 AM, Jan Beulich <JBeulich@suse.com>= ; wrote:
>>= > On 18.02.16 at 20:35, <czu= zu@bitdefender.com> wrote:
> ---
>=C2=A0 MAINTAINERS=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0 =C2=A01 +
>=C2=A0 xen/arch/arm/hvm.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 |=C2=A0 =C2=A08 +++
>=C2=A0 xen/arch/x86/hvm/event.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 | 116 ++++++= ----------------------------------
>=C2=A0 xen/arch/x86/hvm/hvm.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0= =C2=A01 +
>=C2=A0 xen/arch/x86/monitor.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0= 14 -----
>=C2=A0 xen/arch/x86/vm_event.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0= =C2=A01 +
>=C2=A0 xen/common/Makefile=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0|=C2=A0 =C2=A02 +-
>=C2=A0 xen/common/hvm/Makefile=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0|=C2=A0= =C2=A03 +-
>=C2=A0 xen/common/hvm/event.c=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 |=C2=A0= 96 +++++++++++++++++++++++++++++++++

So here you _again_ try to introduce something HVM-ish for ARM.
Why? Why can't this code live in common/vm_event.c?

I too am wondering if this is the right wa= y to architect this. It would be better to move the guest-requested stuff i= nto the generic vm_event component as it doesn't seem to be HVM specifi= c other then it using an HVMOP hypercall to be triggered.

Tamas

--001a114e6724fc7f4c052c219d8f-- --===============5035825211187680118== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel --===============5035825211187680118==--