[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH RFC 0/9] Basic guest memory introspection support

  • To: Jan Beulich <JBeulich@xxxxxxxx>
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Wed, 02 Jul 2014 17:50:11 +0300
  • Cc: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Wed, 02 Jul 2014 14:49:31 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=HZbRuCPdxxboTy/ke2uGk4TJNvuJVED22UUg1mP3jweYiPPynrzDHOTfbWXYgqMuLkvXP2X6k+am4AG8vqaoVftK4zlK7nagSr0sGMoRkcxD4KYb/Jp5N0vi1Efbu3QYeVVEPdlXMhhTzNZbaI/n4tvWNN+y0AvBcbpc2J/etzFKew+lxfGxn2lsyEjYr+vDAw3Adpo4Zn6K9XMNnk8BPocCr1vlO1KrY6ZedNc1/3LyrUgu0viUnSuTxO93PrAS5/KFLNVb76ZCdd0SpIPAfNNDrnoOf6QrevLimz6xGOkbvwiAtH1LWb25h59AniLc8csxcs9QGnIgLsbpm59zkA==; h=Received:Received:Received:Received:Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-BitDefender-Scanner:X-BitDefender-Spam:X-BitDefender-SpamStamp:X-BitDefender-CF-Stamp;
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

On 07/02/2014 05:30 PM, Jan Beulich wrote:
>>>> On 02.07.14 at 15:34, <rcojocaru@xxxxxxxxxxxxxxx> wrote:
>> 4. Add an additional mem_event type, namely a VMCALL event - in order to
>> do its work, our application occasionally triggers VMCALLs in the guest.
> That seems like bending the mem_event interface quite a bit - VMCALL
> isn't really memory (or event) specific.

First, thank you for the reply.

I don't disagree that it's somewhat bending mem_event, however in the
context of our application it became necessary to know exactly when a
triggered VMCALL occured, so conceptually this was a noteworthy event
for us.

As for using mem_event for it, we chose it because it seems to be the
closest thing to a standard Xen way of handling events, it is quite
stable, and we thought it might not be such a stretch since there's also

We thought that adding an extra mem_event type would solve the problem
while adding as little unnecessary complications to the existing code,
and making it as trouble-free as possible for Xen maintainers / testers.

Thanks again,
Razvan Cojocaru

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.