On 03.11.23 20:48, Jason Andryuk wrote:
On Wed, Nov 1, 2023 at 6:09 AM Juergen Gross wrote:
Add the walk request of the 9pfs protocol.
Signed-off-by: Juergen Gross
---
tools/xenlogd/io.c | 138
tools/xenlogd/xenlogd.h | 1 +
2 files changed
On 03.11.23 16:13, Jason Andryuk wrote:
On Wed, Nov 1, 2023 at 5:54 AM Juergen Gross wrote:
Add the attach request of the 9pfs protocol. This introduces the "fid"
scheme of the 9pfs protocol.
As this will be needed later, use a dedicated memory allocation
function in alloc_fid().
For filling
On 05.11.2023 10:58, scan-ad...@coverity.com wrote:
> Hi,
>
> Please find the latest report on new defect(s) introduced to XenProject found
> with Coverity Scan.
>
> 1 new defect(s) introduced to XenProject found with Coverity Scan.
> 1 defect(s), reported by Coverity Scan earlier, were marked f
Hi Ayan,
On 03/11/2023 18:34, Ayan Kumar Halder wrote:
>
>
> The MMU specific code in head.S will not be used on MPU systems.
> Instead of introducing more #ifdefs which will bring complexity
> to the code, move MMU related code to mmu/head.S and keep common
> code in head.S. Two notes while mov
Hi Ayan,
On 03/11/2023 18:34, Ayan Kumar Halder wrote:
>
>
> All the MMU related functionality have been clubbed together in
> enable_boot_cpu_mm() for booting primary cpu and enable_secondary_cpu_mm() for
> booting secondary cpus.
> This is done in preparation for moving the code related to MMU
On 06.11.23 06:56, Randy Dunlap wrote:
Don't use kernel-doc markers ("/**") for comments that are not in
kernel-doc format. This prevents multiple kernel-doc warnings:
xen-front-pgdir-shbuf.c:25: warning: This comment starts with '/**', but isn't
a kernel-doc comment. Refer Documentation/doc-gu
Don't use kernel-doc markers ("/**") for comments that are not in
kernel-doc format. This prevents multiple kernel-doc warnings:
xen-front-pgdir-shbuf.c:25: warning: This comment starts with '/**', but isn't
a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* This structure repr
Hi Andrew,
> On Nov 4, 2023, at 03:50, Andrew Cooper wrote:
>
> [andcoo...@tibco.com appears similar to someone who previously sent you
> email, but may not be that person. Learn why this could be a risk at
> https://aka.ms/LearnAboutSenderIdentification ]
(+Your work email address since this
flight 183689 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183689/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 778134e491a9f53abc903f6fa730d8389f27697d
baseline version:
ovmf 038499a2681c1adab5a50
flight 183688 linux-linus real [real]
flight 183691 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/183688/
http://logs.test-lab.xenproject.org/osstest/logs/183691/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-armhf-
Hi all,
On Wed, Oct 18, 2023 at 07:11:11PM +0100, Julien Grall wrote:
[...]
> > Anyway, both Bertrand and you seems to be against the Fixes tag here. So
> > I can compromise with the "This commit fixes...". However, can Bertrand
> > or you update process/send-patches.pandoc so it is clear for a
Hi maintainers,
On Fri, Oct 13, 2023 at 08:04:42PM +0800, Leo Yan wrote:
> Currently, Xen doesn't check the status property of memory/reserved
> memory nodes, which may lead to the following issues:
>
> - If a memory node has a status "disabled" it implies that it should
> not be used. Xen does
flight 183687 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183687/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 183684
test-amd64-amd64-xl-qemuu-win7-amd64
flight 183686 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/183686/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 12 windows-install fail like 183671
test-armhf-armhf-libvirt 16 save
14 matches
Mail list logo
