On Sat, May 9, 2020 at 10:25 AM Jason Wang wrote:
>
>
> On 2020/5/9 上午12:32, Cindy Lu wrote:
> > Introduce a function to set the state to the vhost driver.
> > vDPA need to sync the driver's state to NIC
>
>
> Let's split this patch into two.
>
> 1) introduce vhost_set_state
> 2) make virtio-net u
On Sat, May 9, 2020 at 12:42 AM Eric Blake wrote:
>
> On 5/8/20 11:32 AM, Cindy Lu wrote:
> > From: Tiwei Bie
> >
> > This patch set introduces a new net client type: vhost-vdpa.
> > vhost-vdpa net client will set up a vDPA device which is specified
> > by a "vhostdev" parameter.
> >
> > Co-autho
On Sat, May 9, 2020 at 10:40 AM Jason Wang wrote:
>
>
> On 2020/5/9 上午12:32, Cindy Lu wrote:
> > From: Tiwei Bie
>
>
> If you think you've done a huge refactor on the code, you can change the
> author but need to keep the sob of Tiwei.
>
>
> >
> > This patch set introduces a new net client type:
Probably not, but there may be a workaround. The closest cpu to Octeon
that is supported in QEMU is "MIPS64R2-generic".
Please try using switch -cpu MIPS64R2-generic in your QEMU command line.
Also, I think you should use qemu-mipsn32 rather than qemu-mips or qemu-
mips64.
I don't have much hope
Hi, Aleksandar,
On Fri, May 8, 2020 at 7:23 PM Aleksandar Markovic
wrote:
>
> нед, 3. мај 2020. у 12:14 Huacai Chen је написао/ла:
> >
> > This patch add Loongson-3 Virtual IPI interrupt support in the kernel,
> > because emulate it in QEMU is too expensive for performance.
> >
>
> Huacei, hi!
>
Patchew URL:
https://patchew.org/QEMU/20200508230823.22956-1-wall...@linux.ibm.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200508230823.22956-1-wall...@linux.ibm.com
Subject: [PATCH v1 0/8] s390: Extended-Length SCCB & DI
On Sat, May 9, 2020 at 11:00 AM Jason Wang wrote:
>
>
> On 2020/5/9 上午12:32, Cindy Lu wrote:
> > From: Tiwei Bie
> >
> > Currently we have 2 types of vhost backends in QEMU: vhost kernel and
> > vhost-user. The above patch provides a generic device for vDPA purpose,
> > this vDPA device exposes t
Public bug reported:
On Arch Linux, the recent qemu package update seems to misbehave on some
systems. In my case, my Windows 10 guest runs fine for around 5 minutes
and then start to get really sluggish, even unresponsive. It needs to be
forced off. I could reproduce this on a minimal VM with no
Note that bisecting is difficult due to the nature of the bug (does not
appear before 5 to 10 minutes on my machine).
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877716
Title:
Win10 guest unsuab
** Attachment added: "libvirt/qemu log of a 73fd272 run reproducing the issue"
https://bugs.launchpad.net/qemu/+bug/1877716/+attachment/5368818/+files/win10.log
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpa
** Attachment added: "libvirt description of the machine used to debug"
https://bugs.launchpad.net/qemu/+bug/1877716/+attachment/5368819/+files/win10.xml
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/b
Patchew URL:
https://patchew.org/QEMU/20200508154359.7494-1-richard.hender...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200508154359.7494-1-richard.hender...@linaro.org
Subject: [PATCH v5 00/19] target/arm: sve l
суб, 9. мај 2020. у 12:16 Aleksandar Markovic <
aleksandar.qemu.de...@gmail.com> је написао/ла:
>
>
>
> сре, 6. мај 2020. у 13:26 Alex Bennée је
написао/ла:
> >
> >
> > Aleksandar Markovic writes:
> >
> > Some preliminary thoughts
> >
>
> Alex, many thanks for all your thoughts and hints that
I can also replicate the problem on current master. I can solve it by
building master with --disable-linux-io-uring.
I also tried building Linux 5.4.39 where the issue happens too:
Linux cc 5.4.39qemu #1 SMP PREEMPT Sat May 9 12:11:38 CEST 2020 x86_64 GNU/Linux
I attached the logs of that latest
On Sat, May 9, 2020 at 12:17 PM Aleksandar Markovic
wrote:
> сре, 6. мај 2020. у 13:26 Alex Bennée је написао/ла:
>
> > This is very much driven by how much code generation vs running you see.
> > In most of my personal benchmarks I never really notice code generation
> > because I give my machi
On 5/8/20 5:43 PM, Richard Henderson wrote:
The only caller of cpu_watchpoint_address_matches passes
TARGET_PAGE_SIZE, so the bug is not currently visible.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
exec.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --gi
Typo "virtio-pci" in patch subject.
On 5/8/20 6:32 PM, Cindy Lu wrote:
From: Jason Wang
With version 1, we can detect whether a queue is enabled via
queue_enabled.
Signed-off-by: Jason Wang
---
hw/virtio/virtio-pci.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/hw/vi
On Fri, 8 May 2020 06:50:39 +
"Zhang, Chen" wrote:
> > -Original Message-
> > From: Lukas Straub
> > Sent: Friday, May 8, 2020 2:11 PM
> > To: Zhang, Chen
> > Cc: qemu-devel ; Li Zhijian
> > ; Jason Wang ; Marc-
> > André Lureau ; Paolo Bonzini
> >
> > Subject: Re: [PATCH v4 5/6] n
суб, 9. мај 2020. у 13:37 Laurent Desnogues
је написао/ла:
>
> On Sat, May 9, 2020 at 12:17 PM Aleksandar Markovic
> wrote:
> > сре, 6. мај 2020. у 13:26 Alex Bennée је
> > написао/ла:
> >
> > > This is very much driven by how much code generation vs running you see.
> > > In most of my person
On Sat, May 9, 2020 at 2:38 PM Aleksandar Markovic
wrote:
>
> суб, 9. мај 2020. у 13:37 Laurent Desnogues
> је написао/ла:
> >
> > On Sat, May 9, 2020 at 12:17 PM Aleksandar Markovic
> > wrote:
> > > сре, 6. мај 2020. у 13:26 Alex Bennée је
> > > написао/ла:
> > >
> > > > This is very much dr
суб, 9. мај 2020. у 14:50 Laurent Desnogues
је написао/ла:
>
> On Sat, May 9, 2020 at 2:38 PM Aleksandar Markovic
> wrote:
> >
> > суб, 9. мај 2020. у 13:37 Laurent Desnogues
> > је написао/ла:
> > >
> > > On Sat, May 9, 2020 at 12:17 PM Aleksandar Markovic
> > > wrote:
> > > > сре, 6. мај 202
Restrict init_machine(), setup_post() and has_memory()
to system-mode.
Signed-off-by: Philippe Mathieu-Daudé
---
include/sysemu/accel.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/sysemu/accel.h b/include/sysemu/accel.h
index 47e5788530..e08b8ab8fa 100644
--- a/include/sysemu/a
The code related to PPC Virtual Hypervisor is pointless in user-mode.
Signed-off-by: Philippe Mathieu-Daudé
---
target/ppc/cpu.h| 4 ++--
target/ppc/kvm_ppc.h| 22 +++---
target/ppc/translate_init.inc.c | 4
3 files changed, 17 insertions(+), 13
When TCG is not available, the tcg_allowed variable does not exist.
Signed-off-by: Philippe Mathieu-Daudé
---
include/sysemu/tcg.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/sysemu/tcg.h b/include/sysemu/tcg.h
index 7d116d2e80..d9d3ca8559 100644
--- a/include/sys
The 'hwaddr' type declared in "exec/hwaddr.h" is meant for
system-mode emulation only. Poison it in user-mode code.
Philippe Mathieu-Daudé (11):
plugins: Restrict functions handling hwaddr to system-mode
sysemu/accel: Restrict machine methods to system-mode
sysemu/tcg: Only declare tcg_allow
Restrict qemu_plugin_hwaddr_is_io() and
qemu_plugin_hwaddr_device_offset() to system-mode.
Signed-off-by: Philippe Mathieu-Daudé
---
include/qemu/qemu-plugin.h | 2 ++
plugins/api.c | 17 ++---
2 files changed, 4 insertions(+), 15 deletions(-)
diff --git a/include/qemu
The decode_basedisp*() methods are only used in ioinst.c,
which is only build in system-mode emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
target/s390x/internal.h | 4
1 file changed, 4 insertions(+)
diff --git a/target/s390x/internal.h b/target/s390x/internal.h
index 8c95c734db..c1
As these declarations are restricted to !CONFIG_USER_ONLY in
helper.c, only declare them when system-mode emulation is used.
Signed-off-by: Philippe Mathieu-Daudé
---
target/s390x/internal.h | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/target/s390x/internal.h b
All this code is guarded checking CONFIG_USER_ONLY definition.
Drop the duplicated checks.
Signed-off-by: Philippe Mathieu-Daudé
---
Suspicious ifdef'ry in s390_handle_wait() from commit 83f7f32901c.
---
target/s390x/helper.c | 7 ++-
1 file changed, 2 insertions(+), 5 deletions(-)
diff --g
When HVF is not available, the tcg_allowed variable does not exist.
Signed-off-by: Philippe Mathieu-Daudé
---
include/sysemu/hvf.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/include/sysemu/hvf.h b/include/sysemu/hvf.h
index d211e808e9..fe95743124 100644
--- a/inclu
The "exec/hwaddr.h" header is restricted to system-mode emulation.
Instead, use "exec/cpu-common.h", which is meant for all modes.
Signed-off-by: Philippe Mathieu-Daudé
---
include/disas/disas.h | 2 +-
include/hw/core/cpu.h | 2 +-
include/sysemu/accel.h | 2 +-
3 files changed, 3 insertions(
Restrict the following handlers to system-mode:
- do_unaligned_access
- do_transaction_failed
- get_phys_page_debug
- get_phys_page_attrs_debug
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h | 8 +---
target/alpha/cpu.h | 4 +++-
target/arm/cpu.h
The 'hwaddr' type is restricted to system-mode.
Declare it poisoned on user-mode emulation.
Signed-off-by: Philippe Mathieu-Daudé
---
Checkpatch complains:
WARNING: architecture specific defines should be avoided
#10: FILE: include/exec/cpu-common.h:7:
+#ifdef __GNUC__
---
include/exec/cpu-c
On Thu, 7 May 2020 18:22:35 +0200
Philippe Mathieu-Daudé wrote:
> The BootLinuxAarch64.test_virt_tcg is reported to take >7min to run.
> Add a possibility to users to skip this particular test, by setting
> the AVOCADO_SKIP_SLOW_TESTS environment variable:
>
> $ AVOCADO_SKIP_SLOW_TESTS=please
Since the report is about overlayfs being involved, could you please try if
the following patch makes a difference?
https://github.com/gkurz/qemu/commit/f7f5a1b01307af1c7b6c94672f2ce75c36f10565
It's not yet on master, but will be soon.
--
You received this bug notification because you are a me
Hi,
As suggested on #qemu-devel IRC channel, I am including Gerd and
Michael to point in the right direction how to move forward with Qemu
support for Virtio Video V4L2 driver
posted in [1].
[1]: https://patchwork.linuxtv.org/patch/61717/
Regards,
Saket Sinha
On Sat, May 9, 2020 at 1:09 AM Sake
Hi,
As suggested on #qemu-devel IRC channel, I am including virtio-dev, Gerd and
Michael to point in the right direction how to move forward with Qemu
support for Virtio Video V4L2 driver
posted in [1].
[1]: https://patchwork.linuxtv.org/patch/61717/
Regards,
Saket Sinha
On Sat, May 9, 2020 at
Looks like being introduced by this change:
https://patchwork.kernel.org/patch/11319993/
More specifically this one exactly:
-if (buf_size < size) {
+if (buf_size < P9_IOHDRSZ) {
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to Q
On 5/9/20 3:09 PM, Philippe Mathieu-Daudé wrote:
Restrict the following handlers to system-mode:
- do_unaligned_access
- do_transaction_failed
- get_phys_page_debug
- get_phys_page_attrs_debug
Signed-off-by: Philippe Mathieu-Daudé
---
include/hw/core/cpu.h | 8 +---
target/alp
Laurent Desnogues writes:
> On Sat, May 9, 2020 at 2:38 PM Aleksandar Markovic
> wrote:
>>
>> суб, 9. мај 2020. у 13:37 Laurent Desnogues
>> је написао/ла:
>> >
>> > On Sat, May 9, 2020 at 12:17 PM Aleksandar Markovic
>> > wrote:
>> > > сре, 6. мај 2020. у 13:26 Alex Bennée је
>> > > напи
The following patch should fix this bug for the kvm backend (not for the
XEN backend yet).
Please let me know if it fixes this bug for you.
** Patch added: "bug1877688_kvm_fix.patch"
https://bugs.launchpad.net/qemu/+bug/1877688/+attachment/5369130/+files/bug1877688_kvm_fix.patch
** Changed i
Thanks, it works.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1877688
Title:
9p virtfs device reports error when opening certain files
Status in QEMU:
In Progress
Bug description:
Reading c
On Sat, May 9, 2020 at 6:08 PM Philippe Mathieu-Daudé wrote:
> On 5/9/20 3:09 PM, Philippe Mathieu-Daudé wrote:
> > Restrict the following handlers to system-mode:
> > - do_unaligned_access
> > - do_transaction_failed
> > - get_phys_page_debug
> > - get_phys_page_attrs_debug
> >
> > Signed-off-by:
Public bug reported:
This is not a bug so much as a feature request.
It would be great if there was a pure-software emulation of the x2APIC
on x86_64, so that it could be used on systems that don't support such
providing a thing on via a host-based solution (e.g., KVM etc). KVM
provides this, but
Il sab 9 mag 2020, 22:01 Philippe Mathieu-Daudé ha
scritto:
> > I forgot once Peter Maydell told me we can't do that for some reason I
> > don't remember.
> >
> > At least this changes the sizeof(CPUClass), so we get:
> >
> > qom/object.c:315:type_initialize: assertion failed: (parent->class_size
Public bug reported:
Hello, I've been recently working on my own little branch of QEMU
implementing the drm IOCTLs, when I discovered that glxgears seems to
crash in GLXSwapBuffers(); with a SIGILL. I investigated this for about
2 weeks, manually trying to trace the call stack, only to find that w
On Mon, Apr 20, 2020 at 13:04:51 +0300, Nikolay Igotti wrote:
> In linux-user multithreaded scenarious CPU could be inited many times with
> the same id,
> so avoid assertions on already present hashtable entry.
>
> Signed-off-by: Nikolay Igotti
> ---
> plugins/core.c | 5 +
> 1 file changed
You can advance 'parts' to track the current path fragment.
The 'index' parameter is unneeded.
Signed-off-by: Masahiro Yamada
---
qom/object.c | 17 -
1 file changed, 8 insertions(+), 9 deletions(-)
diff --git a/qom/object.c b/qom/object.c
index aa8a3f24e6..a3ee968b12 100644
--
CET feature SHSTK and IBT are enumerated via CPUID(EAX=0x7,0):ECX[bit 7]
and EDX[bit 20] respectively. Two CET bits (bit 11 and 12) are defined in
MSR_IA32_XSS to support XSAVES/XRSTORS. CPUID(EAX=0xd, 1):ECX[bit 11] and
ECX[bit 12] correspond to CET states in user and supervisor mode respectively.
Currently XSAVES dependent features are not supported in CPUID enumeration,
update CPUID(0xD,n>=1) to enable it.
CET XSAVES related enumeration includes:
CPUID(0xD,1):ECX[bit 11]: user mode CET state, controls bit 11 in XSS.
CPUID(0xD,1):ECX[bit 12]: supervisor mode CET state, controls bit 12 in X
Control-flow Enforcement Technology (CET) provides protection against
return/jump-oriented programming (ROP/JOP). It includes two
sub-features: Shadow Stack(SHSTK) and Indirect Branch Tracking(IBT).
This patchset is to enable CET related CPUID report, XSAVES/XRSTORS
support and MSR access etc. for
CET SHSTK/IBT MSRs can be saved/restored with XSAVES/XRSTORS, but
currently the related feature words are not supported, so add the
new entries. XSAVES/RSTORS always use compacted storage format, which
means the supervisor states' offsets are always 0, ignore them while
calculating stardard format
Added interface for CET MSR_IA32_{U,S}_CET, MSR_IA32_PL{0,1,2,3}_SSP,
MSR_IA32_INTR_SSP_TBL and MSR_KVM_GUEST_SSP save/restore. Check if
corresponding CET features are available before access the MSRs.
Signed-off-by: Yang Weijiang
---
target/i386/cpu.h | 18 +
target/i386/kvm.c | 7
Hi Ubuntu / KVM Maintainers,
I have now done additional diagnostics on this bug and it appears to be
triggered in nested virtualization case when apic virtualisation is
available in Layer 0 HW and then passed forward to Layer 1 VM via
Libvirt: .
Testing found that in case where Layer 1 FreeBSD h
Good idea.
The ESCC device looks like it's written as a sysbus device. I think the
Ultra 5 has no devices on the root sabre bus. The serial controller is
behind the ebus (essentially isa). I'm guessing I would need to write a
wrapper device around the memory io functions so that it can be used
und
add options documents changes for -chardev
Signed-off-by: xiaoqiang zhao
---
qemu-options.hx | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/qemu-options.hx b/qemu-options.hx
index 292d4e7c0c..ce73014f8e 100644
--- a/qemu-options.hx
+++ b/qemu-options.hx
@@ -2930,7 +
add cases to test tight and non-tight for abstract address type
Signed-off-by: xiaoqiang zhao
---
tests/test-util-sockets.c | 83 +++
1 file changed, 83 insertions(+)
diff --git a/tests/test-util-sockets.c b/tests/test-util-sockets.c
index 5fd947c7bf..8042fb9
unix_listen/connect_saddr now support abstract address types
two aditional BOOL switches are introduced:
tight: whether to set @addrlen to the minimal string length,
or the maximum sun_path length. default is TRUE
abstract: whether we use abstract address. default is FALSE
cli example:
-mo
By default qemu does not support abstract UNIX domain
socket address. Add this ability to make qemu handy
when abstract address is needed.
Changes since v2:
* reorganize code to cover both connect and listen
* qapi related changes
* add test cases and update qemu-options documents
Xiaoqiang Zhao
59 matches
Mail list logo
