From: Zeinab Alebouyeh <z.alebouyeh@gmail.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: "xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: Grab the physical address of a label
Date: Fri, 8 Jun 2012 11:15:29 -0700 [thread overview]
Message-ID: <CAE+SDMz1Yak4zSYiT1ow7QmxmbTghtd2oKjzCCAgVtn0RjZY1Q@mail.gmail.com> (raw)
In-Reply-To: <1339050679.6557.21.camel@dagon.hellion.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 2098 bytes --]
On Wed, Jun 6, 2012 at 11:31 PM, Ian Campbell <Ian.Campbell@citrix.com>wrote:
> Please don't top post, it makes it hard to follow the flow of the
> conversation.
>
> You might also find it useful to read
> http://wiki.xen.org/wiki/Asking_Xen_Devel_Questions
>
> On Thu, 2012-06-07 at 05:29 +0100, Zeinab Alebouyeh wrote:
> > Thanks but I think if I find the base physical address of xen image I
> > can convert virtual address to physical address
>
> I'm not sure what this has to do with taking the address of a label,
> like you originally asked, but...
>
> There are macros to convert a xenheap virtual address into a physical
> one and back, see __pa and __va. (Note that these only work for xenheap
> addresses).
>
> > I'm working in xen4 and my platform is: Processor AMD 64 and Centos 6
> > i386 with 8G of RAM
>
> Are you using a 32-bit or 64-bit hypervisor?
>
> I strongly recommend basing all future x86 work on 64-bit Xen, even if
> you are using a 32 bit dom0.
>
> > Can anyone tell me The physical address that xen image load in it?
> > This physical address depends on platform?
>
> Yes, Xen will relocate itself at start of day. You should be able to
> figure out the details from the implementation of __pa and __va.
>
> It might be helpful if you described what you are actually trying to
> achieve here -- what is your end goal?
>
> Ian.
>
Hi
Because currently I'm not in lab I don't know my hypervisor is 32b or 64
bit.
I'm working in a security project. for improve security of applications
running in virtualized environment. I want to use the security instruction
of AMD SVM named SKINIT.
because this instruction must run in ring0, I add a hypercall in xen and
write my codes in my hypercall function.
The skinit instruction takes the physical address of a block as an input
operand( in the eax register) and establish a secure execution environment
for a software component(block)
I have a label in my hypercall function that is the start of my block. In
order to use skinit I want grab the physical address of my label to save in
eax register.
Thanks if anyone help me.
[-- Attachment #1.2: Type: text/html, Size: 2754 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2012-06-08 18:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-05 6:07 Grab the physical address of a label Zeinab Alebouyeh
2012-06-06 9:43 ` Ian Campbell
2012-06-07 4:29 ` Zeinab Alebouyeh
2012-06-07 6:31 ` Ian Campbell
2012-06-08 18:15 ` Zeinab Alebouyeh [this message]
2012-06-12 9:05 ` Ian Campbell
2012-06-14 15:59 ` Zeinab Alebouyeh
2012-06-19 9:59 ` Ian Campbell
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=CAE+SDMz1Yak4zSYiT1ow7QmxmbTghtd2oKjzCCAgVtn0RjZY1Q@mail.gmail.com \
--to=z.alebouyeh@gmail.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.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 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).