On 6/11/2025 5:58 AM, Juergen Gross wrote:
I'm just doing a V2 of my series, but this time including the additional
support of the non-serializing and immediate forms. Lets see how this will
look like. I will drop using the EAX_EDX_* macros, but due to the reason
mentioned above I won't switch to
On 8/23/25 22:06, Elliott Mitchell wrote:
> On Sat, Aug 23, 2025 at 08:59:13AM +0100, Julien Grall wrote:
>>
>> On 22/08/2025 21:09, Elliott Mitchell wrote:
>>> Since you're not pointing to anything definite, could it be everything
>>> has been resolved?
>>
>> Unfortunately, the situation has not c
On 8/21/25 21:46, Xiaoyao Li wrote:
> On 8/22/2025 3:43 AM, Sohil Mehta wrote:
>> On 8/21/2025 12:34 PM, Sohil Mehta wrote:
>>> On 8/21/2025 6:15 AM, David Woodhouse wrote:
>>>
Hm. My test host is INTEL_HASWELL_X (0x63f). For reasons which are
unclear to me, QEMU doesn't set bit 8 of 0x80
On 8/21/25 11:25, Teddy Astie wrote:
> abi-tool is a small Rust tool that is able to parse ABI yaml
> files and generate C stubs for performing hypercalls.
>
> Signed-off-by: Teddy Astie
Would it make sense to generate the hypervisor side of the
interface in this way as well?
--
Sincerely,
Demi
Hello Oleksandr,
On 24.08.25 20:21, Oleksandr Tyshchenko wrote:
>
>
> On 07.08.25 15:33, Leonid Komarianskyi wrote:
>> Hello everyone!
>
> Hello Leonid,
>
>>
>> ### Background
>> Unlike the Linux kernel, which has supported extended shared peripheral
>> interrupts (eSPIs) since 2019 [1], Xen c
Hello Oleksandr,
Thank you for your question.
On 23.08.25 16:02, Oleksandr Tyshchenko wrote:
> [You don't often get email from olekst...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On 07.08.25 15:33, Leonid Komarianskyi wrote:
>
> Hello Leoni
Hello Oleksandr,
Thank you for your close review.
On 23.08.25 17:39, Oleksandr Tyshchenko wrote:
>
>
> On 07.08.25 15:33, Leonid Komarianskyi wrote:
>
>
> Hello Leonid
>
>> This change introduces resource management in the VGIC to handle
>> extended SPIs introduced in GICv3.1. The pending_ir
Hi Oleksandr,
Thank you for your review comments.
On 23.08.25 17:23, Oleksandr Tyshchenko wrote:
> [You don't often get email from olekst...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On 07.08.25 15:33, Leonid Komarianskyi wrote:
>
> Hello
Hello Oleksandr,
On 23.08.25 15:29, Oleksandr Tyshchenko wrote:
> [You don't often get email from olekst...@gmail.com. Learn why this is
> important at https://aka.ms/LearnAboutSenderIdentification ]
>
> On 07.08.25 15:33, Leonid Komarianskyi wrote:
>
> Hello Leonid
>
>
>> Introduced two new
From: Dmytro Prokopchuk1
Fix the following issues:
1. xen/docs/misra/deviations.rst:90: WARNING: Inline interpreted text or
phrase reference start-string without end-string. [docutils]
2. xen/docs/misra/deviations.rst:54: ERROR: Error parsing content block
for the "list-table" directive: uniform
MISRA C Rule 11.3 states: "A cast shall not be performed between a pointer
to object type and a pointer to a different object type."
Violations of this rule arise due to the 'container_of()' macro, which casts
a member of a structure to its containing structure:
container_of(ptr, type, member)
On 07.08.25 15:33, Leonid Komarianskyi wrote:
Hello everyone!
Hello Leonid,
### Background
Unlike the Linux kernel, which has supported extended shared peripheral
interrupts (eSPIs) since 2019 [1], Xen currently lacks support for this
interrupt range. For SoCs with GICv3.1+, this feature
On 2025-08-24 16:56, Dmytro Prokopchuk1 wrote:
MISRA C Rule 2.1 states: "A project shall not contain unreachable
code".
Functions that are non-returning and are not explicitly annotated with
the 'noreturn' attribute are considered a violation of this rule.
In certain cases, some functions might
MISRA C Rule 2.1 states: "A project shall not contain unreachable code."
The return statements in the 'read_file()' function is unreachable due
to function 'PrintErrMesg()' which has 'noreturn' attribute:
PrintErrMesg(name, ret);
/* not reached */
return false;
}
No ex
MISRA C Rule 2.1 states: "A project shall not contain unreachable code".
Functions that are non-returning and are not explicitly annotated with
the 'noreturn' attribute are considered a violation of this rule.
In certain cases, some functions might be non-returning in specific build
configurations
15 matches
Mail list logo