x86: memcpy() / memset() (non-)ERMS flavors plus fallout
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v7 Latest7 patches 2 repliesIn review
- v67 patches 13 repliesSuperseded
- v56 patches 11 repliesSuperseded
Earlier versions · 2
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v4 | 6 patches | 1 reply | Superseded | |
| v3 | 7 patches | 12 replies | Superseded |
Patches in v7 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/7 | x86: suppress ERMS for internal use when MISC_ENABLE.FAST_STRING is clearxen/ xen/ xen/ | +24 | 1 reply | |
| 2/7 | x86/alternatives: serialize after (self-)modifying codexen/ | +8 | 0 replies | |
| 3/7 | x86: re-work memset()xen/ xen/ xen/ +1 more | +37 | 0 replies | |
| 4/7 | x86: re-work memcpy()xen/ xen/ xen/ | +21 | 0 replies | |
| 5/7 | x86: control memset() and memcpy() inliningxen/ | +3 | 0 replies | |
| 6/7 | x86: introduce "hot" and "cold" page clearing functionsxen/ xen/ xen/ +2 more | +86 | 0 replies | |
| 7/7 | mm: allow page scrubbing routine(s) to be arch controlledxen/ xen/ xen/ +5 more | +113 | 0 replies |
Reviews trailers per patch
All 7 patches have a Reviewed-by or Acked-by.
| Patch | Jason Andryuk | Teddy Astie | Andrew Cooper | Julien Grall | Oleksii Kurochko |
|---|---|---|---|---|---|
| 1/7 | R-b | ||||
| 2/7 | R-b | ||||
| 3/7 | R-b | ||||
| 4/7 | R-b | R-b | |||
| 5/7 | R-b | Requested-by | |||
| 6/7 | R-b | ||||
| 7/7 | R-b | A-b | R-b |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 5 reviewers.
Cover letter [PATCH v7 0/7] x86: memcpy() / memset() (non-)ERMS flavors plus fallout
While the performance varies quite a bit on older (pre-ERMS) and newer (ERMS) hardware, so far we've been going with just a single flavor of these two functions, and oddly enough with ones not consistent with one another. Using plain memcpy() / memset() on MMIO (video frame buffer) is generally okay, but the ERMS variant of memcpy() turned out to regress (boot) performance in a way easily visible to the human eye (meanwhile addressed by using ioremap_wc() there).
1: x86: suppress ERMS for internal use when MISC_ENABLE.FAST_STRING is clear 2: x86/alternatives: serialize after (self-)modifying code
3: x86: re-work memset()
4: x86: re-work memcpy()
5: x86: control memset() and memcpy() inlining
6: x86: introduce "hot" and "cold" page clearing functions
7: mm: allow page scrubbing routine(s) to be arch controlled
Jan