From: Andrew Fish <afish@apple.com>
To: "Tomas Pilar (tpilar)" <tpilar@solarflare.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: Creating Event in an EventGroup that has already been signaled
Date: Thu, 20 Jul 2017 10:38:09 -0700 [thread overview]
Message-ID: <77454275-17A1-4E65-BA75-8E022171129D@apple.com> (raw)
In-Reply-To: <638485ba-9d86-2954-1ae7-365bf9bc7aaf@solarflare.com>
> On Jul 20, 2017, at 9:35 AM, Tomas Pilar (tpilar) <tpilar@solarflare.com> wrote:
>
> What would be the state of that event post creation. Would it be immediately signalled and the notify function queued? Or would the EventGroup have to be signaled a second time for this new event to also become signaled?
>
Tom,
Signaling an event inserts that event into a queue based on TPL. For GUIDed events the list of events is walked and any event that matches the GUID of the event group gets placed in the queue.
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Event/Event.c#L258 <https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Event/Event.c#L258>
The event is later dequeued and signaled.
https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Event/Event.c#L165 <https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Dxe/Event/Event.c#L165>
So basically you only signal the events that exists, including the event created to signal the event group.
Thanks,
Andrew Fish
> Cheers,
> Tom
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-07-20 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-20 16:35 Creating Event in an EventGroup that has already been signaled Tomas Pilar (tpilar)
2017-07-20 17:38 ` 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=77454275-17A1-4E65-BA75-8E022171129D@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