On 28.10.22 06:43, Henry Wang wrote:
Hi all,
Since there will be a batch of XSAs released on Nov. 1 [1] and the original
date for
the 4.17 release was supposed to be Nov. 2, I am thinking to postpone the 4.17
release to a week later (Nov. 11) to give a little bit longer time so that:
- The sec
On Thu, Oct 27, 2022 at 9:44 PM Henry Wang wrote:
> Hi all,
>
> Since there will be a batch of XSAs released on Nov. 1 [1] and the
> original date for
> the 4.17 release was supposed to be Nov. 2, I am thinking to postpone the
> 4.17
> release to a week later (Nov. 11) to give a little bit longer
在 2022/10/21 17:09, Laurent Vivier 写道:
Signed-off-by: Laurent Vivier
Acked-by: Michael S. Tsirkin
---
I got this:
63/63 ERROR:../tests/qtest/netdev-socket.c:139:test_stream_inet_ipv6:
assertion failed (resp == expect): ("st0: index=0,type=stream,connection
error\r\n" == "st0: index=0,ty
Hi all,
Since there will be a batch of XSAs released on Nov. 1 [1] and the original
date for
the 4.17 release was supposed to be Nov. 2, I am thinking to postpone the 4.17
release to a week later (Nov. 11) to give a little bit longer time so that:
- The security team won't do anything in rush.
-
flight 174499 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174499/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 174435
test-amd64-i386-xl-qemuu-win7-amd64
Hi Roger,
> -Original Message-
> From: Roger Pau Monne
> Subject: [PATCH for-4.17 v3 2/2] vpci: refuse BAR writes only if the BAR is
> mapped
>
> Writes to the BARs are ignored if memory decoding is enabled for the
> device, and the same happen with ROM BARs if the write is an attempt
>
Hi Roger,
> -Original Message-
> From: Roger Pau Monne
> Subject: [PATCH for-4.17 v3 1/2] pci: do not disable memory decoding for
> devices
>
> Commit 75cc460a1b added checks to ensure the position of the BARs from
> PCI devices don't overlap with regions defined on the memory map.
> Whe
flight 174476 xen-4.13-testing real [real]
flight 174519 xen-4.13-testing real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/174476/
http://logs.test-lab.xenproject.org/osstest/logs/174519/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
t
flight 174512 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174512/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 99338ef81ed6e48be57f71c01af85fbbdd7030ed
baseline version:
ovmf 115cebbe4d7541c795b4f
On Thu, 27 Oct 2022 19:55:55 +0100
Ayan Kumar Halder wrote:
> If a guest is running in 32 bit mode and it tries to access
> "GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vreg_reg64_extract()
> will return the value stored "v->arch.vgic.rdist_pendbase + 4".
> This will be stored in a 6
flight 174452 xen-4.16-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174452/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 172623
test-amd64-amd64-xl-qemuu-win7-a
On Thu, 27 Oct 2022 20:09:13 +0100
Ayan Kumar Halder wrote:
Hi,
> As "spin_lock_irqsave(&v->arch.vgic.lock, flags)" saves the current interrupt
> state in "flags", "spin_unlock_irqrestore(&v->arch.vgic.lock, flags)" should
> be
> used to restore the saved interrupt state.
>
> Fixes: fe7fa1332d
flight 174460 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174460/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-examine 8 reboot fail REGR. vs. 173462
test-arm64-arm64-xl
Hello,
Krystian is working on the next bit of the Trenchboot project's plans,
specifically getting Xen able to operate with TXT directly (i.e. without
tboot in the middle).
The way TXT releases APs back to the BSP is causing some fun. All APs
release simultaneously, at a point of the BSP's choos
On 27/10/2022 17:13, Julien Grall wrote:
On 27/10/2022 16:40, Ayan Kumar Halder wrote:
On 27/10/2022 10:44, Andre Przywara wrote:
On Wed, 26 Oct 2022 19:30:04 +0100
Ayan Kumar Halder wrote:
Hi,
Hi Andre,
Hi,
Hi Julien/Andre,
I need a clarification.
I am not Andre but will ans
As "spin_lock_irqsave(&v->arch.vgic.lock, flags)" saves the current interrupt
state in "flags", "spin_unlock_irqrestore(&v->arch.vgic.lock, flags)" should be
used to restore the saved interrupt state.
Fixes: fe7fa1332dabd9ce4 ("ARM: vGICv3: handle virtual LPI pending and property
tables")
Signed-
If a guest is running in 32 bit mode and it tries to access
"GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vreg_reg64_extract()
will return the value stored "v->arch.vgic.rdist_pendbase + 4".
This will be stored in a 64bit cpu register.
So now we have the top 32 bits of GICR_PENDBASER (a
flight 174470 xen-4.14-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174470/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemuu-win7-amd64 19 guest-stop fail like 172550
test-amd64-amd64-xl-qemut-win7-a
On Fri, Oct 21, 2022 at 04:53:57PM +0200, Juergen Gross wrote:
> Today all timers are migrated to cpu 0 when the system is being
> suspended. They are not migrated back after resuming the system again.
>
> This results (at least) to problems with the credit scheduler, as the
> timer isn't handled
Hi Rahul,
On 27/10/2022 18:33, Julien Grall wrote:
>
>
> On 27/10/2022 17:08, Rahul Singh wrote:
>> Hi Julien,
>
> Hi Rahul,
>
>>> On 26 Oct 2022, at 8:48 pm, Julien Grall wrote:
>>>
>>>
>>>
>>> On 26/10/2022 15:33, Rahul Singh wrote:
Hi Julien,
>>>
>>> Hi Rahul,
>>>
> On 26 Oct 2022
flight 174450 linux-5.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174450/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-vhd broken
test-armhf-armhf-libvirt-qcow2 17 guest-star
Hi Oleksandr,
> On 26 Oct 2022, at 7:23 pm, Oleksandr Tyshchenko wrote:
>
>
>
> On Wed, Oct 26, 2022 at 8:18 PM Michal Orzel wrote:
> Hi Rahul,
>
>
> Hello all
>
> [sorry for the possible format issues]
>
>
> On 26/10/2022 16:33, Rahul Singh wrote:
> >
> >
> > Hi Julien,
> >
> >> On
On 27/10/2022 17:08, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On 26 Oct 2022, at 8:48 pm, Julien Grall wrote:
On 26/10/2022 15:33, Rahul Singh wrote:
Hi Julien,
Hi Rahul,
On 26 Oct 2022, at 2:36 pm, Julien Grall wrote:
On 26/10/2022 14:17, Rahul Singh wrote:
Hi All,
Hi Rahul,
On Thu, 27 Oct 2022 16:40:01 +0100
Ayan Kumar Halder wrote:
Hi Ayan,
> On 27/10/2022 10:44, Andre Przywara wrote:
> > On Wed, 26 Oct 2022 19:30:04 +0100
> > Ayan Kumar Halder wrote:
> >
> > Hi,
>
> Hi Andre,
>
> I need a clarification.
>
> >
> >> If a guest is running in 32 bit mode and
On 27/10/2022 16:40, Ayan Kumar Halder wrote:
On 27/10/2022 10:44, Andre Przywara wrote:
On Wed, 26 Oct 2022 19:30:04 +0100
Ayan Kumar Halder wrote:
Hi,
Hi Andre,
Hi,
I need a clarification.
I am not Andre but will answer :).
[...]
/* Writing PENDBASER with LPIs enable
Hi Michal,
> On 26 Oct 2022, at 6:17 pm, Michal Orzel wrote:
>
> Hi Rahul,
>
> On 26/10/2022 16:33, Rahul Singh wrote:
>>
>>
>> Hi Julien,
>>
>>> On 26 Oct 2022, at 2:36 pm, Julien Grall wrote:
>>>
>>>
>>>
>>> On 26/10/2022 14:17, Rahul Singh wrote:
Hi All,
>>>
>>> Hi Rahul,
>>>
>
Hi Julien,
> On 26 Oct 2022, at 8:48 pm, Julien Grall wrote:
>
>
>
> On 26/10/2022 15:33, Rahul Singh wrote:
>> Hi Julien,
>
> Hi Rahul,
>
>>> On 26 Oct 2022, at 2:36 pm, Julien Grall wrote:
>>>
>>>
>>>
>>> On 26/10/2022 14:17, Rahul Singh wrote:
Hi All,
>>>
>>> Hi Rahul,
>>>
>>>
On 27/10/2022 10:44, Andre Przywara wrote:
On Wed, 26 Oct 2022 19:30:04 +0100
Ayan Kumar Halder wrote:
Hi,
Hi Andre,
I need a clarification.
If a guest is running in 32 bit mode and it tries to access
"GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vreg_reg64_extract()
will r
On Thu, 27 Oct 2022 14:38:52 +0100
Ayan Kumar Halder wrote:
Hi Ayan,
> On 25/10/2022 14:55, Andre Przywara wrote:
> > On Tue, 25 Oct 2022 13:25:52 +0100
> > Ayan Kumar Halder wrote:
> >
> > Hi,
>
> Hi Andre,
>
> Many thanks for the explanation.
>
> I need a clarification on the issue of at
On 27.10.2022 15:23, Roger Pau Monne wrote:
> Writes to the BARs are ignored if memory decoding is enabled for the
> device, and the same happen with ROM BARs if the write is an attempt
> to change the position of the BAR without disabling it first.
>
> The reason of ignoring such writes is a limi
On 27.10.2022 15:23, Roger Pau Monne wrote:
> Commit 75cc460a1b added checks to ensure the position of the BARs from
> PCI devices don't overlap with regions defined on the memory map.
> When there's a collision memory decoding is left disabled for the
> device, assuming that dom0 will reposition t
flight 174448 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174448/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-win7-amd64 19 guest-stopfail like 174155
test-amd64-i386-xl-qemuu-win7-amd64
On 25/10/2022 14:55, Andre Przywara wrote:
On Tue, 25 Oct 2022 13:25:52 +0100
Ayan Kumar Halder wrote:
Hi,
Hi Andre,
Many thanks for the explanation.
I need a clarification on the issue of atomic access to 64bit normal
memory on R52.
Hi Andre/All,
This came up while porting Xen on
Commit 75cc460a1b added checks to ensure the position of the BARs from
PCI devices don't overlap with regions defined on the memory map.
When there's a collision memory decoding is left disabled for the
device, assuming that dom0 will reposition the BAR if necessary and
enable memory decoding.
Whi
Writes to the BARs are ignored if memory decoding is enabled for the
device, and the same happen with ROM BARs if the write is an attempt
to change the position of the BAR without disabling it first.
The reason of ignoring such writes is a limitation in Xen, as it would
need to unmap the BAR, chan
Hello,
Just two patches left, but likely the ones with more meat in them.
Previous series was release-acked by Henry, but I haven't kept the acks
in case there's delay in getting them reviewed at which point the
release-ack would expire.
Thanks, Roger.
Roger Pau Monne (2):
pci: do not disable
flight 174500 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174500/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-arm64-arm64-xl-xsm 15 migrate-support-checkfail never pass
test-arm64-arm64-xl-xsm 1
Hi Henry, Jan,
Sorry for the late reply.
On 26/10/2022 03:03, Henry Wang wrote:
-Original Message-
From: Jan Beulich
Sent: Wednesday, October 26, 2022 12:07 AM
To: Henry Wang
Cc: xen-devel@lists.xenproject.org; Andrew Cooper
; George Dunlap ;
Julien Grall ; Stefano Stabellini ;
Wei Li
On 26/10/2022 01:24, Henry Wang wrote:
Hi Julien,
-Original Message-
From: Julien Grall
Subject: Re: [PATCH for-4.14-to-4.16 0/2] Backports for XSA-409 fixes
Hi Henry,
On 25/10/2022 10:21, Henry Wang wrote:
This series is a backported series for XSA-409 fixes from master for
4.14
On 27/10/2022 10:44, Andre Przywara wrote:
On Wed, 26 Oct 2022 19:30:04 +0100
Ayan Kumar Halder wrote:
Hi,
Hi Andre,
Thanks for the feedback. Just one clarification.
If a guest is running in 32 bit mode and it tries to access
"GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vr
flight 174490 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174490/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-libvirt-xsm 15 migrate-support-checkfail never pass
test-amd64-amd64-libvirt-xsm 15 migrate-s
Hi Jan,
> -Original Message-
> From: Jan Beulich
> Subject: [PATCH][4.17?] x86: also zap secondary time area handles during
> soft reset
>
> Just like domain_soft_reset() properly zaps runstate area handles, the
> secondary time area ones also need discarding to prevent guest memory
> co
On Wed, 26 Oct 2022 19:30:04 +0100
Ayan Kumar Halder wrote:
Hi,
> If a guest is running in 32 bit mode and it tries to access
> "GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vreg_reg64_extract()
> will return the value stored "v->arch.vgic.rdist_pendbase + 4".
> This will be stored i
On 27/10/2022 10:01, Ayan Kumar Halder wrote:
On 26/10/2022 14:17, Rahul Singh wrote:
CAUTION: This message has originated from an External Source. Please
use proper judgment and caution when opening attachments, clicking
links, or responding to this email.
Hi All,
Hi Rahul,
I have a v
flight 174435 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/174435/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemut-win7-amd64 19 guest-stopfail like 174367
test-amd64-i386-xl-qemuu-win7-amd64
Hi Jan,
> -Original Message-
> From: Jan Beulich
> Subject: [PATCH][4.17] Arm32: prune (again) ld warning about mismatched
> wchar_t sizes
>
> The name change (stub.c -> common-stub.c) rendered the earlier
> workaround (commit a4d4c541f58b ["xen/arm32: avoid EFI stub wchar_t size
> linke
Hi Jan,
On 27/10/2022 10:30, Jan Beulich wrote:
The name change (stub.c -> common-stub.c) rendered the earlier
workaround (commit a4d4c541f58b ["xen/arm32: avoid EFI stub wchar_t size
linker warning"]) ineffectual.
Ah! I noticed this warning over the week-end and was wondering why it
was stil
The name change (stub.c -> common-stub.c) rendered the earlier
workaround (commit a4d4c541f58b ["xen/arm32: avoid EFI stub wchar_t size
linker warning"]) ineffectual.
Fixes: bfd3e9945d1b ("build: fix x86 out-of-tree build without EFI")
Signed-off-by: Jan Beulich
--- a/xen/arch/arm/efi/Makefile
+
Hi Jan,
On 27/10/2022 07:56, Jan Beulich wrote:
On 26.10.2022 23:24, Julien Grall wrote:
On 26/10/2022 20:22, Andrew Cooper wrote:
--- a/xen/arch/x86/mm/hap/hap.c
+++ b/xen/arch/x86/mm/hap/hap.c
@@ -345,6 +345,16 @@ unsigned int hap_get_allocation(struct domain *d)
+ ((pg & ((1
Vikram Garhwal writes:
> xenstore_record_dm_state() will also be used in aarch64 xenpv machine.
>
> Signed-off-by: Vikram Garhwal
> Signed-off-by: Stefano Stabellini
> ---
> accel/xen/xen-all.c | 2 +-
> include/hw/xen/xen.h | 2 ++
> 2 files changed, 3 insertions(+), 1 deletion(-)
>
> diff
Vikram Garhwal writes:
> From: Stefano Stabellini
>
> In preparation to moving most of xen-hvm code to an arch-neutral location,
> move the x86-specific portion of xen_set_memory to arch_xen_set_memory.
>
> Also move handle_vmport_ioreq to arch_handle_ioreq.
>
> NOTE: This patch breaks the bui
On 26/10/2022 14:17, Rahul Singh wrote:
CAUTION: This message has originated from an External Source. Please use proper
judgment and caution when opening attachments, clicking links, or responding to
this email.
Hi All,
Hi Rahul,
I have a very basic question.
At Arm, we started to imp
Vikram Garhwal writes:
> From: Stefano Stabellini
>
> In preparation to moving most of xen-hvm code to an arch-neutral location,
> move:
> - shared_vmport_page
> - log_for_dirtybit
> - dirty_bitmap
> - suspend
> - wakeup
>
> out of XenIOState struct as these are only used on x86, especially t
Vikram Garhwal writes:
> From: Stefano Stabellini
>
> On ARM it is possible to have a functioning xenpv machine with only the
> PV backends and no IOREQ server. If the IOREQ server creation fails continue
> to the PV backends initialization.
>
> Signed-off-by: Stefano Stabellini
> ---
> hw/x
Vikram Garhwal writes:
> Add a new machine xenpv which creates a IOREQ server to register/connect with
> Xen Hypervisor.
>
> Optional: When CONFIG_TPM is enabled, it also creates a tpm-tis-device, adds a
> TPM emulator and connects to swtpm running on host machine via chardev socket
> and supp
Julien Grall writes:
> Hi,
>
> There seem to be some missing patches on xen-devel (including the
> cover letter). Is that expected?
>
> On 15/10/2022 06:07, Vikram Garhwal wrote:
>> Add a new machine xenpv which creates a IOREQ server to register/connect with
>> Xen Hypervisor.
>
> I don't like
On Mon, Jul 18, 2022 at 09:15:43PM +, Volodymyr Babchuk wrote:
> Patch b4f211606011 ("vpci/msix: fix PBA accesses") introduced call to
> iounmap(), but not added corresponding include.
>
> Fixes: b4f211606011 ("vpci/msix: fix PBA accesses")
>
> Signed-off-by: Volodymyr Babchuk
Reviewed-by:
On 26/10/2022 19:30, Ayan Kumar Halder wrote:
If a guest is running in 32 bit mode and it tries to access
"GICR_PENDBASER + 4" mmio reg, it will be trapped to Xen. vreg_reg64_extract()
will return the value stored "v->arch.vgic.rdist_pendbase + 4".
This will be stored in a 64bit cpu register.
S
Vikram Garhwal writes:
> Optional: When CONFIG_TPM is enabled, it also creates a tpm-tis-device, adds a
> TPM emulator and connects to swtpm running on host machine via chardev socket
> and support TPM functionalities for a guest domain.
>
> Extra command line for aarch64 xenpv QEMU to connect
On 26.10.2022 12:20, Andrew Cooper wrote:
> +int arch_set_p2m_mempool_size(struct domain *d, uint64_t size)
> +{
> +unsigned long pages = size >> PAGE_SHIFT;
> +bool preempted = false;
> +int rc;
> +
> +if ( is_pv_domain(d) )
> +return -EOPNOTSUPP;
> +
> +if ( size & ~PA
On 26.10.2022 21:22, Andrew Cooper wrote:
> On 26/10/2022 14:42, Jan Beulich wrote:
>> On 26.10.2022 12:20, Andrew Cooper wrote:
>>> The existing XEN_DOMCTL_SHADOW_OP_{GET,SET}_ALLOCATION have problems:
>>>
>>> * All set_allocation() flavours have an overflow-before-widen bug when
>>>calculati
61 matches
Mail list logo
