OvmfPkg/VirtioInputDxe: invert condition for matching KEY_PRESSED events

Technically, beyond KEY_PRESSED and its inverse KEY_RELEASED, a third
type of event is possible for autorepeated keystrokes.  Invert the
condition on Event->Value to handle autorepeat events as (successive)
key presses rather than repeated releases (essentially ignoring them).

Signed-off-by: Ivan Shapovalov <intelfx@intelfx.name>
Tested-by: Alexander Mikhalitsyn <aleksandr.mikhalitsyn@futurfusion.io>

OvmfPkg/VirtioInputDxe/VirtioInput.h

@@ -115,7 +115,8 @@ typedef struct {
           CR (a, VIRTIO_INPUT_DEV, AbsolutePointer, VIRTIO_INPUT_SIG)
 
 // Bellow candidates to be included as Linux header
-#define KEY_PRESSED  1
+#define KEY_RELEASED  0
+#define KEY_PRESSED   1
 
 //
 // VirtioInput.c

OvmfPkg/VirtioInputDxe/VirtioKeyboard.c

@@ -191,7 +191,7 @@ VirtioKeyboardHandleEvent (
   IN VIRTIO_INPUT_EVENT    *Event
   )
 {
-  if (Event->Value == KEY_PRESSED) {
+  if (Event->Value != KEY_RELEASED) {
     // Key pressed event received
     Dev->KeyActive[(UINT8)Event->Code] = TRUE;