Public bug reported:
Using libvirt on Ubuntu 19.10, I get the following error when I try to
set to the latest qemu from git (commit dc65a5bdc9):
error: internal error: Failed to start QEMU binary /usr/local/bin
/qemu-system-x86_64 for probing:
/home/joey/git/qemu/target/i386/kvm.c:2176:kvm_a
On Fri, 10 Jan. 2020, 08:42 Peter Maydell, wrote:
> Hi; somebody pointed out to me that hw/arm/xlnx-zynqmp.c only
> sets the psci-conduit on the A-profile cores, not the R. This
> means you can't set the boot-cpu to an R-profile core and
> use PSCI to wake up the other one. Is the omission delibe
On Thu, Jan 9, 2020 at 12:13 AM Philippe Mathieu-Daudé
wrote:
> On 1/8/20 9:00 PM, Niek Linnenbank wrote:
> > The Allwinner H3 is a System on Chip containing four ARM Cortex A7
> > processor cores. Features and specifications include DDR2/DDR3 memory,
> > SD/MMC storage cards, 10/100/1000Mbit eth
Thanks for all the help Laurent! I'm new to git so not surre how to
'properly' revert a previous commit on top of master, so I'll google,
but if you have some a good link please do send.
Also, I've heard of the term "bisect" for figuring out at which commit
something breaks and if there were some
On Sat, Jan 11, 2020 at 7:43 AM Aleksandar Markovic
wrote:
>
> From: Aleksandar Markovic
>
> Currently, there is no usage of TARGET_NR_syscall_count for target
> xtensa, and there is no obvious indication if there is some planned
> usage in future.
>
> ---
>
> cc: Max Filippov
> ---
> linux-use
Public bug reported:
When using 'ecall' from supervisor mode, user exception is raised
instead of supervisor exception. The problem is located under
'target/riscv/insn_trans/trans_priviledged.inc.c' in function 'static
bool trans_ecall(DisasContext *ctx, arg_ecall *a)'. Best regards, Serge
Teodori
Patchew URL:
https://patchew.org/QEMU/1578757241-29583-1-git-send-email-aleksandar.marko...@rt-rk.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Subject: [PATCH v4 00/19] linux-user: Misc patches for 5.0
Type: series
Message-id: 15787572
From: Aleksandar Markovic
KCOV_ENABLE and KCOV_DISABLE play the role in kernel coverage
tracing. These ioctls do not use the third argument of ioctl()
system call and are straightforward to implement in QEMU.
Signed-off-by: Aleksandar Markovic
---
linux-user/ioctls.h | 5 +
linux-use
From: Aleksandar Markovic
FDFMTBEG, FDFMTTRK, and FDFMTEND ioctls provide means for controlling
formatting of a floppy drive.
FDFMTTRK's third agrument is a pointer to the structure:
struct format_descr {
unsigned int device,head,track;
};
defined in Linux kernel header .
Since all fields
From: Aleksandar Markovic
FDGETFDCSTAT's third agrument is a pointer to the structure:
struct floppy_fdc_state {
int spec1;
int spec2;
int dtr;
unsigned char version;
unsigned char dor;
unsigned long address;
unsigned int rawcmd:2;
unsigned int reset:1;
unsign
From: Aleksandar Markovic
kcov is kernel code coverage tracing tool. It requires kernel 4.4+
compiled with certain kernel options. Its interface consists of
three ioctls.
This patch checks if kcov support is present on build machine, and
stores the result in variable CONFIG_KCOV, meant to be use
From: Aleksandar Markovic
FITRIM ioctl accepts a pointer to the structure
struct fstrim_range {
__u64 start;
__u64 len;
__u64 minlen;
};
as its third argument.
All ioctls in this group (FI* ioctl) are guarded with "#ifdef", so the
guards are used in this implementation
From: Aleksandar Markovic
KCOV_INIT_TRACE ioctl plays the role in kernel coverage tracing.
This ioctl's third argument is of type 'unsigned long', and the
implementation in QEMU is straightforward.
Signed-off-by: Aleksandar Markovic
---
linux-user/ioctls.h | 1 +
linux-user/syscall_defs.
From: Aleksandar Markovic
Both FS_IOC_FSGETXATTR and FS_IOC_FSSETXATTR accept a pointer to
the structure
struct file_clone_range {
__s64 src_fd;
__u64 src_offset;
__u64 src_length;
__u64 dest_offset;
};
as their third argument.
These ioctls were relatively recen
From: Aleksandar Markovic
Both FIFREEZE and FITHAW ioctls accept an integer as their third
argument.
All ioctls in this group (FI* ioctl) are guarded with "#ifdef", so the
guards are used in this implementation too for consistency (however,
many of ioctls in FI* group became old enough that thei
From: Aleksandar Markovic
These FS_IOC32_FLAGS ioctls are identical to
FS_IOC_FLAGS ioctls, but without the anomaly of their
number defined as if their third argument is of type long, while
it is treated internally in kernel as is of type int.
Signed-off-by: Aleksandar Markovic
---
linux-user/
From: Aleksandar Markovic
FDSETEMSGTRESH, FDSETMAXERRS, and FDGETMAXERRS ioctls are commands
for controlling error reporting of a floppy drive.
FDSETEMSGTRESH's third agrument is a pointer to the structure:
struct floppy_max_errors {
unsigned int
abort, /* number of errors to be
From: Aleksandar Markovic
These FS_IOC32_VERSION ioctls are identical to
FS_IOC_VERSION ioctls, but without the anomaly of their
number defined as if their third argument is of type long, while
it is treated internally in kernel as is of type int.
Signed-off-by: Aleksandar Markovic
---
linux-u
From: Aleksandar Markovic
Update x86_64 syscall numbers based on Linux kernel tag v5.5-rc3
(commit 46cf053e).
Signed-off-by: Aleksandar Markovic
---
cc: Paolo Bonzini
cc: Richard Henderson
cc: Eduardo Habkost
---
linux-user/x86_64/syscall_nr.h | 24
1 file changed
From: Aleksandar Markovic
Currently, there is no usage of TARGET_NR_syscall_count for target
xtensa, and there is no obvious indication if there is some planned
usage in future.
---
cc: Max Filippov
---
linux-user/xtensa/syscall_nr.h | 2 --
1 file changed, 2 deletions(-)
diff --git a/linux-
From: Aleksandar Markovic
A very specific thing for these two ioctls is that their code
implies that their third argument is of type 'long', but the
kernel uses that argument as if it is of type 'int'. This anomaly
is recognized also in commit 6080723 (linux-user: Implement
FS_IOC_GETFLAGS and FS
From: Aleksandar Markovic
Update mips syscall numbers based on Linux kernel tag v5.5-rc3
(commit 46cf053e).
Signed-off-by: Aleksandar Markovic
---
linux-user/mips/cpu_loop.c | 78 +-
linux-user/mips/syscall_nr.h | 45
linux
From: Aleksandar Markovic
Update xtensa syscall numbers based on Linux kernel tag v5.5-rc3
(commit 46cf053e).
Signed-off-by: Aleksandar Markovic
---
cc: Max Filippov
---
linux-user/xtensa/syscall_nr.h | 38 --
1 file changed, 36 insertions(+), 2 deletions
From: Aleksandar Markovic
Some constants were defined in terms of host, instead of target,
as they should be.
Some additional trivial changes in this patch were forced by
checkpatch.pl.
Reviewed-by: Max Filippov
Signed-off-by: Aleksandar Markovic
---
linux-user/aarch64/termbits.h| 4 +-
From: Aleksandar Markovic
Update microblaze syscall numbers based on Linux kernel tag v5.5-rc3
(commit 46cf053e).
Signed-off-by: Aleksandar Markovic
---
cc: Edgar E. Iglesias
---
linux-user/microblaze/syscall_nr.h | 45 ++
1 file changed, 45 insertions(+)
From: Aleksandar Markovic
Update m68k syscall numbers based on Linux kernel tag v5.5-rc3
(commit 46cf053e).
Signed-off-by: Aleksandar Markovic
---
cc: Laurent Vivier
---
linux-user/m68k/syscall_nr.h | 50 +++-
1 file changed, 49 insertions(+), 1 delet
From: Aleksandar Markovic
This series is a collection of linux-user patches I recently
accumulated. The summary of patches is as follows:
Patch 1: Fix for some issues in termbits.h files.
Patches 2-6: Updating syscall numbers
Patch 7: A minor xtensa cleanup
Patches 8-13: Adding support for some
If I revert 67113c03423a on top of master, vda is correctly detected.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1856834
Title:
PCI broken in qemu ppc e500 in v2.12.0 and other versions
Status
This is broken by:
commit 67113c03423a23e60915574275aed7d60e9f85e1
Author: Michael Davidsaver
Date: Sun Nov 26 15:59:05 2017 -0600
e500: fix pci host bridge class/type
Correct some confusion wrt. the PCI facing
side of the PCI host bridge (not PCIe root complex).
The ref.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1653577
Title:
Ability to set umask for 9pfs
Status in QEMU:
Incomplete
Bug description:
We
On 10/01/2020 21.02, Wainer dos Santos Moschetta wrote:
> Hi Thomas,
>
> On 12/18/19 4:48 PM, Thomas Huth wrote:
>> On 18/12/2019 18.00, Wainer dos Santos Moschetta wrote:
>>> The test case may need to boot the VM with an accelerator that
>>> isn't actually enabled on the QEMU binary and/or presen
31 matches
Mail list logo
