On 22.08.2025 12:52, Penny Zheng wrote:
> Change "balance" to "ondemand" in help info for "xenpm set-cpufreq-cppc"
>
> Fixes: 81ce87fc5e36 (xen/cpufreq: rename cppc preset name to
> "XEN_SYSCTL_CPPC_SET_PRESET_ONDEMAND")
> Signed-off-by: Penny Zheng
Acked-by: Jan Beulich
Change "balance" to "ondemand" in help info for "xenpm set-cpufreq-cppc"
Fixes: 81ce87fc5e36 (xen/cpufreq: rename cppc preset name to
"XEN_SYSCTL_CPPC_SET_PRESET_ONDEMAND")
Signed-off-by: Penny Zheng
---
v6 -> v7:
- new commit
---
tools/misc/xenpm.
On 5/12/25 10:58 AM, Andrew Cooper wrote:
> On 12/05/2025 11:58 am, Jan Beulich wrote:
>> On 08.05.2025 18:03, Andrew Cooper wrote:
>>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>>> stale
>>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>
On 12.05.2025 16:58, Andrew Cooper wrote:
> On 12/05/2025 11:58 am, Jan Beulich wrote:
>> On 08.05.2025 18:03, Andrew Cooper wrote:
>>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>>> stale
>>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>
On 12/05/2025 11:58 am, Jan Beulich wrote:
> On 08.05.2025 18:03, Andrew Cooper wrote:
>> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already
>> stale
>> by the time speculative vulnerabilities hit the headlines in 2018. It is
>> specifically an out-of-line-ing mechansim, and
On 08.05.2025 18:03, Andrew Cooper wrote:
> The text for CONFIG_INDIRECT_THUNK isn't really correct, and was already stale
> by the time speculative vulnerabilities hit the headlines in 2018. It is
> specifically an out-of-line-ing mechansim, and repoline is one of several
> safety sequences used.
> @@ -162,29 +162,21 @@ config STATIC_MEMORY
>> menu "Speculative hardening"
>>
>> config INDIRECT_THUNK
>> -bool "Speculative Branch Target Injection Protection"
>> +bool "Out-of-line Indirect Call/Jumps"
>> depends
fig
> +++ b/xen/common/Kconfig
> @@ -162,29 +162,21 @@ config STATIC_MEMORY
> menu "Speculative hardening"
>
> config INDIRECT_THUNK
> - bool "Speculative Branch Target Injection Protection"
> + bool "Out-of-line Indirect Call/Jumps"
&g
quot;Speculative Branch Target Injection Protection"
+ bool "Out-of-line Indirect Call/Jumps"
depends on CC_HAS_INDIRECT_THUNK
default y
help
- Contemporary processors may use speculative execution as a
- performance optimisation, but this can pote
Thank you
Caleb
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>
> Cc: "Jan Beulich"
> Sent: Friday, January 3, 2025 3:35:43 PM
> Subject: Re: Help With Identifying CPUID faulting logic
On 03/01/2025 2:25 pm, Fonyuy-Asheri Caleb wrote:
> Hello,
>
> I am interested in finding understanding how xen handles CPUID
> faulting and
> VM exits in general. Please can someone indicate to me the concerned
> files?
>
> I want to know how xen detects the execution of the CPUID instruction an
Hello,
I am interested in finding understanding how xen handles CPUID faulting and
VM exits in general. Please can someone indicate to me the concerned files?
I want to know how xen detects the execution of the CPUID instruction and
ensures a guest only gets the features defined in cpuid-auto
,
we query the size of the QSPI flash device by communicating with it, during
every boot this query is printing correct size; so the QSPI communication
seems to work but apparently anything to do with data transfers is failing.
Can someone help with the above issue, am I missing something obvious?
Thanks
Naresh
Thanks both.
I'll look to see what's possible, although if anyone could help automate
this monthly that would be greatly helpful!
Many thanks,
Kelly Choi
Community Manager
Xen Project
On Mon, Aug 19, 2024 at 9:38 AM Jan Beulich wrote:
> On 16.08.2024 20:25, Stefano Sta
On 16.08.2024 20:25, Stefano Stabellini wrote:
> xen.biterg.io was created by a company called Bitergia. Bitergia was
> later contracted by the Linux Foundation to create a generic dashboard
> for all their Open Source projects. Getting access to the Linux
> Foundation dashboard is the best way to
On Fri, 16 Aug 2024, Stefano Stabellini wrote:
> Hi Kelly,
>
> xen.biterg.io was created by a company called Bitergia. Bitergia was
> later contracted by the Linux Foundation to create a generic dashboard
> for all their Open Source projects. Getting access to the Linux
> Foundation dashboard is t
t;|@|>' '{print $3}' | sort | uniq -c | sort -rn
You need to run these commands on xen.git on a Linux machine.
Cheers,
Stefano
On Fri, 16 Aug 2024, Kelly Choi wrote:
> Hi all,
> I'm looking for a way to gather some statistics around our project, that
> would help monito
Hi all,
I'm looking for a way to gather some statistics around our project, that
would help monitor the health of the community and show our progress so
far.
AFAIK, there used to be a dashboard on https://xen.biterg.io/ (
https://wiki.xenproject.org/wiki/Code_Review_Dashboard) which no l
On Mon, Aug 05, 2024 at 04:14:34PM +0200, Juergen Gross wrote:
> On 05.08.24 16:11, John E. Krokes wrote:
> > In "xl help", the output includes this line:
> >
> > vsnd-list List virtual display devices for a domain
> >
> > This should obviou
Hi all,
As you'll know we've been working on an initiative to update documentation
so that others in the community find it easier to learn about the Xen
Project.
@Alejandro Vallejo has kindly started our
Sphinx user documentation but we need your help adding to this!
*All memb
>
> None of these require extra state (i.e. registers), hence ...
>
>> Per my current understanding, I would expect more xstates on the VM than
>> supported on the target
>> server and hence a failure with xstate verification when restoring CPU state.
>
> ... no extra "xstates" (as you name it).
On 06.08.2024 11:30, Fonyuy-Asheri Caleb wrote:
> Seems there's more to this than I think. Here's the entire information about
> my setup.
>
> Source Server:
>Processor: Intel(R) Xeon(R) Platinum 8358 CPU @ 2.60GHz
>Xsave dependences(based on xen gen-cpuid.py):
> '
> On 06.08.2024 09:34, Fonyuy-Asheri Caleb wrote:
>>> If what you say in the earlier paragraph was the case with upstream Xen and
>>> without you restricting what the guest being migrated was able to see on the
>>> source host, then I think that would indicate a bug somewhere. Yet you don't
>>>
On 06.08.2024 09:34, Fonyuy-Asheri Caleb wrote:
>> If what you say in the earlier paragraph was the case with upstream Xen and
>> without you restricting what the guest being migrated was able to see on the
>> source host, then I think that would indicate a bug somewhere. Yet you don't
>> provide e
> If what you say in the earlier paragraph was the case with upstream Xen and
> without you restricting what the guest being migrated was able to see on the
> source host, then I think that would indicate a bug somewhere. Yet you don't
> provide enough details to be certain.
>
> Jan
Sorry for not
On 06.08.2024 09:04, Fonyuy-Asheri Caleb wrote:
>> On 15/07/2024 9:16 am, Jan Beulich wrote:
>>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
> Perhaps the more important question, are you booting the skylake with
> cpuid=no-avx on the command line by any chance?
No. I didn't boot a
Hello Andrew,
Hello Jan,
Please permit me to come back to this once again.
> On 15/07/2024 9:16 am, Jan Beulich wrote:
>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
Perhaps the more important question, are you booting the skylake with
cpuid=no-avx on the command line by any chanc
On 05.08.24 16:11, John E. Krokes wrote:
In "xl help", the output includes this line:
vsnd-list List virtual display devices for a domain
This should obviously say "sound devices" instead of "display devices".
Signed-off-by: John E. Krokes
Reviewe
In "xl help", the output includes this line:
vsnd-list List virtual display devices for a domain
This should obviously say "sound devices" instead of "display devices".
Signed-off-by: John E. Krokes
---
tools/xl/xl_cmdtable.c | 2 +-
1 file chang
On Mon, 5 Aug 2024, Jan Beulich wrote:
On 04.08.2024 15:18, John E. Krokes wrote:
Here's a simple and obvious mistake:
~> xl help | grep vsnd
vsnd-attach Create a new virtual sound device
vsnd-list List virtual display devices for a domain
vsnd-detach
On 04.08.2024 15:18, John E. Krokes wrote:
> Here's a simple and obvious mistake:
>
>
> ~> xl help | grep vsnd
> vsnd-attach Create a new virtual sound device
> vsnd-list List virtual display devices for a domain
> vsnd-detach Des
Here's a simple and obvious mistake:
~> xl help | grep vsnd
vsnd-attach Create a new virtual sound device
vsnd-list List virtual display devices for a domain
vsnd-detach Destroy a domain's virtual sound device
~>
I'm pretty sure vsnd-l
On 15/07/2024 9:16 am, Jan Beulich wrote:
> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>>> Perhaps the more important question, are you booting the skylake with
>>> cpuid=no-avx on the command line by any chance?
>> No. I didn't boot any of the machines with any cpuid modification
>> whatsoev
> On 15.07.2024 10:48, Fonyuy-Asheri Caleb wrote:
> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>>> Perhaps the more important question, are you booting the skylake with
>>> cpuid=no-avx on the command line by any chance?
>>
>> No. I didn't boot any of the machines with an
On 15.07.2024 10:48, Fonyuy-Asheri Caleb wrote:
On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>> Perhaps the more important question, are you booting the skylake with
>> cpuid=no-avx on the command line by any chance?
>
> No. I didn't boot any of the machines with any cpuid m
>>> On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
> Perhaps the more important question, are you booting the skylake with
> cpuid=no-avx on the command line by any chance?
No. I didn't boot any of the machines with any cpuid modification
whatsoever.
>>>
>>> Yet is there pe
On 15.07.2024 10:22, Fonyuy-Asheri Caleb wrote:
> - Original Message -
>> From: "Jan Beulich"
>> To: "Fonyuy-Asheri Caleb"
>> Cc: "xen-devel" , "Andrew Cooper"
>>
>> Sent: Monday, July 15, 2024 10:16:07 AM
&g
- Original Message -
> From: "Jan Beulich"
> To: "Fonyuy-Asheri Caleb"
> Cc: "xen-devel" , "Andrew Cooper"
>
> Sent: Monday, July 15, 2024 10:16:07 AM
> Subject: Re: Help with Understanding vcpu xstate restore error during v
On 15.07.2024 09:38, Fonyuy-Asheri Caleb wrote:
>> Perhaps the more important question, are you booting the skylake with
>> cpuid=no-avx on the command line by any chance?
>
> No. I didn't boot any of the machines with any cpuid modification whatsoever.
Yet is there perhaps "Mitigating GDS by di
>> PV Default policy: 30 leaves, 2 MSRs
>> ...
>> 000d: -> 0003::0240:
>> 000d:0001 -> 0007:::
>
> ... PV guests get nothing, while you're trying to migrate in a guest
> which...
>
>> =
Ok, so trimming down to the relevant pieces, we have:
On 11/07/2024 12:09 pm, Fonyuy-Asheri Caleb wrote:
> =
> Source server xen-cpuid -p
> ==
On 12.07.2024 11:08, Fonyuy-Asheri Caleb wrote:
>>> I was able to locate the failure point to the file
>>> xen/arch/x86/domctl.c with the following check.
>>>
>>> if( evc->size>> evc->size>PV_XSAVE_SIZE(xfeature_mask) )
>>> gotovcpuextstate_out;
>>
>> It is certainly more complicated than that.
>>
Hi Andrew,
>> I was able to locate the failure point to the file
>> xen/arch/x86/domctl.c with the following check.
>>
>> if( evc->size> evc->size>PV_XSAVE_SIZE(xfeature_mask) )
>> gotovcpuextstate_out;
>
> It is certainly more complicated than that.
>
> What that's saying is that Xen doesn't
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb"
> Cc: "xen-devel" , "Jan Beulich"
> , "Roger Pau Monné"
>
> Sent: Thursday, July 11, 2024 3:04:05 PM
> Subject: Re: Help with Understanding
On 11/07/2024 1:18 pm, Fonyuy-Asheri Caleb wrote:
>>> Please do you mind giving me more insight on the logic currently implemented
>>> and maybe what is wrong with it? It will be important for me since what I'm
>>> doing is research work.
>> See 9e6dbbe8bf40^..267122a24c49
> What reference is this
>> Please do you mind giving me more insight on the logic currently implemented
>> and maybe what is wrong with it? It will be important for me since what I'm
>> doing is research work.
>
> See 9e6dbbe8bf40^..267122a24c49
What reference is this please?
>
>> How do the values evc->size and xf
On 11/07/2024 12:09 pm, Fonyuy-Asheri Caleb wrote:
> - Original Message -
>> From: "Andrew Cooper"
>> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>>
>> Sent: Thursday, July 11, 2024 12:45:18 PM
>> Subject: Re: Help with Unders
- Original Message -
> From: "Andrew Cooper"
> To: "Fonyuy-Asheri Caleb" , "xen-devel"
>
> Sent: Thursday, July 11, 2024 12:45:18 PM
> Subject: Re: Help with Understanding vcpu xstate restore error during vm
> migration
> On 11/07
On 11/07/2024 11:38 am, Fonyuy-Asheri Caleb wrote:
> Hello,
>
> I am trying to understand the causes of the vcpu xstate restore error
> during live migration.
> I get the following error during live migration:
>
> xc: error: Failed to set vcpu0's xsave info (22 = Invalid argument):
> Internal e
Hello,
I am trying to understand the causes of the vcpu xstate restore error during
live migration.
I get the following error during live migration:
xc: error: Failed to set vcpu0's xsave info (22 = Invalid argument): Internal
error
I was able to locate the failure point to the file xen/ar
ain_dt_overlay, 0, 1,
"Add/Remove a device tree overlay",
- "add/remove <.dtbo>"
+ "add/remove <.dtbo>",
"-h print this help\n"
},
#endif
diff --git a/tools/xl/xl_vmcontrol.c b/tools/xl/xl_vmcontrol.c
index 98f6bd2e7
ain_dt_overlay, 0, 1,
"Add/Remove a device tree overlay",
- "add/remove <.dtbo>"
+ "add/remove <.dtbo>",
"-h print this help\n"
},
#endif
diff --git a/tools/xl/xl_vmcontrol.c b/tools/xl/xl_vmcontrol.c
index 98f6bd2e7
mdtable.c b/tools/xl/xl_cmdtable.c
> index 62bdb2aeaa..1f3c6b5897 100644
> --- a/tools/xl/xl_cmdtable.c
> +++ b/tools/xl/xl_cmdtable.c
> @@ -635,7 +635,7 @@ const struct cmd_spec cmd_table[] = {
> { "dt-overlay",
>&main_dt_overlay, 0, 1,
>"Add/Remove
uot;,
&main_dt_overlay, 0, 1,
"Add/Remove a device tree overlay",
- "add/remove <.dtbo>"
+ "add/remove <.dtbo>",
"-h print this help\n"
},
#endif
diff --git a/tools/xl/xl_vmcontrol.c b/tools/xl/xl_vmcontr
amp;main_dt_overlay, 0, 1,
"Add/Remove a device tree overlay",
- "add/remove <.dtbo>"
+ "add/remove <.dtbo>",
"-h print this help\n"
},
#endif
diff --git a/tools/xl/xl_vmcontrol.c b/tools/xl/xl_vmcontrol.c
index 98f6
On 2024-05-16 06:03, Henry Wang wrote:
Fix the name mismatch in the xl dt-overlay command, the
command name should be "dt-overlay" instead of "dt_overlay".
Add the missing "," in the cmdtable.
Fix the exit code of the dt-overlay command, use EXIT_FAILURE
instead of ERROR_FAIL.
Fixes: 61765a07e3
lay",
- "add/remove <.dtbo>"
+ "add/remove <.dtbo>",
"-h print this help\n"
},
#endif
diff --git a/tools/xl/xl_vmcontrol.c b/tools/xl/xl_vmcontrol.c
index 98f6bd2e76..02575d5d36 100644
--- a/tools/xl/xl_vmcontrol.c
+++
--- a/tools/xl/xl_vmcontrol.c
+++ b/tools/xl/xl_vmcontrol.c
@@ -1278,7 +1278,7 @@ int main_dt_overlay(int argc, char **argv)
const int overlay_remove_op = 2;
if (argc < 2) {
-help("dt_overlay");
+help("dt-overlay");
return EXIT_FAILURE;
On Thu, 2024-05-02 at 19:10 +0100, Andrew Cooper wrote:
> We deprecated the use of ---help--- a while ago, but a lot of new
> content
> copy&pastes bad examples. Convert the remaining instances, and
> update
> Kconfig's parser to no longer recongise it.
>
> This
On Thu, 2 May 2024, Andrew Cooper wrote:
> We deprecated the use of ---help--- a while ago, but a lot of new content
> copy&pastes bad examples. Convert the remaining instances, and update
> Kconfig's parser to no longer recongise it.
>
> This now causes builds to fail wi
We deprecated the use of ---help--- a while ago, but a lot of new content
copy&pastes bad examples. Convert the remaining instances, and update
Kconfig's parser to no longer recongise it.
This now causes builds to fail with:
Kconfig.debug:8: syntax error
Kconfig.debug:7: unknown
On 16.03.24 00:32, Stefano Stabellini wrote:
Hi Dominique,
You posted this configuration:
device_model_args = [ "
"-device","nec-usb-xhci,id=xhci",
"-device","usb-host,bus=xhci.0,hostbus=1,hostport=13",
"-device","usb-host,bus
Cheers,
Stefano
On Thu, 14 Mar 2024, LARRIEU Dominique wrote:
> Hi Julien,
>
>
>
> You will find here above the answers to your questions.
>
>
>
> Thank you very much for your help.
>
>
>
> Best regards,
>
> Dominique
>
>
>
>
&
Hi Julien,
You will find here above the answers to your questions.
Thank you very much for your help.
Best regards,
Dominique
-Message d'origine-
De : Julien Grall mailto:jul...@xen.org>>
Envoyé : jeudi 29 février 2024 12:52
À : LARRIEU Dominique
mailto:dom
s] : we are using the USB chipset of the mother board (see below the
references)
Thanks for the clarification. IIUC, you said you are having problem in
the guest itself. Have you tried to access the same USB device from
dom0? Or better without any Xen involved (i.e. booting Debian on baremetal).
ger@citrix.com>>; Andrew Cooper
mailto:andrew.coop...@citrix.com>>; George Dunlap
mailto:george.dun...@citrix.com>>; Jan Beulich
mailto:jbeul...@suse.com>>; Juergen Gross
mailto:jgr...@suse.com>> Objet : Re: IMPORTANT - : Need help
on USB port virtualization with
France
De : Rob Townley De
Envoyé : dimanche 25 février 2024 13:20
À : Julien Grall
Cc : Andrew Cooper ; GOURLOT Francois
; George Dunlap ;
Jan Beulich ; Juergen Gross ; Kelly Choi
; Roger Pau Monné ;
xen-devel@lists.xenproject.org
Objet : Re: IMPORTANT - : Need help on USB port
sniffing USB
traffic, but my name is not Heisenberg and not sure if that traffic
monitoring does not also slow down other devices.
On Sat, Feb 24, 2024 at 8:39 AM Julien Grall wrote:
> Hi Dominique and Francois,
>
> Thank you for the report. I am CCing some person who I think could help.
&
Hi Dominique and Francois,
Thank you for the report. I am CCing some person who I think could help.
I also have some questions (see below).
On 23/02/2024 16:00, GOURLOT Francois wrote:
Dear All,
We send you a message few days ago.
We have major performance with XEN USB Drivers. We use your
; Kelly Choi
Objet : Need help on USB port virtualization with Xen hypervisor
Critère de diffusion : Confidentiel
Dear all,
We are detecting several issues with USB port virtualization with the Xen
hypervisor.
- We cannot do PCI passthrough of the PCI usb bus on a Windows 10 1607 64-bit
virtual
virtual machine,
we notice that the speed of the USB port is not high speed but full speed on a
USB 3.0 port
- We notice instabilities when using the nec-usb-xhci driver, USB 2.0 keys are
not recognized by the Windows virtual machine (incorrect descriptor)
We need your help to find a solution
On 2023-11-17 10:21, Nicola Vetrini wrote:
Static analysis tools may detect a possible null pointer
dereference of 'config'. This ASSERT helps them in detecting
that such a condition is not possible given that only
real domains can enter this branch, which are guaranteeed to have
a non-NULL confi
Static analysis tools may detect a possible null pointer
dereference of 'config'. This ASSERT helps them in detecting
that such a condition is not possible given that only
real domains can enter this branch, which are guaranteeed to have
a non-NULL config at this point, but this information is not
On 2023-11-11 02:13, Stefano Stabellini wrote:
On Fri, 10 Nov 2023, Nicola Vetrini wrote:
Hi everyone,
I trimmed the thread a bit, to make this more readable.
> > > > > IMHO, the only viable option would be to have a configuration to
> > > > > keep
> > > > > ASSERT in production build for scan
On Fri, 10 Nov 2023, Nicola Vetrini wrote:
> Hi everyone,
>
> I trimmed the thread a bit, to make this more readable.
>
> > > > > > IMHO, the only viable option would be to have a configuration to
> > > > > > keep
> > > > > > ASSERT in production build for scanning tools.
> > > > >
> > > > > But
gt;>
>> I have an idea that might resolve this differently and in an easier way.
>>
>> Would you be happy waiting for a couple of days for me to experiment?
>> Absolutely no guarantees of it turning into a workable solution.
>>
>
> Sure, no problem.
>
I
Hi everyone,
I trimmed the thread a bit, to make this more readable.
IMHO, the only viable option would be to have a configuration to
keep
ASSERT in production build for scanning tools.
But wouldn't that then likely mean scanning to be done on builds not
also
used in production? Would doing
Hi Stefano,
On 10/11/2023 00:29, Stefano Stabellini wrote:
On Thu, 9 Nov 2023, Julien Grall wrote:
On 09/11/2023 07:42, Jan Beulich wrote:
On 08.11.2023 14:33, Julien Grall wrote:
Hi Jan,
On 08/11/2023 11:19, Jan Beulich wrote:
On 08.11.2023 12:03, Nicola Vetrini wrote:
On 2023-11-08 09:24
On Thu, 9 Nov 2023, Julien Grall wrote:
> On 09/11/2023 07:42, Jan Beulich wrote:
> > On 08.11.2023 14:33, Julien Grall wrote:
> > > Hi Jan,
> > >
> > > On 08/11/2023 11:19, Jan Beulich wrote:
> > > > On 08.11.2023 12:03, Nicola Vetrini wrote:
> > > > > On 2023-11-08 09:24, Jan Beulich wrote:
> >
Hi Jan,
On 09/11/2023 07:42, Jan Beulich wrote:
On 08.11.2023 14:33, Julien Grall wrote:
Hi Jan,
On 08/11/2023 11:19, Jan Beulich wrote:
On 08.11.2023 12:03, Nicola Vetrini wrote:
On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
Static analysis tools may d
On 08.11.2023 14:28, Nicola Vetrini wrote:
> On 2023-11-08 12:19, Jan Beulich wrote:
>> On 08.11.2023 12:03, Nicola Vetrini wrote:
>>> On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
> Static analysis tools may detect a possible null
> pointer derefer
On 08.11.2023 14:33, Julien Grall wrote:
> Hi Jan,
>
> On 08/11/2023 11:19, Jan Beulich wrote:
>> On 08.11.2023 12:03, Nicola Vetrini wrote:
>>> On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
> Static analysis tools may detect a possible null
> poin
On 2023-11-08 14:37, Andrew Cooper wrote:
On 03/11/2023 5:58 pm, Nicola Vetrini wrote:
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain.c. This ASSERT helps them in
detecting that such a condition is not possible
and also pro
On 03/11/2023 5:58 pm, Nicola Vetrini wrote:
> Static analysis tools may detect a possible null
> pointer dereference at line 760 (the memcpy call)
> of xen/common/domain.c. This ASSERT helps them in
> detecting that such a condition is not possible
> and also provides a basic sanity check.
>
> Sig
Hi Jan,
On 08/11/2023 11:19, Jan Beulich wrote:
On 08.11.2023 12:03, Nicola Vetrini wrote:
On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain
On 2023-11-08 12:19, Jan Beulich wrote:
On 08.11.2023 12:03, Nicola Vetrini wrote:
On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain.c. This
On 08.11.2023 12:03, Nicola Vetrini wrote:
> On 2023-11-08 09:24, Jan Beulich wrote:
>> On 03.11.2023 18:58, Nicola Vetrini wrote:
>>> Static analysis tools may detect a possible null
>>> pointer dereference at line 760 (the memcpy call)
>>> of xen/common/domain.c. This ASSERT helps them in
>>> det
On 2023-11-08 09:24, Jan Beulich wrote:
On 03.11.2023 18:58, Nicola Vetrini wrote:
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain.c. This ASSERT helps them in
detecting that such a condition is not possible
and also provide
On 03.11.2023 18:58, Nicola Vetrini wrote:
> Static analysis tools may detect a possible null
> pointer dereference at line 760 (the memcpy call)
> of xen/common/domain.c. This ASSERT helps them in
> detecting that such a condition is not possible
> and also provides a basic sanity check.
I disagr
On Fri, 3 Nov 2023, Nicola Vetrini wrote:
> On 2023-11-03 18:58, Nicola Vetrini wrote:
> > Static analysis tools may detect a possible null
> > pointer dereference at line 760 (the memcpy call)
> > of xen/common/domain.c. This ASSERT helps them in
> > detecting that such a condition is not possible
On 2023-11-03 18:58, Nicola Vetrini wrote:
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain.c. This ASSERT helps them in
detecting that such a condition is not possible
and also provides a basic sanity check.
Suggested-by: J
Static analysis tools may detect a possible null
pointer dereference at line 760 (the memcpy call)
of xen/common/domain.c. This ASSERT helps them in
detecting that such a condition is not possible
and also provides a basic sanity check.
Signed-off-by: Nicola Vetrini
---
The check may be later imp
On Fri, May 26, 2023 at 1:38 PM Olaf Hering wrote:
> Invoking the --help option of any tool should not return with an error,
> if that tool does have a documented and implemented help option.
>
> Adjust the usage() function to exit with either error or success.
> Handle the existi
Hi Julien,
> -Original Message-
> Subject: [PATCH] xen/dt: Rework the prototype of dt_property_read_string()
> to help Eclair
>
> From: Julien Grall
>
> Eclair vXXX is unable to prove the parameter out_string will only be
> used the return of dt_property_read_s
On Mon, 24 Jul 2023, Julien Grall wrote:
> From: Julien Grall
>
> Eclair vXXX is unable to prove the parameter out_string will only be
> used the return of dt_property_read_string() is 0. So it will consider
> that MISRA C:2012 Rule 9.1 was violated.
>
> Rework the prototype so the string is ret
Hi Nicola,
On 24/07/2023 13:58, Nicola Vetrini wrote:
On 24/07/23 12:24, Julien Grall wrote:
From: Julien Grall
Eclair vXXX is unable to prove the parameter out_string will only be
used the return of dt_property_read_string() is 0. So it will consider
that MISRA C:2012 Rule 9.1 was violated
On 24/07/23 12:24, Julien Grall wrote:
From: Julien Grall
Eclair vXXX is unable to prove the parameter out_string will only be
used the return of dt_property_read_string() is 0. So it will consider
that MISRA C:2012 Rule 9.1 was violated.
This is not correct: ECLAIR cannot prove that the r
From: Julien Grall
Eclair vXXX is unable to prove the parameter out_string will only be
used the return of dt_property_read_string() is 0. So it will consider
that MISRA C:2012 Rule 9.1 was violated.
Rework the prototype so the string is returned and use ERR_PTR() to
embed the error code.
Signe
Hi Julien,
Thank you for your answer. Do you have any advice on how to debug the
issue?
I have very little experience with xen so I think I still need
debugging even if I can
get MBI-gen's tech doc...
Best regards,
Jiatong Shen
On Fri, Jun 30, 2023 at 5:42 AM Julien Grall wrote:
> On 24/06/
On 24/06/2023 15:54, Jiatong Shen wrote:
Hello Julien,
Hi,
Thank you very much for your reply. Can you teach me how to find the
relationship between MBI-gen and devices?
I am not sure how to find out the mbi-gen backed devices..
I am afraid I don't have any experience with the MBI-gen.
1 - 100 of 224 matches
Mail list logo
