From: "Mihai Donțu" <mdontu@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Razvan Cojocaru <rcojocaru@bitdefender.com>, xen-devel@lists.xen.org
Subject: Re: [PATCH RFC 0/9] Basic guest memory introspection support
Date: Wed, 2 Jul 2014 17:52:38 +0300 [thread overview]
Message-ID: <20140702175238.1ff1de57@bitdefender.com> (raw)
In-Reply-To: <20140702175053.3f2e0ecd@bitdefender.com>
[-- Attachment #1.1: Type: text/plain, Size: 748 bytes --]
On Wednesday 02 July 2014 17:50:53 Mihai Donțu wrote:
> On Wed, 02 Jul 2014 15:30:24 +0100 Jan Beulich wrote:
> > >>> On 02.07.14 at 15:34, <rcojocaru@bitdefender.com> 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.
>
> Indeed. We've used that existing communication channel to carry MSR
> change events as well. Maybe in the feature we could rework the whole
> thing (mem, MSRs, VMCALL) under a new name, like 'guest events'.
Corrected Răzvan's email address.
--
Mihai DONȚU
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
prev parent reply other threads:[~2014-07-02 14:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-02 13:34 [PATCH RFC 0/9] Basic guest memory introspection support Razvan Cojocaru
2014-07-02 14:30 ` Jan Beulich
2014-07-02 14:50 ` Razvan Cojocaru
2014-07-02 14:50 ` Mihai Donțu
2014-07-02 14:52 ` Mihai Donțu [this message]
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=20140702175238.1ff1de57@bitdefender.com \
--to=mdontu@bitdefender.com \
--cc=JBeulich@suse.com \
--cc=rcojocaru@bitdefender.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.