WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [PATCH] NextRIPS support for forthcoming AMD processors

To: Mark Langsdorf <mark.langsdorf@xxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] NextRIPS support for forthcoming AMD processors
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 15 Oct 2008 22:11:18 +0100
Cc:
Delivery-date: Wed, 15 Oct 2008 14:11:35 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <200810151603.10121.mark.langsdorf@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AckvCpCpz0n8Npr9Ed2JPwAWy6hiGQ==
Thread-topic: [Xen-devel] [PATCH] NextRIPS support for forthcoming AMD processors
User-agent: Microsoft-Entourage/11.4.0.080122
On 15/10/08 22:03, "Mark Langsdorf" <mark.langsdorf@xxxxxxx> wrote:

> Future versions of AMD processors will support a feature called
> NextRIPS or Next RIP Save.  This feature causes the processor
> to store the next sequential RIP of a guest in the VMCB on
> most instruction interrupts.  The hypervisor can use this
> information to determine how much memory to read to determine
> the intercepted instruction, modestly improving performance.
> The following patch implements support for this feature.
> 
> This patch has been stress tested at AMD for three weeks of
> continuous runtime and should not cause any regressions.

Why bother with a 'nrip' boot parameter? If this feature works, let's always
enable it. The check of vmexit code in svm_nextrip_is_valid() could also
perhaps be avoided? _get_instruction_length[_from_list]() is used only in a
very few cases, and in quite likely all those situations the nrip field
would actually be valid. Have you checked that, or are there in fact some
callers for whom nrip isn't guaranteed valid?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>