similar to: Fwd: Re: [RFC] kvm tools: Implement multiple VQ for virtio-net

Compile issue with tools/libfsimage/iso9660 char vs unsigned char signedness causes a warning when compiling iso9660 (xen-unstable). This patch changes the unsigned char * for char *. Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca> diff -r 8eff89a69521 tools/libfsimage/iso9660/fsys_iso9660.c --- a/tools/libfsimage/iso9660/fsys_iso9660.c Fri Mar 02 18:42:00 2007 -0500 +++

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

Xen i386 xen-head.S fix sections mixup xen-head.S does not come back to the data section, leaving the text section as current section. It causes problems with a slightly enhanced DEBUG_RODATA that supports CONFIG_HOTPLUG and bringing a CPU up after the text has been marked read-only: reference to early_gdt_descr causes a page fault. It applies on 2.6.22-rc2-mm2. Signed-off-by: Mathieu Desnoyers

As planned the new release is available at: ftp://libvirt.org/libvirt/ It is a rather large release with near 400 commits included. From an user point of view the main improvement is likely to be when using migration as various work has been done to extend the protocol and to avoid having the migration command stop other concurrent operations (like virsh list). See below for a number of

On 28.04.23 11:50, Hou Wenlong wrote: > Similar to the alternative patching, use relative reference for original > instruction rather than absolute one, which saves 8 bytes for one entry > on x86_64. And it could generate R_X86_64_PC32 relocation instead of > R_X86_64_64 relocation, which also reduces relocation metadata on > relocatable builds. And the alignment could be hard

Hi, On a slightly different topic there seems to be some sort of issue with Intel chipset 915G and windows 2003. The guests seem to stop responding after some time unless you connect via VNC to the guest and move the mouse over the window, the guest them comes back to life. Another guy said it was like a symptom that he had seen before called ''lost interupt'' I was wondering if

Isolate some of the non-VMI timer related changes in Linux. This patch moves the cyc_2_ns conversion code into a common location, eliminating redundant code in hpet and tsc timer implementations, and introduces some macros that may be redefined by the sub-architecture to avoid dependence on APIC routing, CMOS time sync, and testing for broken time hardware (which presumably, does not happen in a

Isolate some of the non-VMI timer related changes in Linux. This patch moves the cyc_2_ns conversion code into a common location, eliminating redundant code in hpet and tsc timer implementations, and introduces some macros that may be redefined by the sub-architecture to avoid dependence on APIC routing, CMOS time sync, and testing for broken time hardware (which presumably, does not happen in a

On Wed, Aug 28, 2013 at 6:12 AM, Peter Hurley <peter at hurleysoftware.com> wrote: > This series was originally motivated by a deadlock, introduced in > commit 1d7c71a3e2f77336df536855b0efd2dc5bdeb41b > 'drm/nouveau/disp: port vblank handling to event interface', > due to inverted lock order between nouveau_drm_vblank_enable() > and nouveau_drm_vblank_handler() (the

Introduce a helper to retrieve the current task's work struct if it is a workqueue worker. This allows us to fix a long-standing deadlock in several DRM drivers wherein the ->runtime_suspend callback waits for a specific worker to finish and that worker in turn calls a function which waits for runtime suspend to finish. That function is invoked from multiple call sites and waiting for

Subject: Add a sched_clock paravirt_op The tsc-based get_scheduled_cycles interface is not a good match for Xen's runstate accounting, which reports everything in nanoseconds. This patch replaces this interface with a sched_clock interface, which matches both Xen and VMI's requirements. In order to do this, we: 1. replace get_scheduled_cycles with sched_clock 2. hoist cycles_2_ns

Subject: Add a sched_clock paravirt_op The tsc-based get_scheduled_cycles interface is not a good match for Xen's runstate accounting, which reports everything in nanoseconds. This patch replaces this interface with a sched_clock interface, which matches both Xen and VMI's requirements. In order to do this, we: 1. replace get_scheduled_cycles with sched_clock 2. hoist cycles_2_ns

On Mon, Aug 07, 2023 at 07:09:31PM +0800, Qi Zheng wrote: > Currently, the synchronize_shrinkers() is only used by TTM pool. It only > requires that no shrinkers run in parallel. > > After we use RCU+refcount method to implement the lockless slab shrink, > we can not use shrinker_rwsem or synchronize_rcu() to guarantee that all > shrinker invocations have seen an update before

Lockdep report [1] correctly identifies a potential deadlock between nouveau_drm_vblank_enable() and nouveau_drm_vblank_handler() due to inverted lock order of event->lock with drm core's dev->vblank_time_lock. Fix vblank event deadlock by converting event handler list to RCU. List updates remain serialized by event->lock. List traversal & handler execution is lockless which

Hi there, I am trying to install Microsoft Visual C++ Toolkit 2003, it fails with: $ wine VCToolkitSetup.exe fixme:advapi:LookupAccountNameW (null) L"mathieu" (nil) 0x33f80c (nil) 0x33f810 0x33f804 - stub fixme:advapi:LookupAccountNameW (null) L"mathieu" 0x12fd98 0x33f80c 0x12f828 0x33f810 0x33f804 - stub fixme:msi:ACTION_HandleStandardAction unhandled standard action

Hi all, The C++11 (& C11) compare_exchange functions with explicit memory order allow you to specify two sets of semantics, one for when the exchange actually happens and one for when it fails. Unfortunately, at the moment the LLVM IR "cmpxchg" instruction only has one ordering, which means we get sub-optimal codegen. This probably affects all architectures which use

On Wed, May 31, 2023 at 11:27:12AM -0500, Mike Christie wrote: >On 5/31/23 10:15 AM, Mike Christie wrote: >>>> rcu would work for your case and for what Jason had requested. >>> Yeah, so you already have some patches? >>> >>> Do you want to send it to solve this problem? >>> >> Yeah, I'll break them out and send them later today when I

On 5/31/23 10:15 AM, Mike Christie wrote: >>> rcu would work for your case and for what Jason had requested. >> Yeah, so you already have some patches? >> >> Do you want to send it to solve this problem? >> > Yeah, I'll break them out and send them later today when I can retest > rebased patches. > Just one question. Do you core vhost developers

anyone ever got this error ? [Wed Jul 26 17:36:25 2006] [error] [client 192.168.11.100] (eval):21:in `seek'', referer: http://rf.mathieu.mv.sha/diary.cgi/edit/1?someting=true [Wed Jul 26 17:36:25 2006] [error] [client 192.168.11.100] : , referer: http://rf.mathieu.mv.sha/diary.cgi/edit/1?someting=true [Wed Jul 26 17:36:25 2006] [error] [client 192.168.11.100] Illegal seek, referer: