xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Razvan Cojocaru <rzvncj@gmail.com>
To: Tim Deegan <tim@xen.org>
Cc: Andres Lagar-Cavilla <andreslc@gridcentric.ca>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH V2] mem_event: Allow emulating an instruction that caused a page fault
Date: Tue, 22 Jan 2013 16:45:34 +0200	[thread overview]
Message-ID: <50FEA60E.2000503@gmail.com> (raw)
In-Reply-To: <20130122142644.GB87324@ocelot.phlegethon.org>

> The only properly safe way to allow exactly one exception to your rules
> is to emulate the instruction in user-space.  (Well, that or somehow
> move your policy into Xen and do the emulation there, but I'm quite
> strongly opposed to that).

Is there an example of that somewhere in the Xen source code tree?

> If you're just using this to gather statistics about how often a page
> gets written, you could use sampling; you don't need to see _every_
> write.

I'm not gathering statistics.

> It might be helpful if you could give us a clear description of exactly
> what problem you're trying to solve.

I'm watching for suspicious activity on the domU. If any occurs, the 
domU should be paused (at least the VCPU in question). A dom0 userspace 
application should decide what constitutes suspicious activity, with (1) 
the least possible slowing down of the domU, and (2) with as little 
"false positive" writes allowed as possible (ideally zero, if there's a 
way that doesn't go against requirement (1)).

Thanks,
Razvan Cojocaru

  reply	other threads:[~2013-01-22 14:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.21624.1358431706.1399.xen-devel@lists.xen.org>
2013-01-17 15:38 ` [PATCH V2] mem_event: Allow emulating an instruction that caused a page fault Andres Lagar-Cavilla
2013-01-17 15:50   ` Razvan Cojocaru
2013-01-21 23:13   ` Razvan Cojocaru
2013-01-22 12:31     ` Tim Deegan
2013-01-22 12:53       ` Razvan Cojocaru
2013-01-22 13:20         ` Tim Deegan
2013-01-22 13:47           ` Razvan Cojocaru
2013-01-22 14:02             ` Andres Lagar-Cavilla
2013-01-22 14:22               ` Razvan Cojocaru
2013-01-22 14:26             ` Tim Deegan
2013-01-22 14:45               ` Razvan Cojocaru [this message]
2013-01-24 11:05                 ` Tim Deegan
2013-01-24 11:34                   ` Razvan Cojocaru
2013-01-17 14:02 Razvan Cojocaru

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=50FEA60E.2000503@gmail.com \
    --to=rzvncj@gmail.com \
    --cc=andreslc@gridcentric.ca \
    --cc=tim@xen.org \
    --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 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).