linux-efi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joel Schopp <jschopp-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Greg KH <gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org>
Cc: linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	Leonidas da Silva Barbosa
	<leosilva-xuelUoVDAHHQT0dZR+AlfA@public.gmane.org>
Subject: Re: unusual uefi call/mapping problem
Date: Wed, 17 Apr 2013 00:04:16 -0500	[thread overview]
Message-ID: <516E2D50.8030908@linux.vnet.ibm.com> (raw)
In-Reply-To: <20130417024056.GA13609-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>

Thanks for the quick reply.

>> I'm working on the Linux kernel implementation of an draft standard
>> that has a uefi component.
>
> What standard would that be?

Trusted Computing Group Dynamic Root of Trust Management (D-RTM).


>> After extracting the physical address of the UEFI service we can't
>> successfully map it or call it.
>
> You want to call it from the kernel?  Why?  Usually you get a "virtual"
> address to call UEFI things, and then use efi_call_virt?(), why can't
> you do that here as well?

If I had a virtual address I would be a happy man.  I have a physical 
address and my attempts to turn it into a virtual one that is callable 
have been unfruitful.


>> 2) Various methods to map in the physical address into virtual
>> address space and then call the virtual address.  All of these have
>> failed.
>
> Why?  What have you done that failed?  Any pointers to code anywhere?

Unfortunately I can't release code until after the spec is public.  I 
believe that will happen in a matter of weeks and not months.  Then all 
work will be shared under gpl and we will work on getting it functional 
and acceptable for upstream inclusion.  I realize not being able to post 
code now is very limiting.

>
> Are you trying to do this before we switch to virtual mode, or after?

After.  We are trying to do this well after all userspace has started.

  parent reply	other threads:[~2013-04-17  5:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-16 21:31 unusual uefi call/mapping problem Joel Schopp
     [not found] ` <516DC325.6090604-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2013-04-17  2:40   ` Greg KH
     [not found]     ` <20130417024056.GA13609-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-04-17  5:04       ` Joel Schopp [this message]
2013-04-30 12:52   ` Matthew Garrett
     [not found]     ` <20130430125225.GA4197-1xO5oi07KQx4cg9Nei1l7Q@public.gmane.org>
2013-04-30 15:51       ` Joel Schopp
     [not found]         ` <517FE891.9070103-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
2013-04-30 16:23           ` Matthew Garrett

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=516E2D50.8030908@linux.vnet.ibm.com \
    --to=jschopp-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=gregkh-hQyY1W1yCW8ekmWlsbkhG0B+6BGkLq7r@public.gmane.org \
    --cc=leosilva-xuelUoVDAHHQT0dZR+AlfA@public.gmane.org \
    --cc=linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).