Re: [PATCH v2] docs/misra: document the expected sizes of integer types

On 20.03.2024 07:01, Stefano Stabellini wrote: > On Tue, 19 Mar 2024, Jan Beulich wrote: >> On 19.03.2024 04:37, Stefano Stabellini wrote: >>> On Mon, 18 Mar 2024, Jan Beulich wrote: On 16.03.2024 01:07, Stefano Stabellini wrote: > On Fri, 15 Mar 2024, Jan Beulich wrote: >> On

[XEN PATCH v2 0/1] tools: init scripts: Add missing XENCONSOLED_ARGS variable to xencommons

V2: Now without test emails ending up on the mailing list. And with the correct title prefix. I noticed that the systemd services referenced the XENCONSOLED_ARGS variable, but it was missing from xencommons. I actually ran into this when experimenting with a Qubes patch where I thought I needed

[XEN PATCH v2 1/1] tools: init scripts: Add missing XENCONSOLED_ARGS variable

The systemd xenconsoled.service uses the XENCONSOLED_ARGS variable, but it was missing from the xencommons file. Signed-off-by: Rafaël Kooi --- tools/hotplug/Linux/init.d/sysconfig.xencommons.in | 6 ++ 1 file changed, 6 insertions(+) diff --git

Re: [XEN PATCH 1/1] tools/xenstore: Add missing XENCONSOLED_ARGS variable

On 20/03/2024 08:30, Jan Beulich wrote: On 20.03.2024 08:15, Rafaël Kooi wrote: The systemd xenconsoled.service uses the XENCONSOLED_ARGS variable, but it was missing from the xencommons file. As to the title prefix: How does xenstore come into play here? Jan I don't actually remember, I may

Re: [XEN PATCH 0/1] tools/xenstore: Add missing XENCONSOLED_ARGS

Apologies, it looks like my test email ended up on the mailing list regardless of my intentions. The title should have been: Subject: [XEN PATCH 0/1] tools/xenstore: Add missing XENCONSOLED_ARGS variable to xencommons And Wei Liu and Anthony Perard should've been CC'd. I'll try to do it right

Re: [XEN PATCH 1/1] tools/xenstore: Add missing XENCONSOLED_ARGS variable

On 20.03.2024 08:15, Rafaël Kooi wrote: > The systemd xenconsoled.service uses the XENCONSOLED_ARGS variable, but > it was missing from the xencommons file. As to the title prefix: How does xenstore come into play here? Jan

Re: [PATCH] x86: increase NMI timer frequency if necessary

On 19.03.2024 21:51, Andrew Cooper wrote: > On 25/01/2024 4:55 pm, Jan Beulich wrote: >> Since the performance counters used for the NMI watchdog count non- >> halted cycles, they may count at a rate higher than cpu_khz. > > Is this in theory, or observed in practice? It's been over two months

[XEN PATCH 0/1] tools/xenstore: Add missing XENCONSOLED_ARGS

I noticed that the systemd services referenced the XENCONSOLED_ARGS variable, but it was missing from xencommons. I actually ran into this when experimenting with a Qubes patch where I thought I needed to modify this variable. It turned out to not be the case, but I figure it's good to include

[XEN PATCH 1/1] tools/xenstore: Add missing XENCONSOLED_ARGS variable

The systemd xenconsoled.service uses the XENCONSOLED_ARGS variable, but it was missing from the xencommons file. Signed-off-by: Rafaël Kooi --- tools/hotplug/Linux/init.d/sysconfig.xencommons.in | 6 ++ 1 file changed, 6 insertions(+) diff --git

[linux-5.4 test] 185095: regressions - FAIL

flight 185095 linux-5.4 real [real] flight 185105 linux-5.4 real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/185095/ http://logs.test-lab.xenproject.org/osstest/logs/185105/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run:

Re: [PATCH] x86/features: More AMD features

On 19.03.2024 18:14, Andrew Cooper wrote: > On 19/03/2024 1:11 pm, Jan Beulich wrote: >> On 19.03.2024 08:33, Jan Beulich wrote: >>> On 18.03.2024 19:13, Andrew Cooper wrote: I'm not sure about FSRSC as a name, but it definitely beats AMD's longhand name of FAST_REP_SCASB. >>> With FSRS

[xen-unstable test] 185099: tolerable trouble: fail/pass/starved - PUSHED

flight 185099 xen-unstable real [real] flight 185104 xen-unstable real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/185099/ http://logs.test-lab.xenproject.org/osstest/logs/185104/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking):

[PATCH for-9.1 v5 09/14] memory: Add Error** argument to .log_global_start() handler

Modify all .log_global_start() handlers to take an Error** parameter and return a bool. Adapt memory_global_dirty_log_start() to interrupt on the first error the loop on handlers. In such case, a rollback is performed to stop dirty logging on all listeners where it was previously enabled. Cc:

[PATCH for-9.1 v5 11/14] memory: Add Error** argument to the global_dirty_log routines

Now that the log_global*() handlers take an Error** parameter and return a bool, do the same for memory_global_dirty_log_start() and memory_global_dirty_log_stop(). The error is reported in the callers for now and it will be propagated in the call stack in the next changes. To be noted a

Re: [PATCH] xen/rwlock: Don't perpeuatite broken API in new logic

On 19.03.24 12:30, Andrew Cooper wrote: The single user wants this the sane way around. Write it as a normal static inline just like rspin_lock(). Fixes: cc3e8df542ed ("xen/spinlock: add rspin_[un]lock_irq[save|restore]()") Signed-off-by: Andrew Cooper Reviewed-by: Juergen Gross Maybe

Re: [PATCH v2] docs/misra: document the expected sizes of integer types

On Tue, 19 Mar 2024, Jan Beulich wrote: > On 19.03.2024 04:37, Stefano Stabellini wrote: > > On Mon, 18 Mar 2024, Jan Beulich wrote: > >> On 16.03.2024 01:07, Stefano Stabellini wrote: > >>> On Fri, 15 Mar 2024, Jan Beulich wrote: > On 14.03.2024 23:17, Stefano Stabellini wrote: > > Xen

<    1   2