Skip to content
This repository has been archived by the owner on May 12, 2021. It is now read-only.

kernel: Add 4.19.8 config for x86 #278

Merged
merged 1 commit into from
Dec 14, 2018

Conversation

sboeuf
Copy link

@sboeuf sboeuf commented Dec 10, 2018

We want to make sure Kata runs on latest stable kernels so that it
benefits from the latest features.

For instance, in case of Kata relying on NEMU hypervisor, the recent
kernel patches reworking the way timer calibration is handled are
solving some boot latency issues.

Signed-off-by: Sebastien Boeuf sebastien.boeuf@intel.com

@sboeuf
Copy link
Author

sboeuf commented Dec 10, 2018

@jcvenegas here is the configuration that we need after I have reused the one from 4.14.x. The only thing I had to say Y was the new VIRTIO_MENU config option.

Both patches 0001(9p) and 0002(evged) applied properly. Problem with 0003 is that it's not needed since it's already part of the stable release 4.19.8. How do you want to handle this? I'm asking cause we have other architectures relying on 4.14.x, thinking about s390, that needs this patch.

Should we bump all architectures to 4.19.8? I don't have the hardware to check that what I'm doing is okay for other archs...

Let me know how we should proceed here.

@sboeuf
Copy link
Author

sboeuf commented Dec 10, 2018

/cc @rbradford

@jodh-intel
Copy link
Contributor

ping @kata-containers/kernel, @alicefr.

@Pennyzct
Copy link
Contributor

Pennyzct commented Dec 10, 2018

Hi~@sboeuf
I have already fired a PR #269 to bump arm guest kernel to 4.19.4 for supporting nvdimm on arm64.
And with regards to applying patches, in that pr, I have classified them based on arch.
I think that both patches 0001(9p) and 0002(evged) are generally applied for all arches and 003 is just for s390x. Wdyt?
Also, I pulled a related PR in runtime repo to refine file version.yaml to let the kernel config also arch-dependent. ;)

@Weichen81
Copy link
Contributor

For Arm64, we’re welcome 4.19.x ;)

@alicefr
Copy link

alicefr commented Dec 10, 2018

@Pennyzct 003 is s390 specific but it's applied to all arch. It could be that the patch doesn't apply to the 4.19. I need to check. The patch has been upstreamed since version 4.16

@alicefr
Copy link

alicefr commented Dec 10, 2018

Otherwise I'll fix it and also generate the s390x configs :)

@marcov
Copy link
Contributor

marcov commented Dec 10, 2018

I think that in the master branch we should just keep one set of configs & patches that applies to the kernel version specified in runtime/versions.yaml, hence we should delete old configs & patches.

We have stable- branches to keep older config versions.

The process should be:

  • update runtime/versions.yaml
  • update configs / patches in packaging

@marcov
Copy link
Contributor

marcov commented Dec 10, 2018

@Pennyzct would it be OK to converge to this same kernel version for ARM? It would make life easier for packaging.

@Pennyzct
Copy link
Contributor

hi~ @alicefr @marcov sure, let's keep one set. I will update my PR to follow the latest 4.19.8 and delete arch-dependent code in related PR. ;)

@alicefr
Copy link

alicefr commented Dec 10, 2018

@marcov should I open a PR for the s390 configs?I still need to test the kernel but I can do it quickly

@marcov
Copy link
Contributor

marcov commented Dec 10, 2018

@Pennyzct thanks!

@alicefr you can open a PR to update the s390 config to 4.19.8, and thank you for testing it.

@alicefr
Copy link

alicefr commented Dec 10, 2018

@marcov do I need to remove the s390 config 4.14 and the patch in the same PR? This PR #275 would also be worthless

@marcov
Copy link
Contributor

marcov commented Dec 10, 2018

@alicefr I think so. If it's possible, do a git mv to retain the file history. This is also what @Pennyzct is doing in #269.

Do you agree with this @sboeuf, @jodh-intel?

@marcov
Copy link
Contributor

marcov commented Dec 10, 2018

@alicefr if #275 gets merged soon you can keep it, and open a new PR for the version bump.

CONFIG_CLKBLD_I8253=y
CONFIG_MAILBOX=y
CONFIG_PCC=y

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

as far as I know kata doesn't support modules, please remove them

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh yes you're right, I haven't noticed they've been added.

@sboeuf
Copy link
Author

sboeuf commented Dec 11, 2018

@marcov @alicefr
Removing the patch 0003 from the list of patches would be ideal in a PR bumping s390 arch to kernel 4.19.8, and thanks for doing that :)
Once your PR lands, I'll rebase this one, without the need to handle the patch 0003.

@jcvenegas
Copy link
Member

@sboeuf sorry for the late response for next PRs to avoid conflicts with patches and kernel versions we need to move them to its own directory 4.18.x/patches etc

@alicefr
Copy link

alicefr commented Dec 11, 2018

@sboeuf @marcov @Pennyzct I open a PR #281 that remove the 003 patch and adds the new s390 kernel config. If you decide to keep the 4.14 config let me know and I'll change my PR consequently

Copy link
Member

@jcvenegas jcvenegas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sboeuf could you rename the file name from x86_64_kata_kvm_4.19.8 to x86_64_kata_kvm_4.19.x ?

@sboeuf sboeuf force-pushed the add_config_x86_4_19_8 branch from b6cb804 to b62b1dd Compare December 12, 2018 19:21
@sboeuf
Copy link
Author

sboeuf commented Dec 12, 2018

/test

@sboeuf
Copy link
Author

sboeuf commented Dec 12, 2018

@jcvenegas @devimc comments addressed!

@jodh-intel
Copy link
Contributor

jodh-intel commented Dec 13, 2018

lgtm

Approved with PullApprove

@marcov
Copy link
Contributor

marcov commented Dec 13, 2018

@sboeuf Can you do a git mv from the 4.14 to 4.19 config? I dont think we should keep 4.14 versioned in master.

We want to make sure Kata runs on latest stable kernels so that it
benefits from the latest features.

For instance, in case of Kata relying on NEMU hypervisor, the recent
kernel patches reworking the way timer calibration is handled are
solving some boot latency issues.

Signed-off-by: Sebastien Boeuf <sebastien.boeuf@intel.com>
@sboeuf sboeuf force-pushed the add_config_x86_4_19_8 branch from b62b1dd to 9ec1ca7 Compare December 14, 2018 15:28
@sboeuf
Copy link
Author

sboeuf commented Dec 14, 2018

@marcov

Can you do a git mv from the 4.14 to 4.19 config? I dont think we should keep 4.14 versioned in master.

Yes! Done!

@sboeuf
Copy link
Author

sboeuf commented Dec 14, 2018

/test

@marcov
Copy link
Contributor

marcov commented Dec 14, 2018

lgtm

Approved with PullApprove

@mcastelino mcastelino merged commit 9d4e6b0 into kata-containers:master Dec 14, 2018
jcvenegas pushed a commit that referenced this pull request Jul 2, 2019
Resolve issues with markdown in this repo.

Fixes #278.

Signed-off-by: James O. D. Hunt <james.o.hunt@intel.com>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

9 participants