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

Re: [Xen-devel] [PATCH v2 00/12] Alternate p2m: support multiple copies of host p2m


  • To: "Lengyel, Tamas" <tlengyel@xxxxxxxxxxx>, Ed White <edmund.h.white@xxxxxxxxx>
  • From: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx>
  • Date: Wed, 24 Jun 2015 08:39:35 +0300
  • Cc: Ravi Sahita <ravi.sahita@xxxxxxxxx>, Wei Liu <wei.liu2@xxxxxxxxxx>, Tim Deegan <tim@xxxxxxx>, Ian Jackson <ian.jackson@xxxxxxxxxxxxx>, Xen-devel <xen-devel@xxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxx>, Andrew Cooper <andrew.cooper3@xxxxxxxxxx>, Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
  • Comment: DomainKeys? See http://domainkeys.sourceforge.net/
  • Delivery-date: Wed, 24 Jun 2015 05:39:50 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=bitdefender.com; b=XNLVz7UaJ4BI3fJbrchhr/IqWy3sWwLK5dhVvw1CPXI4p0WHzpt7BzI1w70cZ65cm4FXilOkUnX3ysqn1c8IJIuv0/xV/MNOb9AUPM30YsgRKBbFdnmmtM3pFpRc0pYmEcZfaPpplKyPaOho75Fb9bhiGz7i7lPmfp+kP/+P4O5EfGggYBlKyKtFgPNZCI+gXpSAa4+eUAIVPUoMH3IayzHu2dZ8AMkO6l5dDa96MSI7ypPQ7QSDyx0YDQN+HHXWe2n7i3zBJpRkSbXy0YiqZunCNM02uMtOhyhbVk4wWwdFJalYi5hgqBRdJI+5Isj4yuBwkbEYk5Ono8MDwAbfWQ==; h=Received:Received:Received:Received:Received:Subject:To:References:Cc:From:Message-ID:Date:User-Agent:MIME-Version: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 06/24/2015 12:27 AM, Lengyel, Tamas wrote:
> I've extended xen-access to exercise this new feature taking into
> account some of the current limitations. Using the altp2m_write|exec
> options we create a duplicate view of the default hostp2m, and instead
> of relaxing the mem_access permissions when we encounter a violation, we
> swap the view on the violating vCPU while also enabling MTF
> singlestepping. When the singlestep event fires, we use the response to
> that event to swap the view back to the restricted altp2m view.

That's certainly very interesting. I wonder what the benefits are in
this case over emulating the fault-causing instruction (other than
obviously not going through the emulator)? The altp2m method would
certainly be slower, since you need more round-trips from userspace to
the hypervisor (the EPT vm_event handling + the singlestep event,
whereas with emulation you just reply to the original vm_event).


Regards,
Razvan

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel


 


Rackspace

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