mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Borislav Petkov <bp@alien8.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: x86-ml <x86@kernel.org>, lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] x86/cache for v7.2-rc1
Date: Mon, 15 Jun 2026 08:17:56 -0700	[thread overview]
Message-ID: <20260615151756.GAajAXpNenJr3ksyem@fat_crate.local> (raw)

Hi Linus,

please pull the x86 resource control lineup for v7.2-rc1.

Thx.

---

The following changes since commit 7fd2df204f342fc17d1a0bfcd474b24232fb0f32:

  Linux 7.1-rc2 (2026-05-03 14:21:25 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git tags/x86_cache_for_v7.2_rc1

for you to fetch changes up to 1cfa74c683ea82d37156ccd7ab4f4659056dc701:

  fs/resctrl: Document tasks file behaviour for task id 0 and idle tasks (2026-05-08 12:27:00 +0200)

----------------------------------------------------------------
Preparatory work for MPAM counter assignment:

- Simplify the error handling path when creating monitor group event
  configuration directories

- Make the MBM event filter configurable only on architectures that
  support it and expose this with the respective file modes in the event
  config

- Disallow the MBA software controller on systems where MBM counters are
  assignable, as it requires continuous bandwidth measurement that
  assignable counters do not guarantee

- Replace a compile-time Kconfig option for fixed counter assignment
  with a per-architecture runtime property, and expose whether the
  counter assignment mode is changeable to userspace

- Continue counter allocation across all domains instead of aborting at
  the first failure

- Document that automatic MBM counter assignment is best effort and may
  not assign counters to all domains

- Document the behavior of task ID 0 and idle tasks in the resctrl tasks
  file

----------------------------------------------------------------
Ben Horgan (7):
      fs/resctrl: Tidy up the error path in resctrl_mkdir_event_configs()
      x86,fs/resctrl: Create 'event_filter' files read only if they're not configurable
      fs/resctrl: Disallow the software controller when MBM counters are assignable
      fs/resctrl: Add monitor property 'mbm_cntr_assign_fixed'
      fs/resctrl: Continue counter allocation after failure
      fs/resctrl: Document that automatic counter assignment is best effort
      fs/resctrl: Document tasks file behaviour for task id 0 and idle tasks

 Documentation/filesystems/resctrl.rst | 22 +++++++++++++------
 arch/x86/kernel/cpu/resctrl/monitor.c |  1 +
 fs/resctrl/internal.h                 |  2 ++
 fs/resctrl/monitor.c                  | 30 ++++++++++++++++++++------
 fs/resctrl/rdtgroup.c                 | 40 ++++++++++++++++++++++-------------
 include/linux/resctrl.h               | 18 ++++++++++------
 6 files changed, 78 insertions(+), 35 deletions(-)


-- 
Regards/Gruss,
    Boris.

https://people.kernel.org/tglx/notes-about-netiquette

             reply	other threads:[~2026-06-15 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-15 15:17 Borislav Petkov [this message]
2026-06-16  0:34 ` pr-tracker-bot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260615151756.GAajAXpNenJr3ksyem@fat_crate.local \
    --to=bp@alien8.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®