From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: dandan bi <dandan.bi@intel.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
Ruiyu Ni <ruiyu.ni@intel.com>,
Leif Lindholm <leif.lindholm@linaro.org>
Subject: Re: [patch 1/3] EmbeddedPkg/VirtualKeyboard: Avoid notification called more than once
Date: Thu, 13 Sep 2018 17:50:38 +0200 [thread overview]
Message-ID: <CAKv+Gu_sft72oxtYcfYLvH_vERRtede1kvZ+avJLf4N3_5rSdw@mail.gmail.com> (raw)
In-Reply-To: <20180910071202.11008-1-dandan.bi@intel.com>
On 10 September 2018 at 09:12, dandan bi <dandan.bi@intel.com> wrote:
> From: Dandan Bi <dandan.bi@intel.com>
>
> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=996
>
> Issue:
> In current code logic, when a key is pressed, it will search
> the whole NotifyList to find whether a notification has been
> registered with the keystroke. if yes, it will en-queue the
> key for notification execution later. And now if different
> notification functions have been registered with the same key,
> then the key will be en-queued more than once. Then it will
> cause the notification executed more than once.
>
> This patch is to enhance the code logic to fix this issue.
>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Dandan Bi <dandan.bi@intel.com>
Reviewed-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> ---
> EmbeddedPkg/Drivers/VirtualKeyboardDxe/VirtualKeyboard.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/EmbeddedPkg/Drivers/VirtualKeyboardDxe/VirtualKeyboard.c b/EmbeddedPkg/Drivers/VirtualKeyboardDxe/VirtualKeyboard.c
> index 6609bc8dbe..daea9c47d2 100644
> --- a/EmbeddedPkg/Drivers/VirtualKeyboardDxe/VirtualKeyboard.c
> +++ b/EmbeddedPkg/Drivers/VirtualKeyboardDxe/VirtualKeyboard.c
> @@ -1,9 +1,9 @@
> /** @file
> VirtualKeyboard driver
>
> -Copyright (c) 2006 - 2016, Intel Corporation. All rights reserved.<BR>
> +Copyright (c) 2006 - 2018, Intel Corporation. All rights reserved.<BR>
> Copyright (c) 2018, Linaro Ltd. All rights reserved.<BR>
>
> This program and the accompanying materials
> are licensed and made available under the terms and conditions
> of the BSD License which accompanies this distribution. The
> @@ -1043,10 +1043,11 @@ VirtualKeyboardTimerHandler (
> // while current TPL is TPL_NOTIFY. It will be invoked in
> // KeyNotifyProcessHandler() which runs at TPL_CALLBACK.
> //
> Enqueue (&VirtualKeyboardPrivate->QueueForNotify, &KeyData);
> gBS->SignalEvent (VirtualKeyboardPrivate->KeyNotifyProcessEvent);
> + break;
> }
> }
>
> Enqueue (&VirtualKeyboardPrivate->Queue, &KeyData);
>
> --
> 2.14.3.windows.1
>
prev parent reply other threads:[~2018-09-13 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 7:12 [patch 1/3] EmbeddedPkg/VirtualKeyboard: Avoid notification called more than once dandan bi
2018-09-10 7:12 ` [patch 2/3] IntelFrameworkModulePkg: Avoid key " dandan bi
2018-09-13 2:24 ` Ni, Ruiyu
2018-09-10 7:12 ` [patch 3/3] MdeModulePkg: " dandan bi
2018-09-12 1:55 ` Zeng, Star
2018-09-13 2:24 ` Ni, Ruiyu
2018-09-13 2:24 ` [patch 1/3] EmbeddedPkg/VirtualKeyboard: Avoid " Ni, Ruiyu
2018-09-13 15:50 ` Ard Biesheuvel [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=CAKv+Gu_sft72oxtYcfYLvH_vERRtede1kvZ+avJLf4N3_5rSdw@mail.gmail.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