Convert hw backends to use keycodemapdb
v6 cover Convert hw backends to use keycodemapdb
This is a followup to
v1: https://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg02047.html
v2: https://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg02471.html
v3: https://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg02517.html
v4: https://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg02708.html
v5: https://lists.nongnu.org/archive/html/qemu-devel/2017-09/msg02950.html
This new series contains just the patches for converting the hardware backends to use keycodemapdb.
The main benefit is adding various missing key mappings that were previously accidentally left out
Daniel P. Berrange (4):
hw: convert virtio-input-hid device to keycodemapdb
hw: convert ps2 device to keycodemapdb
hw: convert the escc device to keycodemapdb
hw: convert XenInput keyboard to keycodemapdb
Makefile | 5 + hw/char/escc.c | 126 +------------- hw/display/xenfb.c | 138 ++++----------- hw/input/ps2.c | 406 +------------------------------------------- hw/input/virtio-input-hid.c | 136 +-------------- include/ui/input.h | 15 ++ ui/input-keymap.c | 5 + 7 files changed, 79 insertions(+), 752 deletions(-)
Signature · 7 lines
2.14.3 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v6 1/4 hw: convert virtio-input-hid device to keycodemapdb
Replace the keymap_qcode table with automatically generated tables.
Missing entries in keymap_qcode now fixed:
Q_KEY_CODE_ASTERISK -> KEY_KPASTERISK
Q_KEY_CODE_KP_MULTIPLY -> KEY_KPASTERISK
Q_KEY_CODE_STOP -> KEY_STOP
Q_KEY_CODE_AGAIN -> KEY_AGAIN
Q_KEY_CODE_PROPS -> KEY_PROPS
Q_KEY_CODE_UNDO -> KEY_UNDO
Q_KEY_CODE_FRONT -> KEY_FRONT
Q_KEY_CODE_COPY -> KEY_COPY
Q_KEY_CODE_OPEN -> KEY_OPEN
Q_KEY_CODE_PASTE -> KEY_PASTE
Q_KEY_CODE_FIND -> KEY_FIND
Q_KEY_CODE_CUT -> KEY_CUT
Q_KEY_CODE_LF -> KEY_LINEFEED
Q_KEY_CODE_HELP -> KEY_HELP
Q_KEY_CODE_COMPOSE -> KEY_COMPOSE
Q_KEY_CODE_RO -> KEY_RO
Q_KEY_CODE_HIRAGANA -> KEY_HIRAGANA
Q_KEY_CODE_HENKAN -> KEY_HENKAN
Q_KEY_CODE_YEN -> KEY_YEN
Q_KEY_CODE_KP_COMMA -> KEY_KPCOMMA
Q_KEY_CODE_KP_EQUALS -> KEY_KPEQUAL
Q_KEY_CODE_POWER -> KEY_POWER
Q_KEY_CODE_SLEEP -> KEY_SLEEP
Q_KEY_CODE_WAKE -> KEY_WAKEUP
Q_KEY_CODE_AUDIONEXT -> KEY_NEXTSONG
Q_KEY_CODE_AUDIOPREV -> KEY_PREVIOUSSONG
Q_KEY_CODE_AUDIOSTOP -> KEY_STOPCD
Q_KEY_CODE_AUDIOPLAY -> KEY_PLAYPAUSE
Q_KEY_CODE_AUDIOMUTE -> KEY_MUTE
Q_KEY_CODE_VOLUMEUP -> KEY_VOLUMEUP
Q_KEY_CODE_VOLUMEDOWN -> KEY_VOLUMEDOWN
Q_KEY_CODE_MEDIASELECT -> KEY_MEDIA
Q_KEY_CODE_MAIL -> KEY_MAIL
Q_KEY_CODE_CALCULATOR -> KEY_CALC
Q_KEY_CODE_COMPUTER -> KEY_COMPUTER
Q_KEY_CODE_AC_HOME -> KEY_HOMEPAGE
Q_KEY_CODE_AC_BACK -> KEY_BACK
Q_KEY_CODE_AC_FORWARD -> KEY_FORWARD
Q_KEY_CODE_AC_REFRESH -> KEY_REFRESH
Q_KEY_CODE_AC_BOOKMARKS -> KEY_BOOKMARKS
NB, the virtio-input device reports a bitmask to the guest driver that has a bit set for each Linux keycode that the host is able to send to the guest.
Thus by adding these extra key mappings we are technically changing the host<->guest ABI. This would also happen any time we defined new mappings for QEMU keycodes in future.
When a keycode is removed from the list of possible keycodes that host can send to the guest, it means that the guest OS will think it is possible to receive a key that in pratice can never be generated, which is harmless.
When a keycode is added to the list of possible keycodes that the host can send to the guest, it means that the guest OS can see an unexpected event. The Linux virtio_input.c driver code simply forwards this event to the input_event() method in the Linux input subsystem. This in turn calls input_handle_event(), which then calls input_get_disposition(). This method checks if the input event is present in the permitted keys bitmap, and if not returns INPUT_IGNORE_EVENT. Thus the unexpected event will get dropped, which is harmless.
If the guest OS reboots, or otherwise re-initializes the virt-input device, it will read the new keycode bitmap. No matter how many keys are defined, the config space has a fixed 128 byte bitmap. There is, however, a size field defiend which says how many bytes in the bitmap are used. So the guest OS reads the size of the bitmap, and then it reads the data from bitmap upto the designated size. So if the guest OS re-initializes at precisely the time that QEMU is migrated across versions, in the worst case, it could conceivably read the old size field, but then get the newly updated bitmap. If a key were added this is harmless, since it simply means it may not process the newly added key. If a key were removed, then it could be readnig a byte from the bitmap that was not initialized. Fortunately QEMU always memsets() the entire bitmap to 0, prior to setting keybits. Thus the guest OS will simply read zeros, which is again harmless.
Based on this analysis, it is believed that there is no need to preserve the virtio-input-hid keymaps across migration, as the host<->guest ABI change is harmless and self-resolving at time of guest reboot.
NB, this behaviour should perhaps be formalized in the virtio-input spec to declare how guest OS drivers should be written to be robust in their handling of the potentially changable key bitmaps.
--- Makefile | 1 + hw/input/virtio-input-hid.c | 136 +++----------------------------------------- include/ui/input.h | 3 + ui/input-keymap.c | 1 + 4 files changed, 14 insertions(+), 127 deletions(-)
Makefile +1 -0
@@ -227,6 +227,7 @@ KEYCODEMAP_CSV = $(SRC_PATH)/ui/keycodemapdb/data/keymaps.csv KEYCODEMAP_FILES = \ ui/input-keymap-linux-to-qcode.c \ + ui/input-keymap-qcode-to-linux.c \ ui/input-keymap-qcode-to-qnum.c \ ui/input-keymap-qnum-to-qcode.c \ $(NULL)
hw/input/virtio-input-hid.c +9 -127
171 lines not on this page · raw message
include/ui/input.h +3 -0
@@ -71,6 +71,9 @@ void qemu_remove_mouse_mode_change_notifier(Notifier *notify);extern const guint qemu_input_map_linux_to_qcode_len;extern const guint16 qemu_input_map_linux_to_qcode[]; +extern const guint qemu_input_map_qcode_to_linux_len; +extern const guint16 qemu_input_map_qcode_to_linux[]; +extern const guint qemu_input_map_qcode_to_qnum_len;extern const guint16 qemu_input_map_qcode_to_qnum[];
ui/input-keymap.c +1 -0
@@ -6,6 +6,7 @@#include "standard-headers/linux/input.h" #include "ui/input-keymap-linux-to-qcode.c" +#include "ui/input-keymap-qcode-to-linux.c" #include "ui/input-keymap-qcode-to-qnum.c" #include "ui/input-keymap-qnum-to-qcode.c"
Signature · 7 lines
2.14.3 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Qemu-devel] [PATCH v6 1/4] hw: convert virtio-input-hid device to keycodemapdb
Makefile KEYCODEMAP_CSV = $(SRC_PATH)/ui/keycodemapdb/data/keymaps.csv · line 233
Quoted 12 lines · Daniel P. Berrange
Makefile +1
-0@@ -227,6 +227,7 @@ KEYCODEMAP_CSV = $(SRC_PATH)/ui/keycodemapdb/data/keymaps.csv KEYCODEMAP_FILES = \ ui/input-keymap-linux-to-qcode.c \ + ui/input-keymap-qcode-to-linux.c \ ui/input-keymap-qcode-to-qnum.c \ ui/input-keymap-qnum-to-qcode.c \ $(NULL)
FYI, there is a patch on the mailing list that does just generate the new keymap:
<[email protected]>
([PATCH v5 1/4] ui: generate qcode to linux mappings)
Quoted 25 lines
include/ui/input.h +3
-0@@ -71,6 +71,9 @@ void qemu_remove_mouse_mode_change_notifier(Notifier *notify);extern const guint qemu_input_map_linux_to_qcode_len;extern const guint16 qemu_input_map_linux_to_qcode[]; +extern const guint qemu_input_map_qcode_to_linux_len; +extern const guint16 qemu_input_map_qcode_to_linux[]; +extern const guint qemu_input_map_qcode_to_qnum_len;extern const guint16 qemu_input_map_qcode_to_qnum[];ui/input-keymap.c +1
-0@@ -6,6 +6,7 @@#include "standard-headers/linux/input.h" #include "ui/input-keymap-linux-to-qcode.c" +#include "ui/input-keymap-qcode-to-linux.c" #include "ui/input-keymap-qcode-to-qnum.c" #include "ui/input-keymap-qnum-to-qcode.c"
Signature · 6 lines
Anthony PERARD _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v6 2/4 hw: convert ps2 device to keycodemapdb
In reply to Daniel P. BerrangeReplace the qcode_to_keycode_set1, qcode_to_keycode_set2, and qcode_to_keycode_set3 tables with automatically generated tables.
Missing entries in qcode_to_keycode_set1 now fixed:
- Q_KEY_CODE_SYSRQ -> 0x54
- Q_KEY_CODE_PRINT -> 0x54 (NB ignored due to special case)
- Q_KEY_CODE_AGAIN -> 0xe005
- Q_KEY_CODE_PROPS -> 0xe006
- Q_KEY_CODE_UNDO -> 0xe007
- Q_KEY_CODE_FRONT -> 0xe00c
- Q_KEY_CODE_COPY -> 0xe078
- Q_KEY_CODE_OPEN -> 0x64
- Q_KEY_CODE_PASTE -> 0x65
- Q_KEY_CODE_CUT -> 0xe03c
- Q_KEY_CODE_LF -> 0x5b
- Q_KEY_CODE_HELP -> 0xe075
- Q_KEY_CODE_COMPOSE -> 0xe05d
- Q_KEY_CODE_PAUSE -> 0xe046
- Q_KEY_CODE_KP_EQUALS -> 0x59
And some mistakes corrected:
- Q_KEY_CODE_HIRAGANA was mapped to 0x70 (Katakanahiragana) instead of of 0x77 (Hirigana)
- Q_KEY_CODE_MENU was incorrectly mapped to the compose scancode (0xe05d) and is now mapped to 0xe01e
- Q_KEY_CODE_FIND was mapped to 0xe065 (Search) instead of to 0xe041 (Find)
- Q_KEY_CODE_POWER, SLEEP & WAKE had 0x0e instead of 0xe0 as the prefix
Missing entries in qcode_to_keycode_set2 now fixed:
- Q_KEY_CODE_PRINT -> 0x7f (NB ignored due to special case)
- Q_KEY_CODE_COMPOSE -> 0xe02f
- Q_KEY_CODE_PAUSE -> 0xe077
- Q_KEY_CODE_KP_EQUALS -> 0x0f
And some mistakes corrected:
- Q_KEY_CODE_HIRAGANA was mapped to 0x13 (Katakanahiragana) instead of of 0x62 (Hirigana)
- Q_KEY_CODE_MENU was incorrectly mapped to the compose scancode (0xe02f) and is now not mapped
- Q_KEY_CODE_FIND was mapped to 0xe010 (Search) and is now not mapped.
- Q_KEY_CODE_POWER, SLEEP & WAKE had 0x0e instead of 0xe0 as the prefix
Missing entries in qcode_to_keycode_set3 now fixed:
- Q_KEY_CODE_ASTERISK -> 0x7e
- Q_KEY_CODE_SYSRQ -> 0x57
- Q_KEY_CODE_LESS -> 0x13
- Q_KEY_CODE_STOP -> 0x0a
- Q_KEY_CODE_AGAIN -> 0x0b
- Q_KEY_CODE_PROPS -> 0x0c
- Q_KEY_CODE_UNDO -> 0x10
- Q_KEY_CODE_COPY -> 0x18
- Q_KEY_CODE_OPEN -> 0x20
- Q_KEY_CODE_PASTE -> 0x28
- Q_KEY_CODE_FIND -> 0x30
- Q_KEY_CODE_CUT -> 0x38
- Q_KEY_CODE_HELP -> 0x09
- Q_KEY_CODE_COMPOSE -> 0x8d
- Q_KEY_CODE_AUDIONEXT -> 0x93
- Q_KEY_CODE_AUDIOPREV -> 0x94
- Q_KEY_CODE_AUDIOSTOP -> 0x98
- Q_KEY_CODE_AUDIOMUTE -> 0x9c
- Q_KEY_CODE_VOLUMEUP -> 0x95
- Q_KEY_CODE_VOLUMEDOWN -> 0x9d
- Q_KEY_CODE_CALCULATOR -> 0xa3
- Q_KEY_CODE_AC_HOME -> 0x97
And some mistakes corrected:
- Q_KEY_CODE_MENU was incorrectly mapped to the compose scancode (0x8d) and is now 0x91
--- Makefile | 3 + hw/input/ps2.c | 406 +---------------------------------------------------- include/ui/input.h | 9 ++ ui/input-keymap.c | 3 + 4 files changed, 22 insertions(+), 399 deletions(-)
Makefile +3 -0
@@ -227,6 +227,9 @@ KEYCODEMAP_CSV = $(SRC_PATH)/ui/keycodemapdb/data/keymaps.csv KEYCODEMAP_FILES = \ ui/input-keymap-linux-to-qcode.c \ + ui/input-keymap-qcode-to-atset1.c \ + ui/input-keymap-qcode-to-atset2.c \ + ui/input-keymap-qcode-to-atset3.c \ ui/input-keymap-qcode-to-linux.c \ ui/input-keymap-qcode-to-qnum.c \ ui/input-keymap-qnum-to-qcode.c \
hw/input/ps2.c +7 -399
436 lines not on this page · raw message
include/ui/input.h +9 -0
@@ -71,6 +71,15 @@ void qemu_remove_mouse_mode_change_notifier(Notifier *notify);extern const guint qemu_input_map_linux_to_qcode_len;extern const guint16 qemu_input_map_linux_to_qcode[]; +extern const guint qemu_input_map_qcode_to_atset1_len; +extern const guint16 qemu_input_map_qcode_to_atset1[]; + +extern const guint qemu_input_map_qcode_to_atset2_len; +extern const guint16 qemu_input_map_qcode_to_atset2[]; + +extern const guint qemu_input_map_qcode_to_atset3_len; +extern const guint16 qemu_input_map_qcode_to_atset3[]; +extern const guint qemu_input_map_qcode_to_linux_len;extern const guint16 qemu_input_map_qcode_to_linux[];
ui/input-keymap.c +3 -0
@@ -6,6 +6,9 @@#include "standard-headers/linux/input.h" #include "ui/input-keymap-linux-to-qcode.c" +#include "ui/input-keymap-qcode-to-atset1.c" +#include "ui/input-keymap-qcode-to-atset2.c" +#include "ui/input-keymap-qcode-to-atset3.c" #include "ui/input-keymap-qcode-to-linux.c" #include "ui/input-keymap-qcode-to-qnum.c" #include "ui/input-keymap-qnum-to-qcode.c"
Signature · 7 lines
2.14.3 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v6 3/4 hw: convert the escc device to keycodemapdb
In reply to Daniel P. BerrangeReplace the qcode_to_keycode table with automatically generated tables.
Missing entries in qcode_to_keycode now fixed:
- Q_KEY_CODE_KP_COMMA -> 0x2d
--- Makefile | 1 + hw/char/escc.c | 126 +++-------------------------------------------------- include/ui/input.h | 3 ++ ui/input-keymap.c | 1 + 4 files changed, 10 insertions(+), 121 deletions(-)
Makefile +1 -0
@@ -232,6 +232,7 @@ KEYCODEMAP_FILES = \ ui/input-keymap-qcode-to-atset3.c \ ui/input-keymap-qcode-to-linux.c \ ui/input-keymap-qcode-to-qnum.c \ + ui/input-keymap-qcode-to-sun.c \ ui/input-keymap-qnum-to-qcode.c \ $(NULL)
hw/char/escc.c +5 -121
138 lines not on this page · raw message
include/ui/input.h +3 -0
@@ -86,6 +86,9 @@ extern const guint16 qemu_input_map_qcode_to_linux[];extern const guint qemu_input_map_qcode_to_qnum_len;extern const guint16 qemu_input_map_qcode_to_qnum[]; +extern const guint qemu_input_map_qcode_to_sun_len; +extern const guint16 qemu_input_map_qcode_to_sun[]; +extern const guint qemu_input_map_qnum_to_qcode_len;extern const guint16 qemu_input_map_qnum_to_qcode[];
ui/input-keymap.c +1 -0
@@ -11,6 +11,7 @@#include "ui/input-keymap-qcode-to-atset3.c" #include "ui/input-keymap-qcode-to-linux.c" #include "ui/input-keymap-qcode-to-qnum.c" +#include "ui/input-keymap-qcode-to-sun.c" #include "ui/input-keymap-qnum-to-qcode.c" int qemu_input_linux_to_qcode (unsigned int lnx)
Signature · 7 lines
2.14.3 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
PATCH v6 4/4 hw: convert XenInput keyboard to keycodemapdb
In reply to Daniel P. BerrangeReplace the scancode2linux table with an automatically generated table. In doing so, the XenFB keyboard handler is also converted to the modern InputEvent framework.
--- hw/display/xenfb.c | 138 +++++++++++++---------------------------------------- 1 file changed, 33 insertions(+), 105 deletions(-)
hw/display/xenfb.c +33 -105
@@ -28,6 +28,7 @@#include "hw/hw.h" #include "ui/console.h" +#include "ui/input.h" #include "hw/xen/xen_backend.h" #include <xen/event_channel.h>
@@ -52,7 +53,7 @@ struct XenInput {struct common c;int abs_pointer_wanted;/* Whether guest supports absolute pointer */ int button_state;/* Last seen pointer button state */ -int extended; +QemuInputHandlerState *qkbd;QEMUPutMouseEntry *qmouse; };
@@ -120,78 +121,6 @@ static void common_unbind(struct common *c)/* -------------------------------------------------------------------- */ -#if 0 -/* -* These two tables are not needed any more, but left in here -* intentionally as documentation, to show how scancode2linux[] -* was generated. -* -* Tables to map from scancode to Linux input layer keycode. -* Scancodes are hardware-specific. These maps assumes a -* standard AT or PS/2 keyboard which is what QEMU feeds us. -*/ -const unsigned char atkbd_set2_keycode[512 ] = { - -0 ,67 ,65 ,63 ,61 ,59 ,60 ,88 ,0 ,68 ,66 ,64 ,62 ,15 ,41 ,117 , -0 ,56 ,42 ,93 ,29 ,16 ,2 ,0 ,0 ,0 ,44 ,31 ,30 ,17 ,3 ,0 , -0 ,46 ,45 ,32 ,18 ,5 ,4 ,95 ,0 ,57 ,47 ,33 ,20 ,19 ,6 ,183 , -0 ,49 ,48 ,35 ,34 ,21 ,7 ,184 ,0 ,0 ,50 ,36 ,22 ,8 ,9 ,185 , -0 ,51 ,37 ,23 ,24 ,11 ,10 ,0 ,0 ,52 ,53 ,38 ,39 ,25 ,12 ,0 , -0 ,89 ,40 ,0 ,26 ,13 ,0 ,0 ,58 ,54 ,28 ,27 ,0 ,43 ,0 ,85 , -0 ,86 ,91 ,90 ,92 ,0 ,14 ,94 ,0 ,79 ,124 ,75 ,71 ,121 ,0 ,0 , -82 ,83 ,80 ,76 ,77 ,72 ,1 ,69 ,87 ,78 ,81 ,74 ,55 ,73 ,70 ,99 , - -0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 , -217 ,100 ,255 ,0 ,97 ,165 ,0 ,0 ,156 ,0 ,0 ,0 ,0 ,0 ,0 ,125 , -173 ,114 ,0 ,113 ,0 ,0 ,0 ,126 ,128 ,0 ,0 ,140 ,0 ,0 ,0 ,127 , -159 ,0 ,115 ,0 ,164 ,0 ,0 ,116 ,158 ,0 ,150 ,166 ,0 ,0 ,0 ,142 , -157 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,155 ,0 ,98 ,0 ,0 ,163 ,0 ,0 , -226 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,255 ,96 ,0 ,0 ,0 ,143 ,0 , -0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,107 ,0 ,105 ,102 ,0 ,0 ,112 , -110 ,111 ,108 ,112 ,106 ,103 ,0 ,119 ,0 ,118 ,109 ,0 ,99 ,104 ,119 ,0 , - -}; - -const unsigned char atkbd_unxlate_table[128 ] = { - -0 ,118 ,22 ,30 ,38 ,37 ,46 ,54 ,61 ,62 ,70 ,69 ,78 ,85 ,102 ,13 , -21 ,29 ,36 ,45 ,44 ,53 ,60 ,67 ,68 ,77 ,84 ,91 ,90 ,20 ,28 ,27 , -35 ,43 ,52 ,51 ,59 ,66 ,75 ,76 ,82 ,14 ,18 ,93 ,26 ,34 ,33 ,42 , -50 ,49 ,58 ,65 ,73 ,74 ,89 ,124 ,17 ,41 ,88 ,5 ,6 ,4 ,12 ,3 , -11 ,2 ,10 ,1 ,9 ,119 ,126 ,108 ,117 ,125 ,123 ,107 ,115 ,116 ,121 ,105 , -114 ,122 ,112 ,113 ,127 ,96 ,97 ,120 ,7 ,15 ,23 ,31 ,39 ,47 ,55 ,63 , -71 ,79 ,86 ,94 ,8 ,16 ,24 ,32 ,40 ,48 ,56 ,64 ,72 ,80 ,87 ,111 , -19 ,25 ,57 ,81 ,83 ,92 ,95 ,98 ,99 ,100 ,101 ,103 ,104 ,106 ,109 ,110 - -}; -#endif - -/* -* for (i = 0; i < 128; i++) { -* scancode2linux[i] = atkbd_set2_keycode[atkbd_unxlate_table[i]]; -* scancode2linux[i | 0x80] = atkbd_set2_keycode[atkbd_unxlate_table[i] | 0x80]; -* } -*/ -static const unsigned char scancode2linux[512 ] = { -0 ,1 ,2 ,3 ,4 ,5 ,6 ,7 ,8 ,9 ,10 ,11 ,12 ,13 ,14 ,15 , -16 ,17 ,18 ,19 ,20 ,21 ,22 ,23 ,24 ,25 ,26 ,27 ,28 ,29 ,30 ,31 , -32 ,33 ,34 ,35 ,36 ,37 ,38 ,39 ,40 ,41 ,42 ,43 ,44 ,45 ,46 ,47 , -48 ,49 ,50 ,51 ,52 ,53 ,54 ,55 ,56 ,57 ,58 ,59 ,60 ,61 ,62 ,63 , -64 ,65 ,66 ,67 ,68 ,69 ,70 ,71 ,72 ,73 ,74 ,75 ,76 ,77 ,78 ,79 , -80 ,81 ,82 ,83 ,99 ,0 ,86 ,87 ,88 ,117 ,0 ,0 ,95 ,183 ,184 ,185 , -0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 , -93 ,0 ,0 ,89 ,0 ,0 ,85 ,91 ,90 ,92 ,0 ,94 ,0 ,124 ,121 ,0 , - -0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 , -165 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,163 ,0 ,0 ,96 ,97 ,0 ,0 , -113 ,140 ,164 ,0 ,166 ,0 ,0 ,0 ,0 ,0 ,255 ,0 ,0 ,0 ,114 ,0 , -115 ,0 ,150 ,0 ,0 ,98 ,255 ,99 ,100 ,0 ,0 ,0 ,0 ,0 ,0 ,0 , -0 ,0 ,0 ,0 ,0 ,119 ,119 ,102 ,103 ,104 ,0 ,105 ,112 ,106 ,118 ,107 , -108 ,109 ,110 ,111 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,125 ,126 ,127 ,116 ,142 , -0 ,0 ,0 ,143 ,0 ,217 ,156 ,173 ,128 ,159 ,158 ,157 ,155 ,226 ,0 ,112 , -0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 ,0 , -}; -/* Send an event to the keyboard frontend driver */ static int xenfb_kbd_event (struct XenInput *xenfb,union xenkbd_in_event *event)
@@ -260,38 +189,23 @@ static int xenfb_send_position(struct XenInput *xenfb,return xenfb_kbd_event (xenfb, &event); } -/* -* Send a key event from the client to the guest OS -* QEMU gives us a raw scancode from an AT / PS/2 style keyboard. -* We have to turn this into a Linux Input layer keycode. -* -* Extra complexity from the fact that with extended scancodes -* (like those produced by arrow keys) this method gets called -* twice, but we only want to send a single event. So we have to -* track the '0xe0' scancode state & collapse the extended keys -* as needed. -* -* Wish we could just send scancodes straight to the guest which -* already has code for dealing with this... -*/ -static void xenfb_key_event (void *opaque,int scancode) +static void xenfb_key_event (DeviceState *dev,QemuConsole *src, +InputEvent *evt) { -struct XenInput *xenfb = opaque; -int down =1 ; - -if (scancode ==0xe0 ) { - xenfb->extended =1 ; -return ; - }else if (scancode &0x80 ) { - scancode &=0x7f ; - down =0 ; - } -if (xenfb->extended) { - scancode |=0x80 ; - xenfb->extended =0 ; + struct XenInput *xenfb = container_of(dev, struct XenInput, + c.xendev.qdev); +InputKeyEvent *key = evt->u.key.data; +int qcode; + +assert (evt->type ==INPUT_EVENT_KIND_KEY ); + + qcode =qemu_input_key_value_to_qcode (key->key); +if (qcode < qemu_input_map_qcode_to_linux_len) { +trace_xenfb_key_event (xenfb, qemu_input_map_qcode_to_linux[qcode], + key->down); +xenfb_send_key (xenfb, key->down, + qemu_input_map_qcode_to_linux[qcode]); } -trace_xenfb_key_event (opaque, scancode2linux[scancode], down); -xenfb_send_key (xenfb, down, scancode2linux[scancode]); }/*
@@ -348,6 +262,12 @@ static int input_init(struct XenDevice *xendev)return 0 ; } +static QemuInputHandler xenfb_keyboard_handler = { + .name ="Xen FB Keyboard" , + .mask =INPUT_EVENT_MASK_KEY , + .event = xenfb_key_event, +}; +static int input_initialise (struct XenDevice *xendev) { struct XenInput *in = container_of(xendev, struct XenInput, c.xendev);
@@ -357,7 +277,6 @@ static int input_initialise(struct XenDevice *xendev)if (rc !=0 )return rc; -qemu_add_kbd_event_handler (xenfb_key_event, in);return 0 ; }
@@ -377,6 +296,12 @@ static void input_connected(struct XenDevice *xendev) in->qmouse =qemu_add_mouse_event_handler (xenfb_mouse_event, in, in->abs_pointer_wanted,"Xen PVFB Mouse" ); + +if (in->qkbd) { +qemu_input_handler_unregister (in->qkbd); + } + in->qkbd =qemu_input_handler_register ((DeviceState *)in, + &xenfb_keyboard_handler); }static void input_disconnect (struct XenDevice *xendev)
@@ -387,7 +312,10 @@ static void input_disconnect(struct XenDevice *xendev)qemu_remove_mouse_event_handler (in->qmouse); in->qmouse =NULL ; } -qemu_add_kbd_event_handler (NULL ,NULL ); +if (in->qkbd) { +qemu_input_handler_unregister (in->qkbd); + in->qkbd =NULL ; + }common_unbind (&in->c); }
Signature · 7 lines
2.14.3 _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Qemu-devel] [PATCH v6 4/4] hw: convert XenInput keyboard to keycodemapdb
Quoted 6 lines · Daniel P. Berrange
Replace the scancode2linux table with an automatically generated table. In doing so, the XenFB keyboard handler is also converted to the modern InputEvent framework.
Signed-off-by Daniel P. Berrange <[email protected]>
FYI, I think that is done by <[email protected]>. ([PATCH v5 2/4] xenfb: Use Input Handlers directly)
Signature · 6 lines
Anthony PERARD _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Qemu-devel] [PATCH v6 4/4] hw: convert XenInput keyboard to keycodemapdb
Quoted 10 lines · Anthony PERARD
Quoted 6 lines · Daniel P. Berrange
Replace the scancode2linux table with an automatically generated table. In doing so, the XenFB keyboard handler is also converted to the modern InputEvent framework.
Signed-off-by Daniel P. Berrange <[email protected]>FYI, I think that is done by <[email protected]>. ([PATCH v5 2/4] xenfb: Use Input Handlers directly)
Thanks, I see Stefano has posted a PULL for those patches, so I'll drop my duplicates.
Regards,
Daniel
Signature · 8 lines
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| _______________________________________________ Xen-devel mailing list [email protected] https://lists.xenproject.org/mailman/listinfo/xen-devel
Re: [Qemu-devel] [PATCH v6 4/4] hw: convert XenInput keyboard to keycodemapdb
Quoted 7 lines · Daniel P. Berrange
Quoted 6 lines · Anthony PERARD
Quoted 5 lines · Daniel P. Berrange
Replace the scancode2linux table with an automatically generated table. In doing so, the XenFB keyboard handler is also converted to the modern InputEvent framework.
Quoted 7 lines
Quoted 4 lines
Quoted 1 line
Signed-off-by Daniel P. Berrange <[email protected]>FYI, I think that is done by <[email protected]>. ([PATCH v5 2/4] xenfb: Use Input Handlers directly)
Thanks, I see Stefano has posted a PULL for those patches, so I'll drop my duplicates.
Can you send a updated series? Also ordering virtio-input-hid to the end of the series would be great.
thanks,
Gerd