Displaying 20 results from an estimated 4000 matches similar to: "v2v: docs: Removed vsyscall support in Debian kernels requiring workaround (RHBZ#1592061)."
2018 Jun 17
0
[PATCH] v2v: docs: Removed vsyscall support in Debian kernels requiring workaround (RHBZ#1592061).
Thanks: Haigang Li
---
v2v/virt-v2v.pod | 19 +++++++++++++++++++
1 file changed, 19 insertions(+)
diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod
index 251b4919f..09f505f91 100644
--- a/v2v/virt-v2v.pod
+++ b/v2v/virt-v2v.pod
@@ -977,6 +977,25 @@ A recommended procedure is, before using virt-v2v, to check that the
boot kernel is the best kernel available in the guest (for example
by making
2007 Apr 18
1
[PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch
AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch
which left the vsyscall page at the top of memory (minus hole for
hypervisor) and patched the ELF header at boot.
Thoughts welcome,
Rusty.
Name: Move vsyscall page out of fixmap, above stack
Author: Gerd Hoffmann <kraxel@suse.de>
Hypervisors want to use memory at the top of the address space
(eg. 64MB for Xen, or
2007 Apr 18
1
[PATCH] Gerd Hoffman's move-vsyscall-into-user-address-range patch
AFAICT we'll pay one extra TLB entry for this patch. Zach had a patch
which left the vsyscall page at the top of memory (minus hole for
hypervisor) and patched the ELF header at boot.
Thoughts welcome,
Rusty.
Name: Move vsyscall page out of fixmap, above stack
Author: Gerd Hoffmann <kraxel@suse.de>
Hypervisors want to use memory at the top of the address space
(eg. 64MB for Xen, or
2011 Aug 03
10
[PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
- Patch 6 (optional) adds a trace event to vsyscall emulation. It will
make it easier to handle performance regression reports :)
[1]
2011 Aug 03
10
[PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
- Patch 6 (optional) adds a trace event to vsyscall emulation. It will
make it easier to handle performance regression reports :)
[1]
2011 Aug 03
10
[PATCH v2 0/6] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
- Patch 6 (optional) adds a trace event to vsyscall emulation. It will
make it easier to handle performance regression reports :)
[1]
2007 Apr 18
0
[RFC/PATCH PV_OPS X86_64 14/17] paravirt_ops - vsyscall
plain text document attachment (xx-paravirt-vsyscall.patch)
vsyscall interface updates for paravirt ops.
Signed-off-by: Steven Rostedt srostedt@redhat.com
Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
Index: clean-start/arch/x86_64/kernel/vsyscall.c
===================================================================
--- clean-start.orig/arch/x86_64/kernel/vsyscall.c
+++
2007 Apr 18
0
[RFC/PATCH PV_OPS X86_64 14/17] paravirt_ops - vsyscall
plain text document attachment (xx-paravirt-vsyscall.patch)
vsyscall interface updates for paravirt ops.
Signed-off-by: Steven Rostedt srostedt@redhat.com
Signed-off-by: Glauber de Oliveira Costa <gcosta@redhat.com>
Index: clean-start/arch/x86_64/kernel/vsyscall.c
===================================================================
--- clean-start.orig/arch/x86_64/kernel/vsyscall.c
+++
2011 Jul 27
9
[PATCH 0/5] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]?
I don't have a usable Xen setup.
Also, I'd appreciate a review of patches 4 and 5 from some
2011 Jul 27
9
[PATCH 0/5] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]?
I don't have a usable Xen setup.
Also, I'd appreciate a review of patches 4 and 5 from some
2011 Jul 27
9
[PATCH 0/5] Collected vdso/vsyscall fixes for 3.1
This fixes various problems that cropped up with the vdso patches.
- Patch 1 fixes an information leak to userspace.
- Patches 2 and 3 fix the kernel build on gold.
- Patches 4 and 5 fix Xen (I hope).
Konrad, could you could test these on Xen and run 'test_vsyscall test' [1]?
I don't have a usable Xen setup.
Also, I'd appreciate a review of patches 4 and 5 from some
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise
questions, I left in the code needed for an alternative approach (which
requires mode C code, but less build script changes).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-02-27/arch/i386/Kconfig
===================================================================
---
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise
questions, I left in the code needed for an alternative approach (which
requires mode C code, but less build script changes).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-02-27/arch/i386/Kconfig
===================================================================
---
2007 Mar 05
7
[PATCH 2/10] linux 2.6.18: COMPAT_VDSO
This adds support for CONFIG_COMPAT_VDSO. As this will certainly raise
questions, I left in the code needed for an alternative approach (which
requires mode C code, but less build script changes).
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Index: head-2007-02-27/arch/i386/Kconfig
===================================================================
---
2007 Apr 18
2
[PATCH] exec-shield style vdso move.
So, is everyone happy with this smerge of Ingo and Gerd's work?
Reposted below.
Thanks,
Rusty.
-------- Forwarded Message --------
From: Linus Torvalds <torvalds@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: [Fwd: [Fwd: FW: argh]]
Date: Wed, 17 May 2006 21:35:51 -0700 (PDT)
On Thu, 18 May 2006, Rusty Russell wrote:
>
2007 Apr 18
2
[PATCH] exec-shield style vdso move.
So, is everyone happy with this smerge of Ingo and Gerd's work?
Reposted below.
Thanks,
Rusty.
-------- Forwarded Message --------
From: Linus Torvalds <torvalds@osdl.org>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Andrew Morton <akpm@osdl.org>
Subject: Re: [Fwd: [Fwd: FW: argh]]
Date: Wed, 17 May 2006 21:35:51 -0700 (PDT)
On Thu, 18 May 2006, Rusty Russell wrote:
>
2017 Mar 02
0
heads-up: required vsyscall=emulate boot option for c5/c6 images on recent kernels
Hi,
If the pristine centos:centos5 centos:centos6 images are not
running on your brand new host running another linux distribution,
you might be hitting this issue:
https://github.com/CentOS/sig-cloud-instance-images/issues/62
https://bugs.alpinelinux.org/issues/6928
Cheers
Tru
--
Tru Huynh
http://pgp.mit.edu:11371/pks/lookup?op=get&search=0xBEFA581B
-------------- next part
2007 Apr 18
2
[RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT
Paravirt-ops guests which move the fixmap also end up moving the syscall =
VDSO. This fails if it is prelinked at a fixed address, which is why =
COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). =
Several options are available to try to address this. Jan had cooked up =
a patch for Xen that used build magic to find the parts of the VDSO that =
need relocation. I
2007 Apr 18
2
[RFC, PATCH] Fixup COMPAT_VDSO to work with CONFIG_PARAVIRT
Paravirt-ops guests which move the fixmap also end up moving the syscall =
VDSO. This fails if it is prelinked at a fixed address, which is why =
COMPAT_VDSO is broken under CONFIG_VMI (and also under CONFIG_XEN). =
Several options are available to try to address this. Jan had cooked up =
a patch for Xen that used build magic to find the parts of the VDSO that =
need relocation. I
2007 May 06
2
paravirt_ops queue rebased
I just rebased my paravirt_ops patch queue to current git. Looks like
almost all the pre-req patches are now in, which is nice.
The only missing thing from your patches was you sched_clock patches and
the sched_clock paravirt-op. Are there still problems with either your
sched_clock patch or the paravirt patch? Should I resubmit the
paravirt-sched_clock patch based on git?
The only other