Recently MemReentrancyGuard was added to DeviceState to record that the
device is engaging in I/O. The network device backend needs to update it
when delivering a packet to a device.
In preparation for such a change, add MemReentrancyGuard * as a
parameter of qemu_new_nic().
Signed-off-by: Akihik
Recently MemReentrancyGuard was added to DeviceState to record that the
device is engaging in I/O. The network device backend needs to update it
when delivering a packet to a device.
This implementation follows what bottom half does, but it does not add
a tracepoint for the case that the network d
Recently MemReentrancyGuard was added to DeviceState to record that the
device is engaging in I/O. The network device backend needs to update it
when delivering a packet to a device.
This implementation follows what bottom half does, but it does not add
a tracepoint for the case that the network d
flight 181003 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181003/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 6 xen-buildfail REGR. vs. 180691
build-arm64-xsm
On Mon, May 29, 2023 at 11:31:29PM +0300, Kirill A. Shutemov wrote:
> On Mon, May 29, 2023 at 09:27:13PM +0200, Thomas Gleixner wrote:
> > On Mon, May 29 2023 at 05:39, Kirill A. Shutemov wrote:
> > > On Sat, May 27, 2023 at 03:40:02PM +0200, Thomas Gleixner wrote:
> > > But it gets broken again on
flight 181002 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181002/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl-arndale broken
test-armhf-armhf-xl-arndale 5 host-insta
flight 181004 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181004/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 1034d223f8cc6bf8b9b86c57e564753cdad46f88
baseline version:
ovmf 8e934ab9562a33191af21
On Mon, May 29, 2023 at 09:27:13PM +0200, Thomas Gleixner wrote:
> On Mon, May 29 2023 at 05:39, Kirill A. Shutemov wrote:
> > On Sat, May 27, 2023 at 03:40:02PM +0200, Thomas Gleixner wrote:
> > But it gets broken again on "x86/smpboot: Implement a bit spinlock to
> > protect the realmode stack" w
On Mon, May 29 2023 at 05:39, Kirill A. Shutemov wrote:
> On Sat, May 27, 2023 at 03:40:02PM +0200, Thomas Gleixner wrote:
> But it gets broken again on "x86/smpboot: Implement a bit spinlock to
> protect the realmode stack" with
>
> [0.554079] node #0, CPUs:#1 #2
> [0.738071
flight 181001 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/181001/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 8e934ab9562a33191af21ce3babf1ad37a3cdc34
baseline version:
ovmf 04c5b3023e49c35d291f4
On 08/05/2023 23:11, Wei Liu wrote:
On Fri, May 05, 2023 at 05:20:42PM +0200, Mickaël Salaün wrote:
This enables guests to lock their CR0 and CR4 registers with a subset of
X86_CR0_WP, X86_CR4_SMEP, X86_CR4_SMAP, X86_CR4_UMIP, X86_CR4_FSGSBASE
and X86_CR4_CET flags.
The new KVM_HC_LOCK_CR_UPD
flight 180996 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180996/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-arm64 6 xen-buildfail REGR. vs. 180691
build-arm64-xsm
flight 180995 linux-linus real [real]
flight 181000 linux-linus real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/180995/
http://logs.test-lab.xenproject.org/osstest/logs/181000/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run
On 17/05/2023 14:47, Madhavan T. Venkataraman wrote:
Sorry for the delay. See inline...
On 5/8/23 12:29, Wei Liu wrote:
On Fri, May 05, 2023 at 05:20:40PM +0200, Mickaël Salaün wrote:
From: Madhavan T. Venkataraman
Hypervisor Enforced Kernel Integrity (Heki) is a feature that will use
the
flight 180999 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180999/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf 04c5b3023e49c35d291f41d2c39b4d12a62b8f9c
baseline version:
ovmf c0bce66068c76b5d46f90
On Tue, May 23, 2023 at 01:31:16PM +0200, Jan Beulich wrote:
> Let's have assembler symbols be consistent with C ones. In principle
> there are (a few) cases where gas can produce smaller code this way,
> just that for now there's a gas bug causing smaller code to be emitted
> even when that should
On Tue, May 23, 2023 at 01:30:51PM +0200, Jan Beulich wrote:
> Recent gas versions generate minimalistic Dwarf debug info for items
> annotated as functions and having their sizes specified [1]. "Borrow"
> Arm's END() and (remotely) derive other annotation infrastructure from
> Linux'es.
>
> For s
flight 180998 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180998/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf c0bce66068c76b5d46f901027daf1074316031ac
baseline version:
ovmf e1f5c6249af08c1df2c62
Signed-off-by: Oleksii Kurochko
Acked-by: Alistair Francis
---
Changes in V6:
- Nothing changed
---
Changes in V5:
- Nothing changed
---
Changes in V4:
- Add Acked-by: Alistair Francis
---
Changes in V3:
- Nothing changed
---
Changes in V2:
- Nothing changed
---
xen/arch/riscv/setup.c
Signed-off-by: Oleksii Kurochko
Reviewed-by: Alistair Francis
---
Changes in V6:
- trap_init() is now called after enabling the MMU.
- Add additional explanatory comments.
---
Changes in V5:
- Nothing changed
---
Changes in V4:
- Nothing changed
---
Changes in V3:
- Nothing changed
---
Ch
The patch introdcuces printk related stuff which should be deleted
after Xen common code will be available.
Signed-off-by: Oleksii Kurochko
---
Changes in V6:
- the patch was introduced in the current patch series (V6)
---
xen/arch/riscv/early_printk.c | 168 ++
The patch introduces macros: BUG(), WARN(), run_in_exception(),
assert_failed.
To be precise, the macros from generic bug implementation ()
will be used.
The implementation uses "ebreak" instruction in combination with
diffrent bug frame tables (for each type) which contains useful
information.
S
will be used in the patch "xen/riscv: introduce
decode_cause() stuff" and requires
Signed-off-by: Oleksii Kurochko
---
Changes in V6:
- Nothing changed. Only rebase.
---
Changes in V5:
* the patch was introduced in the current patch series (V5)
---
xen/arch/riscv/include/asm/bug.h | 10 +
The patch series is based on:
enable MMU for RISC-V [1]
which haven't been commited yet.
The patch series provides a basic implementation of exception handling.
It can do only basic things such as decode a cause of an exception,
save/restore registers and execute "wfi" instruction if an except
The patch introduces stuff needed to decode a reason of an
exception.
Signed-off-by: Oleksii Kurochko
---
Changes in V6:
- Remove usage of LINK_TO_LOAD() due to the MMU being enabled first.
- Change early_printk() to printk()
---
Changes in V5:
- Remove from riscv/traps/c as nothing would re
flight 180997 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180997/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
ovmf e1f5c6249af08c1df2c6257e4bb6abbf6134318c
baseline version:
ovmf 5258c4186f3a41c14a1d4
flight 180992 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/180992/
Failures :-/ but no regressions.
Tests which are failing intermittently (not blocking):
test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 18
guest-localmigrate/x10 fail in 180982 pass in 180992
On Thu, May 25, 2023 at 05:22:53PM +0200, Jan Beulich wrote:
> On 25.05.2023 16:54, Roger Pau Monne wrote:
> > When traversing the list of pci devices assigned to a domain cope with
> > some of them not having the vpci struct allocated. It should be
> > possible for the hardware domain to have read
On Wed, May 24, 2023 at 03:36:34PM -0400, Stefan Hajnoczi wrote:
On Wed, May 24, 2023 at 10:52:03AM +0200, Stefano Garzarella wrote:
On Tue, May 23, 2023 at 01:12:59PM -0400, Stefan Hajnoczi wrote:
> Stop using the .bdrv_co_io_plug() API because it is not multi-queue
> block layer friendly. Use
On Fri, May 26, 2023 at 09:35:04AM +0200, Jan Beulich wrote:
> There's no point consuming two port-I/O slots. Even less so considering
> that some real hardware permits both ports to be accessed in one go,
> emulating of which requires there to be only a single instance.
>
> Signed-off-by: Jan Beu
On Thu, May 25, 2023 at 05:30:54PM +0200, Jan Beulich wrote:
> On 25.05.2023 17:02, Roger Pau Monné wrote:
> > On Thu, May 25, 2023 at 04:39:51PM +0200, Jan Beulich wrote:
> >> On 24.05.2023 17:56, Roger Pau Monné wrote:
> >>> On Wed, May 24, 2023 at 03:45:58PM +0200, Jan Beulich wrote:
> ---
31 matches
Mail list logo