[also Cc: bpf maintainers and get_maintainer output]
On Thu, May 23, 2024 at 07:52:22PM +0300, Marcel wrote:
> This seems that it was a long standing problem with the Linux kernel in
> general. bpf_probe_read should have worked for both kernel and user pointers
> but it fails with access error
On Mon, Apr 15, 2024 at 08:20:10PM -0700, Haitao Huang wrote:
> From: Sean Christopherson
>
> Add initial documentation of how to regulate the distribution of
> SGX Enclave Page Cache (EPC) memory via the Miscellaneous cgroup
> controller.
>
The doc LGTM, thanks!
Reviewed
K=Wgbbcyi36ef1-PV8VS=m6nfoqnfgudwy6v7ocnkt0ddr...@mail.gmail.com/
Signed-off-by: Bagas Sanjaya
---
Changes since v1 [2]:
* Add also OMAP hwspinlock & driver entries in CREDITS (Ohad)
I was prompted to do the removal when I was reviewing kernel-doc fix
[3]. When I was digging MAINTAINERS history (`git log --no-me
On Sat, Dec 16, 2023 at 08:59:50PM +0200, Ohad Ben Cohen wrote:
> Hi Bagas,
>
> On Sat, Dec 16, 2023 at 1:10 PM Bagas Sanjaya wrote:
> > --- a/CREDITS
> > +++ b/CREDITS
> > @@ -323,6 +323,7 @@ N: Ohad Ben Cohen
> > E: o...@wizery.com
> > D: Remote
K=Wgbbcyi36ef1-PV8VS=m6nfoqnfgudwy6v7ocnkt0ddr...@mail.gmail.com/
Signed-off-by: Bagas Sanjaya
---
I was prompted to do the removal when I was reviewing kernel-doc fix
[2]. When I was digging MAINTAINERS history (`git log --no-merges --
MAINTAINERS`), I noticed that Ohad is inactive.
This patch is based on mm-nonmm-
pin_lock_free)
> *
> * Should be called from a process context (might sleep)
> *
> - * Returns the address of the assigned hwspinlock, or NULL on error
> + * Returns: the address of the assigned hwspinlock, or %NULL on error
> */
> struct hwspinlock *devm_hwspin_lock_requ
On Thu, Nov 16, 2023 at 07:58:18PM +0100, Tobias Huschle wrote:
> Hi,
>
> when testing the EEVDF scheduler we stumbled upon a performance regression
> in a uperf scenario and would like to
> kindly ask for feedback on whether we are going into the right direction
> with our analysis so far.
>
>
On 07/09/2023 20:56, Marcus Seyfarth wrote:
> As to bisecting: Unfortunately I cannot afford the time right now to bisect
> this further as the system is used in production and already did invest a lot
> of time without success into it. Hopefully someone else can find the root
> cause of the
8 matches
Mail list logo
