Displaying 20 results from an estimated 5000 matches similar to: "[RFC/PATCH 13/15] kvm-s390: update maintainers"
2023 Jul 12
0
[Bridge] llc needs namespace awareness asap, was Re: Patch fixing STP if bridge in non-default namespace.
(CC'ing bridge maintainers.)
Kuniyuki Iwashima <kuniyu at amazon.com> writes:
> From: Harry Coin <hcoin at quietfountain.com>
> Date: Tue, 11 Jul 2023 16:40:03 -0500
>> On 7/11/23 15:44, Andrew Lunn wrote:
>> >>>>>> The current llc_rcv.c around line 166 in net/llc/llc_input.c has
>> >>>>>>
>>
2020 Apr 30
3
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> Some devices/drivers that add memory via add_memory() and friends (e.g.,
> dax/kmem, but also virtio-mem in the future) don't want to create entries
> in /sys/firmware/memmap/ - primarily to hinder kexec from adding this
> memory to the boot memmap of the kexec kernel.
>
> In fact, such memory is never exposed via the
2020 Apr 30
3
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
David Hildenbrand <david at redhat.com> writes:
> Some devices/drivers that add memory via add_memory() and friends (e.g.,
> dax/kmem, but also virtio-mem in the future) don't want to create entries
> in /sys/firmware/memmap/ - primarily to hinder kexec from adding this
> memory to the boot memmap of the kexec kernel.
>
> In fact, such memory is never exposed via the
2007 Oct 21
2
[git pull] lguest: paravirt boot code
Hi Linus,
First attempt at git, so please pull carefully. I've just put the
three i386 boot changes in the repo for the moment. If this works I'll pile
on the 44 lguest patches.
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-lguest.git
Documentation/i386/boot.txt | 34 +++++++++++++++++++++++++++-
arch/x86/boot/compressed/head_32.S | 15 ++++++++++-
2007 Oct 21
2
[git pull] lguest: paravirt boot code
Hi Linus,
First attempt at git, so please pull carefully. I've just put the
three i386 boot changes in the repo for the moment. If this works I'll pile
on the 44 lguest patches.
git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux-2.6-lguest.git
Documentation/i386/boot.txt | 34 +++++++++++++++++++++++++++-
arch/x86/boot/compressed/head_32.S | 15 ++++++++++-
2023 May 22
1
[PATCH 1/3] signal: Don't always put SIGKILL in shared_pending
When get_pending detects the task has been marked to be killed we try to
clean up the SIGKLL by doing a sigdelset and recalc_sigpending, but we
still leave it in shared_pending. If the signal is being short circuit
delivered there is no need to put in shared_pending so this adds a check
in complete_signal.
This patch was modified from Eric Biederman <ebiederm at xmission.com>
original
2020 Apr 30
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
On 30.04.20 17:38, Eric W. Biederman wrote:
> David Hildenbrand <david at redhat.com> writes:
>
>> Some devices/drivers that add memory via add_memory() and friends (e.g.,
>> dax/kmem, but also virtio-mem in the future) don't want to create entries
>> in /sys/firmware/memmap/ - primarily to hinder kexec from adding this
>> memory to the boot memmap of the
2020 Sep 09
1
[PATCH v2 2/7] kernel/resource: move and rename IORESOURCE_MEM_DRIVER_MANAGED
On Tue, Sep 08, 2020 at 10:10:07PM +0200, David Hildenbrand wrote:
> IORESOURCE_MEM_DRIVER_MANAGED currently uses an unused PnP bit, which is
> always set to 0 by hardware. This is far from beautiful (and confusing),
> and the bit only applies to SYSRAM. So let's move it out of the
> bus-specific (PnP) defined bits.
>
> We'll add another SYSRAM specific bit soon. If we
2017 Jul 04
0
[PATCH 1/1] Update my email address
Signed-off-by: Cornelia Huck <cohuck at redhat.com>
---
MAINTAINERS | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 767e9d202adf..84155d593bba 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7285,7 +7285,7 @@ F: arch/powerpc/kvm/
KERNEL VIRTUAL MACHINE for s390 (KVM/s390)
M: Christian Borntraeger <borntraeger at de.ibm.com>
2008 Mar 20
0
[RFC/PATCH 10/15] kvm-s390: intercepts for diagnose instructions
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This patch introduces interpretation of some diagnose instruction intercepts.
Diagnose is our classic architected way of doing a hypercall. This patch
features the following diagnose codes:
- vm storage size, that tells the guest about its memory layout
- time slice end, which is used by
2020 Apr 30
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
On 30.04.20 18:33, Eric W. Biederman wrote:
> David Hildenbrand <david at redhat.com> writes:
>
>> On 30.04.20 17:38, Eric W. Biederman wrote:
>>> David Hildenbrand <david at redhat.com> writes:
>>>
>>>> Some devices/drivers that add memory via add_memory() and friends (e.g.,
>>>> dax/kmem, but also virtio-mem in the future)
2008 Mar 20
0
[RFC/PATCH 11/15] kvm-s390: add kvm to kconfig on s390
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This patch adds the virtualization submenu and the kvm option to the kernel
config. It also defines HAVE_KVM for 64bit kernels.
Acked-by: Martin Schwidefsky <schwidefsky at de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com>
Signed-off-by: Carsten Otte
2008 Mar 20
0
[RFC/PATCH 11/15] kvm-s390: add kvm to kconfig on s390
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This patch adds the virtualization submenu and the kvm option to the kernel
config. It also defines HAVE_KVM for 64bit kernels.
Acked-by: Martin Schwidefsky <schwidefsky at de.ibm.com>
Signed-off-by: Christian Borntraeger <borntraeger at de.ibm.com>
Signed-off-by: Carsten Otte
2008 Mar 20
1
[RFC/PATCH 06/15] kvm-s390: sie intercept handling
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This path introduces handling of sie intercepts in three flavors: Intercepts
are either handled completely in-kernel by kvm_handle_sie_intercept(),
or passed to userspace with corresponding data in struct kvm_run in case
kvm_handle_sie_intercept() returns -ENOTSUPP.
In case of partial
2008 Mar 20
1
[RFC/PATCH 06/15] kvm-s390: sie intercept handling
From: Carsten Otte <cotte at de.ibm.com>
From: Christian Borntraeger <borntraeger at de.ibm.com>
This path introduces handling of sie intercepts in three flavors: Intercepts
are either handled completely in-kernel by kvm_handle_sie_intercept(),
or passed to userspace with corresponding data in struct kvm_run in case
kvm_handle_sie_intercept() returns -ENOTSUPP.
In case of partial
2008 Mar 20
3
[RFC/PATCH 14/15] guest: detect when running on kvm
From: Christian Borntraeger <borntraeger at de.ibm.com>
From: Carsten Otte <cotte at de.ibm.com>
This patch adds functionality to detect if the kernel runs under the KVM
hypervisor. A macro MACHINE_IS_KVM is exported for device drivers. This
allows drivers to skip device detection if the systems runs non-virtualized.
We also define a preferred console to avoid having the ttyS0, which
2008 Mar 20
3
[RFC/PATCH 14/15] guest: detect when running on kvm
From: Christian Borntraeger <borntraeger at de.ibm.com>
From: Carsten Otte <cotte at de.ibm.com>
This patch adds functionality to detect if the kernel runs under the KVM
hypervisor. A macro MACHINE_IS_KVM is exported for device drivers. This
allows drivers to skip device detection if the systems runs non-virtualized.
We also define a preferred console to avoid having the ttyS0, which
2017 Feb 13
0
[Bug 1041] nftables in a container affects the host
https://bugzilla.netfilter.org/show_bug.cgi?id=1041
--- Comment #2 from Pablo Neira Ayuso <pablo at netfilter.org> ---
For just the record:
4.1 needs this workaround though, we have to request inclusion into -stable.
commit fdab6a4cbd8933092155449ca7253eba973ada14
Author: Eric W. Biederman <ebiederm at xmission.com>
Date: Fri Jun 19 10:41:21 2015 -0500
netfilter: nftables: Do
2018 Dec 13
0
[PATCH] Export mm_update_next_owner function for vhost-net
On 2018/12/13 ??12:47, gchen.guomin at gmail.com wrote:
> From: guomin chen <gchen.guomin at gmail.com>
>
> Under normal circumstances,When do_exit exits, mm->owner will
> be updated on exit_mm(). but when the kernel process calls
> unuse_mm() and then exits,mm->owner cannot be updated. And it
> will point to a task that has been released.
>
> Below is
2020 Apr 30
0
[PATCH v2 2/3] mm/memory_hotplug: Introduce MHP_NO_FIRMWARE_MEMMAP
Some devices/drivers that add memory via add_memory() and friends (e.g.,
dax/kmem, but also virtio-mem in the future) don't want to create entries
in /sys/firmware/memmap/ - primarily to hinder kexec from adding this
memory to the boot memmap of the kexec kernel.
In fact, such memory is never exposed via the firmware memmap as System
RAM (e.g., e820), so exposing this memory via