From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1210#note_616893068
Acked-by: Don Zickus
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Don Zickus on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1210#note_616892981
Sorry about the breakage. I need to find a better way to properly test those
changes before merging. The 'include in Releases' is one way. Not sure if
there is a better way.
From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1210#note_616861525
Acked-by: Herton R. Krzesinski
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an
From: Richard W.M. Jones on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616836433
libguestfs is another "small VM" use case. Our default memory size is 1280M
(or 3584M in virt-v2v), so I guess we won't hit this. It might be nice to
have a "crashkernel=off"
From: Justin M. Forbes on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1210
NOTE: Truncated patchset due to missing public @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the
From: Justin M. Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1185#note_616810026
Acked-by: Justin M. Forbes
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email
From: Herton R. Krzesinski on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1185#note_616737270
Acked-by: Herton R. Krzesinski
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an
From: Prarit Bhargava on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1177#note_616436703
Acked-by: Prarit Bhargava
(via approve button)
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send an email to
From: Prarit Bhargava
mod-denylist.sh: Change to denylist
Change blacklist references to denylist.
v2: modprobe still uses blacklist
v3: modprobe doesn't care what the denylist file is named
Suggested-by: Brian Masney
Signed-off-by: Prarit Bhargava
diff --git a/redhat/mod-denylist.sh
From: Prarit Bhargava on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1185#note_616422030
I assumed that it had to end in blacklist.conf but I see now that the code
only looks *in* the file for a blacklist entry. I tested this by blacklisting
the skx_edac driver,
From: Kairui Song on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616216082
I agree with "1G-4G:192M", I can update and do a rebase again.
___
kernel mailing list -- kernel@lists.fedoraproject.org
To unsubscribe send
From: Baoquan He on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616208180
"1G-4G:192M" looks good to me, and the range is consistent with rhel8.5
crashkernel on the low range.
___
kernel mailing list --
From: David Hildenbrand on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616159841
Just to be clear, I'm not strongly against this. I just can see it turn some
corner case setups broken without any clear benefit if we consider the system
requirements a
From: Dave Young on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616156922
Yes, if we regard the 1.5G minimum requirement then it would be good enough as
you said.
@baoquan_he @kasong , what do you think?
___
kernel
From: David Hildenbrand on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616152308
Exactly, and as I said, once we're dealing with such small VMs that are below
the recommended memory size, why do we even care?
1.5 GiB will work fine, with or without that patch.
From: Dave Young on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616135228
Hi David,
The details of the round up is like below:
For 1G-4G:xM, in kernel code we check if system_ram_size < 1G then kernel
does not reserve kdump memory otherwise xM mem is
From: David Hildenbrand on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1171#note_616124920
With kata-containers we run VMs as small as 256 MiB (or sometimes even
smaller). However, in these setups, we run a stripped-down OS, so we can
expect to kdump never to be
17 matches
Mail list logo
