Re: [linux-next:master] BUILD REGRESSION a54df7622717a40ddec95fd98086aff8ba7839a6

2023-01-24 Thread Andrew Morton
On Wed, 25 Jan 2023 00:37:05 +0800 kernel test robot wrote: > tree/branch: > https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master > branch HEAD: a54df7622717a40ddec95fd98086aff8ba7839a6 Add linux-next > specific files for 20230124 > > Error/Warning: (r

Re: [PATCH 0/6] A few cpuidle vs rcu fixes

2023-01-24 Thread Mark Rutland
On Tue, Jan 24, 2023 at 05:30:29PM +, Mark Rutland wrote: > On Tue, Jan 24, 2023 at 04:34:23PM +, Mark Rutland wrote: > > Hi Peter, > > > > On Mon, Jan 23, 2023 at 09:50:09PM +0100, Peter Zijlstra wrote: > > > 0-day robot reported graph-tracing made the cpuidle-vs-rcu rework go > > > spla

Re: [PATCH 0/6] A few cpuidle vs rcu fixes

2023-01-24 Thread Mark Rutland
On Tue, Jan 24, 2023 at 04:34:23PM +, Mark Rutland wrote: > Hi Peter, > > On Mon, Jan 23, 2023 at 09:50:09PM +0100, Peter Zijlstra wrote: > > 0-day robot reported graph-tracing made the cpuidle-vs-rcu rework go splat. > > Do you have a link toe the splat somewhere? > > I'm assuming that this

Re: [PATCH 3/6] ftrace/x86: Warn and ignore graph tracing when RCU is disabled

2023-01-24 Thread Mark Rutland
On Tue, Jan 24, 2023 at 03:44:35PM +0100, Peter Zijlstra wrote: > On Mon, Jan 23, 2023 at 05:07:53PM -0500, Steven Rostedt wrote: > > > Actually, perhaps we can just add this, and all you need to do is create > > and set CONFIG_NO_RCU_TRACING (or some other name). > > Elsewhere I've used CONFIG_A

[linux-next:master] BUILD REGRESSION a54df7622717a40ddec95fd98086aff8ba7839a6

2023-01-24 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master branch HEAD: a54df7622717a40ddec95fd98086aff8ba7839a6 Add linux-next specific files for 20230124 Error/Warning: (recently discovered and may have been fixed) ERROR: modpost: "devm_platform_ioremap_res

Re: [PATCH 0/6] A few cpuidle vs rcu fixes

2023-01-24 Thread Mark Rutland
Hi Peter, On Mon, Jan 23, 2023 at 09:50:09PM +0100, Peter Zijlstra wrote: > 0-day robot reported graph-tracing made the cpuidle-vs-rcu rework go splat. Do you have a link toe the splat somewhere? I'm assuming that this is partially generic, and I'd like to make sure I test the right thing on arm

Re: [RFC] memory pressure detection in VMs using PSI mechanism for dynamically inflating/deflating VM memory

2023-01-24 Thread David Hildenbrand
On 24.01.23 00:04, Sudarshan Rajagopalan wrote: [...] One problematic thing is that adding memory to Linux by virtio-mem eventually consumes memory (e.g., the memmap), especially when having to to add a completely new memory block to Linux. Yes we have thought about this issue as well where-in

Re: [PATCH 3/6] ftrace/x86: Warn and ignore graph tracing when RCU is disabled

2023-01-24 Thread Peter Zijlstra
On Mon, Jan 23, 2023 at 05:07:53PM -0500, Steven Rostedt wrote: > Actually, perhaps we can just add this, and all you need to do is create > and set CONFIG_NO_RCU_TRACING (or some other name). Elsewhere I've used CONFIG_ARCH_WANTS_NO_INSTR for this. Anyway, I took it for a spin and it doesn

Re: [PATCH 6/6] cpuidle: Fix poll_idle() noinstr annotation

2023-01-24 Thread Rafael J. Wysocki
On Mon, Jan 23, 2023 at 9:58 PM Peter Zijlstra wrote: > > The instrumentation_begin()/end() annotations in poll_idle() were > complete nonsense. Specifically they caused tracing to happen in the > middle of noinstr code, resulting in RCU splats. > > Now that local_clock() is noinstr, mark up the r

Re: [PATCH 2/2] vhost: check for pending livepatches from vhost worker kthreads

2023-01-24 Thread Petr Mladek via Virtualization
On Fri 2023-01-20 16:12:22, Seth Forshee (DigitalOcean) wrote: > Livepatch relies on stack checking of sleeping tasks to switch kthreads, > so a busy kthread can block a livepatch transition indefinitely. We've > seen this happen fairly often with busy vhost kthreads. To be precise, it would be "i

Re: [PATCH v2 1/1] virtio_net: notify MAC address change on device initialization

2023-01-24 Thread Laurent Vivier
On 1/24/23 11:15, Michael S. Tsirkin wrote: On Mon, Jan 23, 2023 at 01:00:22PM +0100, Laurent Vivier wrote: In virtnet_probe(), if the device doesn't provide a MAC address the driver assigns a random one. As we modify the MAC address we need to notify the device to allow it to update all the rel

Re: [PATCH v2 1/1] virtio_net: notify MAC address change on device initialization

2023-01-24 Thread Michael S. Tsirkin
On Mon, Jan 23, 2023 at 01:00:22PM +0100, Laurent Vivier wrote: > In virtnet_probe(), if the device doesn't provide a MAC address the > driver assigns a random one. > As we modify the MAC address we need to notify the device to allow it > to update all the related information. > > The problem can