public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Andrew Fish <afish@apple.com>
To: Michael Zimmermann <sigmaepsilon92@gmail.com>
Cc: "Zeng, Star" <star.zeng@intel.com>,
	Mike Kinney <michael.d.kinney@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@ml01.01.org>
Subject: Re: TPL of RegisterKeyNotify
Date: Tue, 10 Jan 2017 09:23:39 -0800	[thread overview]
Message-ID: <A2D6D5F1-62F4-4FFC-B1EE-0DE929658EA6@apple.com> (raw)
In-Reply-To: <CAN9vWDL2H5zxq+2FfOeWKi-yM7oUeCkRQ7E-TK6Ks=XZdGrrhQ@mail.gmail.com>


> On Jan 10, 2017, at 6:48 AM, Michael Zimmermann <sigmaepsilon92@gmail.com> wrote:
> 
> just FYI, mantis links are useless if you don't have access to that ;)
> I don't know what this is usually used for but making some parts of
> uefi.org public doesn't sound like a bad idea to me.
> 

Mantis is the UEFI Forum Specification Working group bug tracker. The UEFI Forums organizational documents require membership to view things work group, only the finished specs are public. There is a history of companies implementing spec work group  items and building interfaces that end up not being compatible with the spec, but close enough that you can't spot them in the wild. I think this was a big problem in wireless specifications, but it is generally the same group of lawyers from the member companies that setup the bylaws of the industry trade groups. 

So I agree the mantis reference in the commit message is confusing...

Thanks,

Andrew Fish 

> Thanks
> Michael
> 
> On Mon, Dec 12, 2016 at 2:07 AM, Zeng, Star <star.zeng@intel.com> wrote:
>> Michael,
>> 
>> There is already an approved UEFI mantis https://mantis.uefi.org/mantis/view.php?id=1634 that has the clarification to the TPL of KeyNotify function.
>> Currently KB drivers just call the KeyNotify functions in TimerEvent that has TPL_NOTIFY, we are updating code to make the KeyNotify functions called in TPL_CALLBACK to the new mantis.
>> 
>> 
>> Thanks,
>> Star
>> -----Original Message-----
>> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Michael Zimmermann
>> Sent: Friday, December 9, 2016 8:09 PM
>> To: edk2-devel@lists.01.org <edk2-devel@ml01.01.org>
>> Subject: [edk2] TPL of RegisterKeyNotify
>> 
>> I couldn't find any information in the spec about the TPL which notify functions will/should be called with.
>> When I do File IO from within such an handler DxeCore tells me that 'RaiseTpl with OldTpl(0x10) > NewTpl(0x8)' which translated means TPL_NOTIFY > TPL_CALLBACK.
>> 
>> That probably means that it's called using TPL_NOTIFY, but is that defined somewhere?
>> Do I have to raise another (TPL_CALLBACK) event to be able to perform my File IO operation to solve this?
>> 
>> Thanks
>> Michael
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel



      reply	other threads:[~2017-01-10 17:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-09 12:09 TPL of RegisterKeyNotify Michael Zimmermann
2016-12-12  1:07 ` Zeng, Star
2017-01-10 14:48   ` Michael Zimmermann
2017-01-10 17:23     ` Andrew Fish [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-list 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=A2D6D5F1-62F4-4FFC-B1EE-0DE929658EA6@apple.com \
    --to=devel@edk2.groups.io \
    /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