similar to: xenfb issuing notify_remote_via_irq() too early

Hi, When I tested pvfb, I got the following warnings. It seems to be caused by checking/setting info->dirty without dirty_lock. We need to check/set info->dirty safely. xenfb_update_screen bogus rect 2147483647 0 2147483647 0 BUG: warning at /root/linux-2.6.18-xen.hg/drivers/xen/fbfront/xenfb.c:240/xenfb_update_screen() Call Trace: [<ffffffff8036920e>] xenfb_thread+0x19b/0x2be

Unfortunately we managed to not catch in our automatic testing this oversight during the porting of the corresponding pv-ops patch (info->irq now getting set later, which doesn''t matter for pv-ops as that has the event channel at hand). Signed-off-by: Jan Beulich <jbeulich@novell.com> --- a/drivers/xen/fbfront/xenfb.c +++ b/drivers/xen/fbfront/xenfb.c @@ -757,7 +757,7 @@ static

Hi folks There are two components, which are currently not included in the main utils package: ioemu, xenfb. ioemu is currently shipped in its own package, xenfb is not shipped at all. Should we fold them into the main utils package for simplicity? ioemu adds 300k to the package and 4300k in one dependency (libsdl1.2debian). xenfb adds another 200k to the package and 200k in one dependency

Without console= arguments on the kernel command line, the first console to register becomes enabled and the preferred console (the one behind /dev/console). This is tty (assuming CONFIG_VT_CONSOLE is enabled, which it commonly is). This is okay as long tty is a useful console. But unless we have the PV framebuffer, and it is enabled for this domain, tty0 in domU is merely a dummy. In that

Without console= arguments on the kernel command line, the first console to register becomes enabled and the preferred console (the one behind /dev/console). This is tty (assuming CONFIG_VT_CONSOLE is enabled, which it commonly is). This is okay as long tty is a useful console. But unless we have the PV framebuffer, and it is enabled for this domain, tty0 in domU is merely a dummy. In that

Without console= arguments on the kernel command line, the first console to register becomes enabled and the preferred console (the one behind /dev/console). This is tty (assuming CONFIG_VT_CONSOLE is enabled, which it commonly is). This is okay as long tty is a useful console. But unless we have the PV framebuffer, and it is enabled for this domain, tty0 in domU is merely a dummy. In that

ioemu: fix xenfb slow case update Signed-off-by: Samuel Thibault <samuel.thibault@eu.citrix.com> diff -r 067d8f19e78a tools/ioemu/hw/xenfb.c --- a/tools/ioemu/hw/xenfb.c Thu Feb 28 13:55:37 2008 +0000 +++ b/tools/ioemu/hw/xenfb.c Fri Feb 29 15:25:17 2008 +0000 @@ -1072,7 +1072,7 @@ /* A convenient function for munging pixels between different depths */ #define

Hi, I''m trying to start Xorg on a PV Fedora8 guest running 2.6.21.7 fedora stock xen kernel, however, it seems that there''s no xenfb.ko driver included in the .rpm package. The only included drivers I see in /lib/modules are: emre@xenroot:/lib/modules/2.6.21.7-3.fc8xen/kernel/drivers/xen$ ls blkback blkfront blktap netback netfront pciback however, if I look at the

Attached patch includes dz in the mouse event packet sent to the frontend. Needed for mouse wheel support in a PV guest. Please apply to xen- unstable. Signed- off- by: Pat Campbell <plc@novell.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

Hi, all. I''m trying to track down some stability issues with my Xen system, and in the course of doing so, I''ve found a few things that are probably unrelated, but things I''d like to clean up nonetheless. I have a Xen guest instance running my Xen0 kernel. When it boots I get: Jul 29 01:31:37 loki kernel: fb0: VGA16 VGA frame buffer device Jul 29 01:31:37 loki

Hi, I am not sure whether this is the right place to ask this question but here it goes. I am writing some experimental kernel modules and recently migrated from kernel 2.6.31.10 to 2.6.32.27. It seems some functions such as: bind_listening_port_to_irqhandler() and notify_remote_via_irq() are deprecated. What are their replacments? I cannot find them and get my code working on this new kernel.

Patches 1of2 and 2of2 adds multiple frame buffer resolution support to the PV xenfb frame buffer driver and the PV xenfb VNC server. API Changelog entry is included here as I did not see doc/ChangeLog when I did a tip clone this morning. --------------------------------------------------------------- API Changelog entry: PV framebuffer multiple resolution facility: Guest may send

Goodmorning, I''m currently playing with XEN/arm on my Allwinner A20 (cubieboard2) I would like to get the XENFB driver working on domU. But currently in xen/arm there''s no support for VFB, atleast qemu is not supported. But this video http://www.youtube.com/watch?v=po1IeElg8tg and this one http://www.youtube.com/watch?v=Km6gBnIqaWo is showing a working framebuffer. So there are

On 3.8-rc2 with lockdep enabled and dual-GPU setup (Macbook Pro Retina), I see two releated lock inversion issues with the EFI framebuffer, leading to possible deadlock: when X takes over from the EFI framebuffer [1] and when nouveau releases the framebuffer when being vgaswitcherood [2]. Let me know if you'd like any testing or analysis when I can get the time. Many thanks, Daniel ---

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. I started with the Xen version at http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/ca05cf1a9bdc Differences to that Xen version, for those who care: * Rewritten on top of fb deferred

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started

This is a pair of Xen para-virtual frontend device drivers: drivers/video/xen-fbfront.c provides a framebuffer, and drivers/input/xen-kbdfront provides keyboard and mouse. The backends run in dom0 user space. Differences since last post: * Required patch fixing 32-on-64 xen-blkfront included. * Cleanup when xenkbd_probe() fails fixed. * Don't store event channel in device info. I started