From: George Dunlap <dunlapg@umich.edu>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Tamas K Lengyel <tamas@tklengyel.com>,
Wei Liu <wei.liu2@citrix.com>, Adrian Pop <apop@bitdefender.com>,
Sergej Proskurin <proskurin@sec.in.tum.de>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: [PATCH v2] x86/altp2m: Allow setting the #VE info page for an arbitrary VCPU
Date: Thu, 20 Sep 2018 16:28:50 +0100 [thread overview]
Message-ID: <CAFLBxZbuGqN93K9dCF5m+gEASqbDaPLLVLHxWeLFPk_2GX8BSA@mail.gmail.com> (raw)
In-Reply-To: <e2d290dd-0b8f-5a04-e5c3-1bcd244492ae@bitdefender.com>
On Thu, Sep 20, 2018 at 3:55 PM Razvan Cojocaru
<rcojocaru@bitdefender.com> wrote:
>
> On 9/20/18 5:42 PM, George Dunlap wrote:
> > I do have a question about your proposed use case. You're running
> > this in 'mixed' mode, right, and using the altp2m to hide a secure bit
> > of code from the operating system? What's to stop a rogue operating
> > system that doesn't want to be introspected from calling
> > HVMOP_altp2m_vcpu_enable_notify with INVALID_GFN to disable this?
>
> Nothing, but we're not running this in mixed mode. :)
> We're after 'external', for the very same reasons you've mentioned.
>
> Everything important is done in dom0-only. If there's something to be
> done that the in-guest agent would like, it has to ask the introspection
> agent in dom0 via VMCALL events.
OK, got it, thanks.
-George
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
prev parent reply other threads:[~2018-09-20 15:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 4:59 [PATCH v2] x86/altp2m: Allow setting the #VE info page for an arbitrary VCPU Adrian Pop
2018-09-04 20:40 ` Tamas K Lengyel
2018-09-04 20:58 ` Razvan Cojocaru
2018-09-05 6:56 ` Jan Beulich
2018-09-05 8:11 ` Razvan Cojocaru
2018-09-05 8:14 ` Razvan Cojocaru
2018-09-05 9:27 ` Jan Beulich
2018-09-05 16:28 ` Tamas K Lengyel
2018-09-05 16:40 ` Razvan Cojocaru
2018-09-05 18:40 ` Tamas K Lengyel
2018-09-05 18:45 ` Andrew Cooper
2018-09-05 22:27 ` Tamas K Lengyel
2018-09-20 8:11 ` Razvan Cojocaru
2018-09-20 8:14 ` Wei Liu
2018-09-20 8:16 ` Razvan Cojocaru
2018-09-20 8:22 ` Jan Beulich
2018-09-20 8:31 ` Wei Liu
2018-09-20 8:38 ` Razvan Cojocaru
2018-09-20 8:33 ` Jan Beulich
2018-09-05 18:53 ` Razvan Cojocaru
2018-09-20 14:42 ` George Dunlap
2018-09-20 14:55 ` Razvan Cojocaru
2018-09-20 15:28 ` George Dunlap [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=CAFLBxZbuGqN93K9dCF5m+gEASqbDaPLLVLHxWeLFPk_2GX8BSA@mail.gmail.com \
--to=dunlapg@umich.edu \
--cc=andrew.cooper3@citrix.com \
--cc=apop@bitdefender.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=proskurin@sec.in.tum.de \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.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 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.