Re: [PATCH 16/18] KVM: x86: Take mem attributes into account when faulting memory

On Sun Jun 9, 2024 at 3:49 PM UTC, Nicolas Saenz Julienne wrote: > Take into account access restrictions memory attributes when faulting > guest memory. Prohibited memory accesses will cause an user-space fault > exit. > > Additionally, bypass a warning in the !tdp case. Access restrictions in > gu

Re: [PATCH 16/18] KVM: x86: Take mem attributes into account when faulting memory

On Thu, Aug 22, 2024, Nicolas Saenz Julienne wrote: > On Sun Jun 9, 2024 at 3:49 PM UTC, Nicolas Saenz Julienne wrote: > > Take into account access restrictions memory attributes when faulting > > guest memory. Prohibited memory accesses will cause an user-space fault > > exit. > > > > Additionally

[no subject]

[no subject]

[PATCH 0/5] tracing: Allow trace_printk() to use the persistent ring buffer

[ Take-two because I had an extra comma at the end of my Cc list for sending via quilt ] While debugging the rtla and timerlat issue[1], I started using trace_printk() to see what was happening as the task_struct was randomly being corrupted. But the reproducer to this bug would cause a kernel c

[PATCH 2/5] tracing: Allow trace_printk() to go to other instance buffers

From: Steven Rostedt Currently, trace_printk() just goes to the top level ring buffer. But there may be times that it should go to one of the instances created by the kernel command line. Add a new trace_instance flag: traceprintk (also can use "printk" or "trace_printk" as people tend to forget

[PATCH 1/5] tracing: Add "traceoff" flag to boot time tracing instances

From: Steven Rostedt Add a "flags" delimiter (^) to the "trace_instance" kernel command line parameter, and add the "traceoff" flag. The format is: trace_instance=[^[^]][@][,] The code allows for more than one flag to be added, but currently only "traceoff" is done so. The motivation for th

[PATCH 3/5] tracing: Have trace_printk not use binary prints if boot buffer

From: Steven Rostedt If the persistent boot mapped ring buffer is used for trace_printk(), force it to not use the binary versions. trace_printk() by default uses bin_printf() that only saves the pointer to the format and not the format itself inside the ring buffer. But for a persistent buffer t

[PATCH 5/5] tracing/Documentation: Start a document on how to debug with tracing

From: Steven Rostedt Add a new document Documentation/trace/debugging.rst that will hold various ways to debug tracing. This initial version mentions trace_printk and how to create persistent buffers that can last across bootups. Signed-off-by: Steven Rostedt (Google) --- .../admin-guide/kern

[PATCH 4/5] tracing: Add option to set an instance to be the trace_printk destination

From: Steven Rostedt Add a option "trace_printk_dest" that will make the tracing instance the location that trace_printk() will go to. This is useful if the trace_printk or one of the top level tracers is too noisy and there's a need to separate the two. Then an instance can be created, the trace