RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1978730 - Change page size to 4k for aarch64
Summary: Change page size to 4k for aarch64
Keywords:
Status: CLOSED DUPLICATE of bug 1978382
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kernel
Version: 9.0
Hardware: aarch64
OS: Linux
unspecified
urgent
Target Milestone: beta
: ---
Assignee: mm-maint-bot
QA Contact: Li Wang
URL:
Whiteboard:
Depends On: 1979804
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-02 15:34 UTC by Chris von Recklinghausen
Modified: 2023-08-08 03:17 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-07-20 10:20:07 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Chris von Recklinghausen 2021-07-02 15:34:53 UTC 
Description of problem:
The decision has been made that RHEL9 on aarch64 will have 4K pages. This is the bug for the kernel change.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Thomas Huth 2021-07-07 09:24:19 UTC 
The description is very sparse - could you please elaborate on the reasons for changing the page size?

Also, is virtio-balloon now working properly with KVM guests that have a different page size? (we had some problems there in the past, see https://bugzilla.redhat.com/show_bug.cgi?id=1324092 )
Comment 3 David Hildenbrand 2021-07-07 10:57:45 UTC 
(In reply to Thomas Huth from comment #1)
> The description is very sparse - could you please elaborate on the reasons
> for changing the page size?
> 
> Also, is virtio-balloon now working properly with KVM guests that have a
> different page size? (we had some problems there in the past, see
> https://bugzilla.redhat.com/show_bug.cgi?id=1324092 )

All distributions except RHEL already switched to 4k. So we're already facing host=64k guest=4k on arm64 I guess.

virtio-balloon itself works on 4k "virtual" pages.

When the guest is 64k and the host is 4k, it works by communicating 16 virtual 4k pages to the host and "works properly". When the guest is 4k and the host is 64k, it only works if the guest reports multiple contiguous 4k pages that for a 64k page -- which is often the case, but not always. The host will discard a whole 64k page once it collected all 4k pages. But it's more an optimization we added for ppc64, and not a "working properly".

Anyhow, the future is 4k and e.g., virtio-mem will benefit heavily from that; if virtio-balloon is suboptimal for now, I don't think it's a show stopper. It was never designed to support differing page sizes, unfortunately, and we've been living with this fact on ppc64 already.
Note You need to log in before you can comment on or make changes to this bug.