search for: send_ev

...fde0b0 #34 0x00002aaab084dfeb in scaleHandleEvent (d=0x633f00, event=0x7fff0f24ad30) at scale.c:1673 s = <value optimized out> sd = (ScaleDisplay *) 0xfe0220 #35 0x000000000040d750 in eventLoop () at display.c:1503 event = {type = 16, xany = {type = 16, serial = 10885, send_event = 0, display = 0x6481b0, window = 421}, xkey = {type = 16, serial = 10885, send_event = 0, display = 0x6481b0, window = 421, root = 20989986, subwindow = 1318554960192, time = 1756641624704, x = 0, y = 0, x_root = 65142784, y_root = 1967360, state = 1, keycode = 2, same_screen = 1},...

...on from device.c. I then do what I describe above, and get the following backtrace from gdb, edited to show what I think is going on. (gdb) bt #0 removeDevice (devNum=1, findNext=TRUE) at devices.c:307 #1 0xb7962855 in handleEvent (event= {type = 33, xany = {type = 33, serial = 15621, send_event = 1, ...(snip)... , 268686226}}) at devX11.c:627 #2 0xb796296c in R_ProcessX11Events (data=0x0) at devX11.c:665 #3 0x080fd99c in R_runHandlers (handlers=0x8263d28, readMask=0x82cf6a0) at sys-std.c:363 #4 0xb74e159e in RTcl_eventProc (evPtr=0x97dfbf0, flags=-1) at tcltk_unix.c:136 #5 0...

...intr = &(((vcpu_iodata_t *) shared_page)->vp_intr[0]); atomic_set_bit(vector, intr); - fprintf(logfile, "injecting vector: %x\n", vector); + if (loglevel & CPU_LOG_INT) + fprintf(logfile, "injecting vector: %x\n", vector); env->send_event = 1; } _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 To: freedesktop@lists.freedesktop.org Subject: Help! I can't fake events! I am very frustrated right now. I need to be able to send an event to a program but for some, unknown, reason I have been unable to find a single way to send a event to a window without the stupid SYNTHETIC flag getting set. I do not wish to explain why I must do this (if

I''ve added experiments/core-model-2 to SVN. I think this is pretty clean and satisfactory. Jeff, please have a look and see if you like the placement of timeouts (which are currently unimplemented). Any event now has the possibility of a timeout. To get an application-level timeout, you''d just post an event with a timeout to a nil target. When the timeout expires, the errback

...rty data items correctly Ran Benita (3): Add "altmask" attribute, like "altenum" for masks xml-xcb.txt: mention that case/bitcase can have a name xml-xcb.txt: remove description of the "localfield" element Robert Ancell (2): shm: Mark PutImage.send_event field as boolean glx: Add IsEnabled request Uli Schlachter (1): Release xcb-proto 1.12 Download: http://xcb.freedesktop.org/dist/xcb-proto-1.12.tar.bz2 http://xcb.freedesktop.org/dist/xcb-proto-1.12.tar.gz md5sum: 14e60919f859560f28426a685a555962 xcb-proto-1.12.tar.bz2 5...

...s wait_marked = no end_marked = no dsp_drop_silence = yes dsp_silence_threshold = 2500 dsp_talking_threshold = 160 denoise = no jitterbuffer = yes talk_detection_events = yes dtmf_passthrough = no announce_user_count = no announce_join_leave = no announce_user_count_all = no announce_only_user = no send_events = no echo_events = no announce_join_leave_review = no Have a great day! Dan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20190313/557c5507/attachment.html>

...if any */ if (vcpu->arch.exception.injected) diff --git a/include/linux/kvmi_host.h b/include/linux/kvmi_host.h index a9f572df1809..7c84ca681411 100644 --- a/include/linux/kvmi_host.h +++ b/include/linux/kvmi_host.h @@ -50,6 +50,10 @@ struct kvm_vcpu_introspection { bool pending; bool send_event; } exception; + + struct { + bool loop; + } singlestep; }; struct kvm_introspection { @@ -90,6 +94,7 @@ void kvmi_handle_requests(struct kvm_vcpu *vcpu); bool kvmi_hypercall_event(struct kvm_vcpu *vcpu); bool kvmi_breakpoint_event(struct kvm_vcpu *vcpu, u64 gva, u8 insn_len); bool kvmi...

The KVM introspection subsystem provides a facility for applications running on the host or in a separate VM, to control the execution of other VMs (pause, resume, shutdown), query the state of the vCPUs (GPRs, MSRs etc.), alter the page access bits in the shadow page tables (only for the hardware backed ones, eg. Intel's EPT) and receive notifications when events of interest have taken place

The KVM introspection subsystem provides a facility for applications running on the host or in a separate VM, to control the execution of other VMs (pause, resume, shutdown), query the state of the vCPUs (GPRs, MSRs etc.), alter the page access bits in the shadow page tables (only for the hardware backed ones, eg. Intel's EPT) and receive notifications when events of interest have taken place