 Home |
Products |
Support |
Community |
News |
xen-devel
Re: [Xen-devel] arch_set_info_guest() and cr1
| To: | Mukesh Rathor <mukesh.rathor@xxxxxxxxxx>, "Xen-devel@xxxxxxxxxxxxxxxxxxx" <Xen-devel@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [Xen-devel] arch_set_info_guest() and cr1 |
| From: | Keir Fraser <keir.xen@xxxxxxxxx> |
| Date: | Fri, 12 Aug 2011 07:16:39 +0100 |
| Cc: | |
| Delivery-date: | Thu, 11 Aug 2011 23:17:30 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; bh=TXNZjZZclds1mubH4lA/SOQbxRp3zgyCx5ogJa7akXk=; b=NYdA1g4fbzzHBuB8J5/wJ+YMB7E5gd9Tfzad3pOGn8NHQaS5RDqNJ34JO9eyhzxCLM mqLl1PJRQuBskvxN9z9G+J2VISTxHSt3jbuk4LYPTDlMDj13YbrB72/vDalFVjSJSE39 XC0xKyq6Exxmpy739OfUjAIpnJ43DDxs/Dh44= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| In-reply-to: | <20110811190315.1cc6afab@xxxxxxxxxxxxxxxxxxxx> |
| 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: | AcxYt2VgrQFeOKCHPkeL3RsB/FYsRg== |
| Thread-topic: | [Xen-devel] arch_set_info_guest() and cr1 |
| User-agent: | Microsoft-Entourage/12.30.0.110427 |
We stash the user-space CR3 value there (PV x86_64 guests have two CR3s). Of
course you should need only the guest kernel CR3.
K.
On 12/08/2011 03:03, "Mukesh Rathor" <mukesh.rathor@xxxxxxxxxx> wrote:
> Hi,
>
> Just wondering under what circumstances will cr1 be set in this
> function?
>
> int arch_set_info_guest(
> struct vcpu *v, vcpu_guest_context_u c)
> {
> .....
>
> #ifdef __x86_64__
> if ( c.nat->ctrlreg[1] ) <------
> {
> .....
>
>
>
> thanks,
> Mukesh
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Xen-devel] [xen-unstable test] 8423: tolerable FAIL, xen . org |
|---|---|
| Next by Date: | [Xen-devel] xen.frontend flag for higher display resolution (vnc) for HVM domU domains, Mark Schneider |
| Previous by Thread: | [Xen-devel] arch_set_info_guest() and cr1, Mukesh Rathor |
| Next by Thread: | Re: [Xen-devel] arch_set_info_guest() and cr1, Mukesh Rathor |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
