From: Keir Fraser <keir.xen@gmail.com>
To: "Nimgaonkar, Satyajeet" <SatyajeetNimgaonkar@my.unt.edu>,
Tim Deegan <Tim.Deegan@citrix.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: Read value of CR3 from DomU VCPU
Date: Fri, 06 May 2011 17:57:39 +0100 [thread overview]
Message-ID: <C9E9E714.176B5%keir.xen@gmail.com> (raw)
In-Reply-To: <12871952FC0E29439F861FA745BCDD850D34A796@CH1PRD0104MB027.prod.exchangelabs.com>
On 06/05/2011 17:33, "Nimgaonkar, Satyajeet"
<SatyajeetNimgaonkar@my.unt.edu> wrote:
> Hi Tim,
> I looked at the xc_translate_foreign_address() in
> tools/libxc/xc_pagetab.c and tried to emulate it. The function below void
> do_jeet1() is a hypercall handler function for my custom hypercall to get the
> value of CR3 from the guest VCPU. But when I try to call this hypercall, my
> machine automatically boots up. Any thoughts?
>
> void do_jeet1(void){
>
> unsigned long pgdaddr;
> vcpu_guest_context_u ctx;
> printk ("Successfull Hypercall made to __HYPERVISOR_jeet1\n");
>
> pgdaddr = xen_cr3_to_pfn(ctx.nat->ctrlreg[3]);
How experienced are you with C? This is so very obviously broken
(dereferencing field 'nat' in uninitialised union 'ctx'), it's surprising
gcc didn't warn and thereby fail the build. It's not really the purpose of
this list to school you.
-- Keir
> printk ("PGDADDR:%lx\n", pgdaddr);
>
> }
>
> Thanks.
>
> Regards,
> Jeet
>
> ________________________________________
> From: Tim Deegan [Tim.Deegan@citrix.com]
> Sent: Thursday, May 05, 2011 2:33 AM
> To: Nimgaonkar, Satyajeet
> Cc: xen-devel@lists.xensource.com
> Subject: Re: [Xen-devel] Read value of CR3 from DomU VCPU
>
> At 21:28 +0100 on 04 May (1304544537), Nimgaonkar, Satyajeet wrote:
>> Hi,
>> I intend to map the DomU kernel memory to the Dom0 using the
>> function xc_map_foreign_range(). For this I need the machine frame
>> number (mfn) for the page I want to map. To get the value of mfn I want
>> to read the value of cr3 from the DomU Vcpu data structure i.e. the
>> value of ctrlreg[3] from a vcpu_guest_context object.
>
> Look at xc_translate_foreign_address() in tools/libxc/xc_pagetab.c; it
> does VA->MFN translations, including extracting CR3.
>
> Cheers,
>
> Tim.
>
>> Also I have implemented a hypercall and wish to read the cr3 value in the
>> hypercall handler.
>> Can anyone share some information regarding how read the cr3 value. Any code
>> examples would help me significantly.
>> Thanks a lot.
>>
>> Regards,
>> Jeet
>
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@lists.xensource.com
>> http://lists.xensource.com/xen-devel
>
>
> --
> Tim Deegan <Tim.Deegan@citrix.com>
> Principal Software Engineer, Xen Platform Team
> Citrix Systems UK Ltd. (Company #02937203, SL9 0BG)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
prev parent reply other threads:[~2011-05-06 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-04 20:28 Read value of CR3 from DomU VCPU Nimgaonkar, Satyajeet
2011-05-05 8:33 ` Tim Deegan
2011-05-06 16:33 ` Nimgaonkar, Satyajeet
2011-05-06 16:57 ` Keir Fraser [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=C9E9E714.176B5%keir.xen@gmail.com \
--to=keir.xen@gmail.com \
--cc=SatyajeetNimgaonkar@my.unt.edu \
--cc=Tim.Deegan@citrix.com \
--cc=xen-devel@lists.xensource.com \
/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).