From: Lars Kurth <lars.kurth.xen@gmail.com>
To: Tamas K Lengyel <tamas.k.lengyel@gmail.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Lars Kurth <lars.kurth@citrix.com>, Wei Liu <wei.liu2@citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Julien Grall <julien.grall@arm.com>,
Jan Beulich <jbeulich@suse.com>,
Xen-devel <xen-devel@lists.xenproject.org>,
Keir Fraser <keir@xen.org>, Corneliu ZUZU <czuzu@bitdefender.com>
Subject: Re: [PATCH] vm_event: Implement ARM SMC events
Date: Wed, 13 Apr 2016 16:06:40 +0100 [thread overview]
Message-ID: <0307D576-2907-4B35-BFC9-FAD67E340C07@gmail.com> (raw)
In-Reply-To: <CABfawhn+8BCn9zipV=QDrQ8LU6FOpFkdKzizFhwSQqe+b0HmBg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1317 bytes --]
> On 13 Apr 2016, at 14:25, Tamas K Lengyel <tamas.k.lengyel@gmail.com> wrote:
> In the DRAKVUF system that's exactly what I do, I mark the page execute only so that the guest is unable to locate/overwrite injected breakpoints without notice. If it were to overwrite injected breakpoints with its own, then we would be able to tell that the trap is both for external and internal use. So there isn't much of an issue there. The main issue is with the racecondition in multi-vCPU guests when the purely external-use breakpoint has to be removed to allow the guest to continue. It can be solved nicely though with altp2m. I did a write-up for the Xen blog about it a couple months ago and sent it to publicity but has not appeared yet. Lars?
>
Tamas,
it hasn't because I was under the impression that Razvan and you disagreed on some aspects of the article. And then I forgot to chase either of you. I am happy with the article: feel free to upload it to the blog (or let me know, if I should) and press the button. Apologies
I think there are a couple of minor knit-picks, such as replace "In the latest release of Xen last summer several new features have been introduced" In "Xen 4.6 several new features have been introduced" ... assuming 4.6 is correct
I will reply to publicity
Regards
Lars
[-- Attachment #1.2: Type: text/html, Size: 1856 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-04-13 15:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-11 19:47 [PATCH] vm_event: Implement ARM SMC events Tamas K Lengyel
2016-04-12 4:31 ` Jan Beulich
2016-04-12 5:35 ` Razvan Cojocaru
2016-04-12 15:08 ` Tamas K Lengyel
2016-04-12 15:05 ` Tamas K Lengyel
2016-04-12 15:58 ` Julien Grall
2016-04-12 17:58 ` Tamas K Lengyel
2016-04-12 7:51 ` Corneliu ZUZU
2016-04-12 15:01 ` Tamas K Lengyel
2016-04-12 16:24 ` Julien Grall
2016-04-12 17:05 ` Corneliu ZUZU
2016-04-12 17:24 ` Tamas K Lengyel
2016-04-13 8:55 ` Corneliu ZUZU
2016-04-13 10:17 ` Andrew Cooper
2016-04-13 10:53 ` Corneliu ZUZU
2016-04-13 12:02 ` Andrew Cooper
2016-04-13 13:25 ` Tamas K Lengyel
2016-04-13 15:06 ` Lars Kurth [this message]
2016-04-13 15:13 ` Tamas K Lengyel
2016-04-13 10:52 ` Julien Grall
2016-04-13 11:02 ` Corneliu ZUZU
2016-04-13 15:32 ` Tamas K Lengyel
2016-04-12 14:55 ` Konrad Rzeszutek Wilk
2016-04-12 15:22 ` 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=0307D576-2907-4B35-BFC9-FAD67E340C07@gmail.com \
--to=lars.kurth.xen@gmail.com \
--cc=andrew.cooper3@citrix.com \
--cc=czuzu@bitdefender.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=julien.grall@arm.com \
--cc=keir@xen.org \
--cc=lars.kurth@citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tamas.k.lengyel@gmail.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).