From: Cornelia Huck
Commit bb15791166c1 ("compat: disable edid on virtio-gpu base
device") tried to disable 'edid' on the virtio-gpu base device.
However, that device is not 'virtio-gpu', but 'virtio-gpu-device'.
Fix it.
Fixes: bb15791166c1 ("compat: disable edid on virtio-gpu base device")
Repo
The following changes since commit e6d567db23219fe9979f16d74e13f27145f07f84:
Merge remote-tracking branch 'remotes/jnsnow/tags/bitmaps-pull-request' into
staging (2020-03-19 15:31:09 +)
are available in the Git repository at:
git://git.kraxel.org/qemu tags/vga-20200320-pu
The specification can be seen here:
https://specifications.freedesktop.org/desktop-entry-spec/desktop-entry-
spec-latest.html#exec-variables
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1868221
Tit
Public bug reported:
According to the www.freedesktop.org .desktop-file specification, all
"Application" desktop files should have an "Exec=" key. The one in qemu
doesn't.
This can be easily verified by running kbuildsycoca4 if KDE4 is present,
but the issue is not DE-dependent.
Which binary exa
четвртак, 19. март 2020., Marc-André Lureau
је написао/ла:
> The following changes since commit f57587c7d47b35b2d9b31def3a74d8
> 1bdb5475d7:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2020-03-17'
> into staging (2020-03-19 10:18:07 +)
>
> are available in the Git reposi
Hi,
> > +uint32_t irq = VIRTIO_IRQ_BASE + index;
> > +hwaddr base = VIRTIO_MMIO_BASE + index * 512;
> > +hwaddr size = 512;
> is it possible to fish these values out from device without poking in its guts
> like using sysbus_get_connected_irq() and make up som
Le 19/03/2020 à 21:45, Peter Maydell a écrit :
> On Thu, 19 Mar 2020 at 09:29, Laurent Vivier wrote:
>>
>> The following changes since commit 373c7068dd610e97f0b551b5a6d0a27cd6da4506:
>>
>> qemu.nsi: Install Sphinx documentation (2020-03-09 16:45:00 +)
>>
>> are available in the Git reposito
On Thu, Mar 19, 2020 at 02:42:18PM +0100, Igor Mammedov wrote:
> On Thu, 19 Mar 2020 09:01:07 +0100
> Gerd Hoffmann wrote:
>
> > Minimal ACPI device for PCI-less machines like microvm.
> it seems that x86 kernel is able to boot on hw-reduced acpi systems
> (but I haven't really tested any distro
On Thu, Mar 19, 2020 at 06:34:40PM +0100, Paolo Bonzini wrote:
> On 19/03/20 14:40, Gerd Hoffmann wrote:
> >> Also, can you confirm that it builds without CONFIG_I440FX and
> >> CONFIG_Q35? You probably need to add "imply ACPI" and possibly some
> >> '#include "config-devices.h"' and '#ifdef CONFI
On Thu, Mar 19, 2020 at 03:41:12AM +0800, Kirti Wankhede wrote:
> DMA mapped pages, including those pinned by mdev vendor drivers, might
> get unpinned and unmapped while migration is active and device is still
> running. For example, in pre-copy phase while guest driver could access
> those pages,
On Thu, Mar 19, 2020 at 04:44:39PM +1000, Nicholas Piggin wrote:
> The new ISA v3.0 slbia variants have not been implemented for TCG,
> which can lead to crashing when a POWER9 machine boots Linux using
> the hash MMU, for example ("disable_radix" kernel command line).
>
> Add them.
>
> Signed-of
On Thu, Mar 19, 2020 at 08:32:44AM -0500, Vincent Fazio wrote:
> From: Vincent Fazio
>
> Previously, the signal handler would be byte swapped if the target and
> host CPU used different endianness. This would cause a SIGSEGV when
> attempting to translate the opcode pointed to by the swapped addr
Priyamvad Acharya writes:
> Thanks Alex, I will check it out.
> Have you look at below issue which I mention in my previous email?
Without seeing the full code changes it's hard to make a determination.
But it looks like you haven't followed the template of defining the
device type.
Also have
On Thu, Mar 19, 2020 at 01:03:26AM -0300, Leonardo Bras wrote:
> When dumping dtb to a file, qemu exits silently before starting the VM.
>
> Add info message so user can easily track why the proccess exits.
> Add error message if dtb dump failed.
>
> Signed-off-by: Leonardo Bras
Reviewed-by: Da
Section markup in definition documentation makes no sense and can
produce invalid Texinfo. Reject.
Signed-off-by: Markus Armbruster
---
docs/devel/qapi-code-gen.txt | 2 ++
scripts/qapi/parser.py | 5 +
tests/qapi-schema/doc-bad-section.err | 1 +
tests/qapi-sc
Lirong Yuan writes:
> On Fri, Mar 6, 2020 at 5:01 PM Lirong Yuan wrote:
>
>> This allows gdb to access the target’s auxiliary vector,
>> which can be helpful for telling system libraries important details
>> about the hardware, operating system, and process.
>>
>> Signed-off-by: Lirong Yuan
>
Our current QAPI doc-comment markup allows section headers (introduced
with a leading '=' or '==') anywhere in a free-form documentation
comment. This works for Texinfo because the generator simply prints a
Texinfo section command at that point in the output stream. For rST
generation, since we'r
PATCH 1 fixes an old defect in the doc comment parser. I figure it'll
simplify the rST generator's job.
PATCH 2 might simplify it further. It's RFC because I'm not sure it
does. Peter, you tell me :)
Markus Armbruster (2):
qapi: Reject section markup in definition documentation
[RFC] qapi
Le 20/03/2020 à 03:25, Chenqun (kuhn) a écrit :
> Gentle ping.
>
> Any other suggestions about this?
I will not take that via the trivial queue as it is not trivial for me.
Could it go via block queue?
Thanks,
Laurent
> Thanks.
>
>> -Original Message-
>> From: Chenqun (kuhn)
>> Sent:
On 19.03.20 21:31, Peter Maydell wrote:
> On Tue, 10 Mar 2020 at 15:09, Christian Borntraeger
> wrote:
>>
>> From: Halil Pasic
>>
>> We expose loadparm as a r/w machine property, but if loadparm is set by
>> the guest via DIAG 308, we don't update the property. Having a
>> disconnect between t
ipi_enable() code would be reusable for other interrupts
than IPI. Let's rename it setup_irq() and pass an interrupt
handler pointer.
Signed-off-by: Eric Auger
---
v4 -> v5:
- s/handler_t/irq_handler_t
- also add irq_handler_fn in lib/arm/asm/processor.h
v2 -> v3:
- do not export setup_irq any
Introduce additional SZ_256, SZ_8K, SZ_16K macros that will
be used by ITS tests.
Signed-off-by: Eric Auger
Reviewed-by: Thomas Huth
---
lib/libcflat.h | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/libcflat.h b/lib/libcflat.h
index ea19f61..7092af2 100644
--- a/lib/libcflat.h
+++ b
PROPBASER, PENDBASE and GICR_CTRL will be used for LPI management.
Signed-off-by: Eric Auger
Reviewed-by: Zenghui Yu
---
v3 -> v4:
- replace some spaces by tabs and added Zenghui's R-b
---
lib/arm/asm/gic-v3.h | 6 ++
1 file changed, 6 insertions(+)
diff --git a/lib/arm/asm/gic-v3.h b/li
This series is a revival of an RFC series sent in Dec 2016 [1].
Given the amount of code and the lack of traction at that time,
I haven't respinned until now. However a recent bug found related
to the ITS migration convinced me that this work may deserve to be
respinned and enhanced.
Tests exercis
Compute the power of 2 order of a size. Use it in
page_memalign. Other users are looming.
Signed-off-by: Eric Auger
---
lib/alloc_page.c | 7 ++-
lib/alloc_page.h | 1 +
2 files changed, 7 insertions(+), 1 deletion(-)
diff --git a/lib/alloc_page.c b/lib/alloc_page.c
index ed23638..7c8461a 1
Introduce an helper functions to register
- a new device, characterized by its device id and the
max number of event IDs that dimension its ITT (Interrupt
Translation Table). The function allocates the ITT.
- a new collection, characterized by its ID and the
target processing engine (PE).
Let's link getchar.o to use puts and getchar from the
tests.
Then allow tests belonging to the migration group to
trigger the migration from the test code by putting
"migrate" into the uart. Then the code can wait for the
migration completion by using getchar().
The __getchar implement is minimal
its_enable_defaults() enable LPIs at redistributor level
and ITS level.
gicv3_enable_defaults must be called before.
Signed-off-by: Eric Auger
Reviewed-by: Zenghui Yu
---
v6 -> v7:
- use for_each_present_cpu in its_enable_defaults
v5 -> v6:
- gicv3_lpi_set/get_config introduced before this pa
Implement main ITS commands. The code is largely inherited from
the ITS driver.
Signed-off-by: Eric Auger
---
v6 -> v7:
- remove #include
v5 -> v6:
- fix 2 printfs
- removed GITS_CMD_MAPVI
v3 -> v4:
- device's itt now is a VGA
- pass verbose to choose whether we shall print the cmd
- use pri
This test maps LPIs (populates the device table, the collection table,
interrupt translation tables, configuration table), migrates and make
sure the translation is correct on the destination.
Signed-off-by: Eric Auger
---
v4 -> v5:
- move stub from header to arm/gic.c
v3 -> v4:
- assert in its
Allocate the LPI configuration and per re-distributor pending table.
Set redistributor's PROPBASER and PENDBASER. The LPIs are enabled
by default in the config table.
Also introduce a helper routine that allows to set the pending
table bit for a given LPI and macros to set/get its configuration.
Detect the presence of an ITS as part of the GICv3 init
routine, initialize its base address and read few registers
the IIDR, the TYPER to store its dimensioning parameters.
Parse the BASER registers. As part of the init sequence we
also init all the requested tables.
This is our first ITS test, b
Triggers LPIs through the INT command.
the test checks the LPI hits the right CPU and triggers
the right LPI intid, ie. the translation is correct.
Updates to the config table also are tested, along with inv
and invall commands.
Signed-off-by: Eric Auger
---
v5 -> v6:
- removed collection-unma
On Thu, Mar 19, 2020 at 04:35:59PM +, Stefan Hajnoczi wrote:
> When external event sources are disabled fdmon-io_uring falls back to
> fdmon-poll. The ->need_wait() callback needs to watch for this so it
> can return true when external event sources are disabled.
>
> It is also necessary to c
Add two new migration tests. One testing the migration of
a topology where collection were unmapped. The second test
checks the migration of the pending table.
Signed-off-by: Eric Auger
---
v6 -> v7:
- test_migrate_unmapped_collection now uses pe0=0. Otherwise,
depending on SMP value it colli
On Fri, 20 Mar 2020 at 08:19, Aleksandar Markovic
wrote:
> This pull request has a very unusual form to me. In its cover letter, it
> appears as if only one
> line of code is changed, while the patch 1/1 strangely suggests that there
> are number of
> underlying patches. I am really puzzled how
On 19.03.20 18:45, Michael S. Tsirkin wrote:
> On Thu, Mar 19, 2020 at 02:54:11PM +0100, David Hildenbrand wrote:
>> Why does the balloon driver not support VIRTIO_F_IOMMU_PLATFORM? It is
>> absolutely not clear to me. The introducing commit mentioned that it
>> "bypasses DMA". I fail to see that.
Thansk, I will check it out.
To make my device I have used following link as reference
https://devkail.wordpress.com/2014/12/16/emulation-of-des-encryption-device-in-qemu/
Also I have shared all the necessary files
in previous mails involved in the development and testing process of device.
Ple
Peter Maydell writes:
> Our current QAPI doc-comment markup allows section headers
> (introduced with a leading '=' or '==') anywhere in any documentation
> comment. This works for texinfo because the texi generator simply
> prints a texinfo heading directive at that point in the output
> stream
Adding an exec field would not be right, because QEMU can't simply be
launched from the desktop without any arguments. There needs to be a
long string of arguments given that are different for every QEMU that is
launched. The only viable way to actually launch QEMU is interactively
from the termina
Remove the global acpi_enabled bool and replace it with an
acpi OnOffAuto machine property.
qemu throws an error now if you use -no-acpi while the machine
type you are using doesn't support acpi in the first place.
Signed-off-by: Gerd Hoffmann
---
include/hw/acpi/acpi.h | 1 -
include/hw/arm
On Fri, Mar 20, 2020 at 07:11:03AM +0100, Aleksandar Markovic wrote:
> Hi,
>
> Given a QEMU executable, is there a way to find out the configure options
> it was built with?
No, you need to get the original build logs.
The binary should contain the full build version (ie the QEMU version
and the
On 3/13/20 9:36 AM, Kevin Wolf wrote:
Peter ran into a 030 hang while testing a pull request. This turned out
to be two bugs in the test suite at once: First was the test failing
because a timeout was apparently too short, second was that the timeout
would actually cause the test to hang instead
On Thu, 19 Mar 2020 at 11:33, Marc-André Lureau
wrote:
>
> The following changes since commit f57587c7d47b35b2d9b31def3a74d81bdb5475d7:
>
> Merge remote-tracking branch 'remotes/armbru/tags/pull-qapi-2020-03-17'
> into staging (2020-03-19 10:18:07 +)
>
> are available in the Git repository
On 3/13/20 9:36 AM, Kevin Wolf wrote:
With a QEMU bug, it can happen that the QEMU process doesn't react to a
'quit' QMP command. If we got an exception during previous QMP
communication (e.g. iotests Timeout expiring), we could also be in an
inconsistent state where after sending 'quit' we immed
On Fri, 20 Mar 2020 at 09:39, Priyamvad Acharya
wrote:
>
> Thansk, I will check it out.
>
> To make my device I have used following link as reference
>
> https://devkail.wordpress.com/2014/12/16/emulation-of-des-encryption-device-in-qemu/
Watch out, because that blog is six years old. Much of QEM
On 3/13/20 9:36 AM, Kevin Wolf wrote:
Waiting for only 1 second proved to be too short on a loaded system,
resulting in false positives when testing pull requests. Increase the
timeout a bit to make this less likely.
Signed-off-by: Kevin Wolf
---
tests/qemu-iotests/iotests.py | 2 +-
1 file
So, is there any up to date blog from where I can get a reference about
device modelling development
On Fri, 20 Mar 2020 at 15:46, Peter Maydell
wrote:
> On Fri, 20 Mar 2020 at 09:39, Priyamvad Acharya
> wrote:
> >
> > Thansk, I will check it out.
> >
> > To make my device I have used following
v3:
* Add new performance results that demonstrate the scalability
* Mention that this is PCI-specific [Cornelia]
v2:
* Let the virtio-DEVICE-pci device select num-queues because the optimal
multi-queue configuration may differ between virtio-pci, virtio-mmio, and
virtio-ccw [Cornelia]
En
Automatically size the number of virtio-scsi-pci, vhost-scsi-pci, and
vhost-user-scsi-pci request virtqueues to match the number of vCPUs.
Other transports continue to default to 1 request virtqueue.
A 1:1 virtqueue:vCPU mapping ensures that completion interrupts are
handled on the same vCPU that
The event and control virtqueues are always present, regardless of the
multi-queue configuration. Define a constant so that virtqueue number
calculations are easier to read.
Signed-off-by: Stefan Hajnoczi
Reviewed-by: Cornelia Huck
---
hw/scsi/vhost-user-scsi.c | 2 +-
hw/scsi/virtio-scs
Automatically size the number of virtio-blk-pci request virtqueues to
match the number of vCPUs. Other transports continue to default to 1
request virtqueue.
A 1:1 virtqueue:vCPU mapping ensures that completion interrupts are
handled on the same vCPU that submitted the request. No IPI is
necessa
On Sat, 14 Mar 2020 16:47:27 +0800
Pan Nengyuan wrote:
> This patch fix memleaks when we call tests/qtest/cpu-plug-test on s390x. The
> leak stack is as follow:
>
> Direct leak of 48 byte(s) in 1 object(s) allocated from:
> #0 0x7fb43c7cd970 in __interceptor_calloc (/lib64/libasan.so.5+0xef
Automatically size the number of request virtqueues to match the number
of vCPUs. This ensures that completion interrupts are handled on the
same vCPU that submitted the request. No IPI is necessary to complete
an I/O request and performance is improved.
Signed-off-by: Stefan Hajnoczi
Reviewed-
commit 4dd6517e369828171290b65e11f6a45aeeed15af:
Merge remote-tracking branch
'remotes/ehabkost/tags/x86-and-machine-pull-request' into staging (2020-03-19
14:22:46 +)
are available in the Git repository at:
https://gitlab.com/philmd/qemu.git tags/target_renesas_rx-20200320
From: Yoshinori Sato
Reviewed-by: Richard Henderson
Signed-off-by: Yoshinori Sato
Signed-off-by: Richard Henderson
[PMD: Use newer QOM style, split cpu-qom.h, restrict access to
extable array, use rx_cpu_tlb_fill() extracted from patch of
Yoshinori Sato 'Convert to CPUClass::tlb_fill', call
The virtio-iommu device attaches itself to a PCI bus, so it makes
no sense to include it unless PCI is supported---and in fact
compilation fails without this change.
Reported-by: Gerd Hoffmann
Signed-off-by: Paolo Bonzini
---
hw/virtio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(
On 20/03/20 09:32, Gerd Hoffmann wrote:
> Hmm, seems we should have that for better regression testing.
> master branch doesn't build with pc+q35+isapc turned off:
>
> LINKx86_64-softmmu/qemu-system-x86_64
> hw/virtio/virtio-iommu.o: In function `virtio_iommu_get_bdf':
> /home/kraxel/project
On 3/20/20 11:03 AM, Daniel P. Berrangé wrote:
On Fri, Mar 20, 2020 at 07:11:03AM +0100, Aleksandar Markovic wrote:
Hi,
Given a QEMU executable, is there a way to find out the configure options
it was built with?
No, you need to get the original build logs.
The binary should contain the full
Hi Paolo
On 3/20/20 11:41 AM, Paolo Bonzini wrote:
> The virtio-iommu device attaches itself to a PCI bus, so it makes
> no sense to include it unless PCI is supported---and in fact
> compilation fails without this change.
with the --- cleanup (?)
Acked-by: Eric Auger
Thanks
Eric
>
> Repor
On Fri, 20 Mar 2020 10:30:39 +
Stefan Hajnoczi wrote:
> Automatically size the number of virtio-scsi-pci, vhost-scsi-pci, and
> vhost-user-scsi-pci request virtqueues to match the number of vCPUs.
> Other transports continue to default to 1 request virtqueue.
>
> A 1:1 virtqueue:vCPU mapping
On 3/20/20 11:01 AM, Gerd Hoffmann wrote:
Remove the global acpi_enabled bool and replace it with an
acpi OnOffAuto machine property.
qemu throws an error now if you use -no-acpi while the machine
type you are using doesn't support acpi in the first place.
Suggested-by: Paolo Bonzini
Signe
On Thu, Mar 19, 2020 at 09:19:24AM -0700, dnbrd...@gmail.com wrote:
> From: danbrodsky
>
> - __COUNTER__ doesn't work with ## concat
> - replaced ## with glue() macro so __COUNTER__ is evaluated
>
> Signed-off-by: danbrodsky
> ---
> include/qemu/lockable.h | 2 +-
> include/qemu/rcu.h | 2
On 20/03/20 11:01, Gerd Hoffmann wrote:
> Remove the global acpi_enabled bool and replace it with an
> acpi OnOffAuto machine property.
>
> qemu throws an error now if you use -no-acpi while the machine
> type you are using doesn't support acpi in the first place.
>
> Signed-off-by: Gerd Hoffmann
On 20/03/20 11:54, Auger Eric wrote:
>> The virtio-iommu device attaches itself to a PCI bus, so it makes
>> no sense to include it unless PCI is supported---and in fact
>> compilation fails without this change.
> with the --- cleanup (?)
Fails if PCI is not included but virtio-iommu is.
Paolo
>
Priyamvad Acharya writes:
> Thansk, I will check it out.
>
> To make my device I have used following link as reference
>
> https://devkail.wordpress.com/2014/12/16/emulation-of-des-encryption-device-in-qemu/
>
> Also I have shared all the necessary files
> in previous mails involved in the deve
On 3/20/20 11:41 AM, Paolo Bonzini wrote:
The virtio-iommu device attaches itself to a PCI bus, so it makes
no sense to include it unless PCI is supported---and in fact
compilation fails without this change.
Reported-by: Gerd Hoffmann
Signed-off-by: Paolo Bonzini
---
hw/virtio/Kconfig | 2 +-
Hi Philippe,
On 3/20/20 12:26 PM, Philippe Mathieu-Daudé wrote:
> On 3/20/20 11:41 AM, Paolo Bonzini wrote:
>> The virtio-iommu device attaches itself to a PCI bus, so it makes
>> no sense to include it unless PCI is supported---and in fact
>> compilation fails without this change.
>>
>> Reported-
On Wed, 18 Mar 2020 23:27:15 +0100
Philippe Mathieu-Daudé wrote:
> Similarly to commit 4f370b1098, test-util-sockets fails in
> restricted non-x86 Travis containers since they apparently
> blacklisted some required system calls there.
Is "they" == "Travis admins"? Can we get them to remove those
On Wed, 18 Mar 2020 23:27:17 +0100
Philippe Mathieu-Daudé wrote:
> Add a job to build QEMU on s390x with TCG disabled, so
> this configuration won't bitrot over time.
>
> This job is quick, running check-unit: Ran for 4 min 48 sec
> https://travis-ci.org/github/philmd/qemu/jobs/663659486
>
> Si
While debugging check-acceptance failures I found an instability in
the mips64el test case. Briefly the test case:
retry.py -n 100 -c -- ./mips64el-softmmu/qemu-system-mips64el \
-display none -vga none -serial mon:stdio \
-machine malta -kernel ./vmlinux-4.7.0-rc1.I6400 \
-cpu I6400
Thanks,
Reviewed-by: Yuval Shaia
On Wed, 18 Mar 2020 at 15:49, Julia Suvorova wrote:
> ring->name is defined as 'char name[MAX_RING_NAME_SZ]'. Replace untruncated
> strncpy with QEMU function.
> This case prevented QEMU from compiling with --enable-sanitizers.
>
> Signed-off-by: Julia Suvorova
On 20/03/20 02:29, Heyi Guo wrote:
>
> On 2020/3/19 22:46, Igor Mammedov wrote:
>> On Wed, 18 Mar 2020 14:48:18 +0800
>> Heyi Guo wrote:
>>
>>> Common VM users sometimes care about CPU speed, so we add two new
>>> options to allow VM vendors to present CPU speed to their users.
>>> Normally these
> -Original Message-
> From: Michael S. Tsirkin [mailto:m...@redhat.com]
> Sent: 19 March 2020 17:51
> To: Shameerali Kolothum Thodi
> Cc: qemu-devel@nongnu.org; qemu-...@nongnu.org;
> eric.au...@redhat.com; imamm...@redhat.com; peter.mayd...@linaro.org;
> shannon.zha...@gmail.com; xiao
On Mon, 16 Mar 2020 at 18:07, Stefan Hajnoczi wrote:
> gcc (GCC) 9.2.1 20190827 (Red Hat 9.2.1-1) with sanitizers enabled
> reports the following error:
>
> CC x86_64-softmmu/hw/rdma/vmw/pvrdma_dev_ring.o
> In file included from /usr/include/string.h:495,
> from include/qe
Note that QEMU sets the NoDisplay=true property to tell desktops not to
display this entry. I don't think KDE should be warning about missing
Exec entry in this case.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launc
Support for VIRTIO_NET_F_RSS and VIRTIO_NET_F_HASH_REPORT
features in QEMU for reference purpose.
Implements Toeplitz hash calculation for incoming
packets according to configuration provided by driver.
Uses calculated hash for decision on receive virtqueue
and/or reports the hash in the virtio hea
Signed-off-by: Yuri Benditovich
---
net/tap.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git a/net/tap.c b/net/tap.c
index 6207f61f84..47de7fdeb6 100644
--- a/net/tap.c
+++ b/net/tap.c
@@ -63,6 +63,14 @@ typedef struct TAPState {
Notifier exit;
} TAPState;
+
Save and restore RSS/hash report configuration.
Signed-off-by: Yuri Benditovich
---
hw/net/virtio-net.c | 37 +
1 file changed, 37 insertions(+)
diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
index a0614ad4e6..7de7587abd 100644
--- a/hw/net/virtio-net
Optionally report RSS feature.
Handle RSS configuration command and keep RSS parameters
in virtio-net device context.
Signed-off-by: Yuri Benditovich
---
hw/net/trace-events| 3 +
hw/net/virtio-net.c| 189 +
include/hw/virtio/virtio-net.h
Signed-off-by: Yuri Benditovich
---
hw/net/virtio-net.c | 65 +
1 file changed, 65 insertions(+)
diff --git a/hw/net/virtio-net.c b/hw/net/virtio-net.c
index 3627bb1717..90b01221e9 100644
--- a/hw/net/virtio-net.c
+++ b/hw/net/virtio-net.c
@@ -71,6 +71
If VIRTIO_NET_F_RSS negotiated and RSS is enabled, process
incoming packets, calculate packet's hash and place the
packet into respective RX virtqueue.
Signed-off-by: Yuri Benditovich
---
hw/net/virtio-net.c| 88 +-
include/hw/virtio/virtio-net.h | 1
Similar to VMSTATE_VARRAY_UINT32_ALLOC, but the size is
16-bit field.
Signed-off-by: Michael S. Tsirkin
Signed-off-by: Yuri Benditovich
---
include/migration/vmstate.h | 10 ++
1 file changed, 10 insertions(+)
diff --git a/include/migration/vmstate.h b/include/migration/vmstate.h
index
Suggest VIRTIO_NET_F_HASH_REPORT if specified in device
parameters.
If the VIRTIO_NET_F_HASH_REPORT is set,
the device extends configuration space. If the feature
is negotiated, the packet layout is extended to
accomodate the hash information. In this case deliver
packet's hash value and report typ
From: Daniel Brodsky
This patch set adds:
- a fix for lock guard macros so they can be used multiple times in
the same function
- replacement of locks with lock guards where appropriate
v2 -> v3:
- added __COUNTER__ fix for additional lock guard macro
- added missing include header in platform.c
From: Daniel Brodsky
- __COUNTER__ doesn't work with ## concat
- replaced ## with glue() macro so __COUNTER__ is evaluated
Fixes: 3284c3ddc4
Signed-off-by: Daniel Brodsky
---
include/qemu/lockable.h | 4 ++--
include/qemu/rcu.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
di
On 20/03/20 00:34, dnbrd...@gmail.com wrote:
> index 682abd8e09..89f8a656a4 100644
> --- a/block/iscsi.c
> +++ b/block/iscsi.c
> @@ -1086,7 +1086,7 @@ static BlockAIOCB *iscsi_aio_ioctl(BlockDriverState *bs,
> acb->task->expxferlen = acb->ioh->dxfer_len;
>
> data.size = 0;
> -qemu_m
From: Daniel Brodsky
- ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
- replaced result with QEMU_LOCK_GUARD if all unlocks at function end
- replaced result with WITH_QEMU_LOCK_GUARD if unlock not at end
Signed-off-by: Daniel Brodsky
---
block/iscsi.c | 11 +++---
bloc
On Thu, 12 Mar 2020 at 16:45, Peter Maydell wrote:
>
> From: Niek Linnenbank
>
> A real Allwinner H3 SoC contains a Boot ROM which is the
> first code that runs right after the SoC is powered on.
> The Boot ROM is responsible for loading user code (e.g. a bootloader)
> from any of the supported e
ilable in the Git repository at:
>
> git://git.kraxel.org/qemu tags/vga-20200320-pull-request
>
> for you to fetch changes up to 02501fc39381c4dabaf6becdd12c2a4754c3847c:
>
> compat: disable edid on correc
On Fri, Mar 20, 2020 at 5:06 AM Paolo Bonzini wrote:
>
> On 20/03/20 00:34, dnbrd...@gmail.com wrote:
> > index 682abd8e09..89f8a656a4 100644
> > --- a/block/iscsi.c
> > +++ b/block/iscsi.c
> > @@ -1086,7 +1086,7 @@ static BlockAIOCB *iscsi_aio_ioctl(BlockDriverState
> > *bs,
> > acb->task->
On Mon, 16 Mar 2020 at 15:30, Marcel Apfelbaum
wrote:
> Hi Yuval,
>
> On 3/7/20 2:56 PM, Yuval Shaia wrote:
> > The function build_host_sge_array uses two sge arrays, one for input and
> > one for output.
> > Since the size of the two arrays is the same, the function can write
> > directly to the
From: Daniel Brodsky
- ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
- replaced result with QEMU_LOCK_GUARD if all unlocks at function end
- replaced result with WITH_QEMU_LOCK_GUARD if unlock not at end
Signed-off-by: Daniel Brodsky
---
block/iscsi.c | 7 ++
block/nf
From: Daniel Brodsky
- __COUNTER__ doesn't work with ## concat
- replaced ## with glue() macro so __COUNTER__ is evaluated
Fixes: 3284c3ddc4
Signed-off-by: Daniel Brodsky
---
include/qemu/lockable.h | 4 ++--
include/qemu/rcu.h | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
di
From: Daniel Brodsky
This patch set adds:
- a fix for lock guard macros so they can be used multiple times in
the same function
- replacement of locks with lock guards where appropriate
v3 -> v4:
- removed unneeded unlocks from areas where lock guards are now used
- dropped change to lock guard
* dnbrd...@gmail.com (dnbrd...@gmail.com) wrote:
> From: Daniel Brodsky
>
> - ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
> - replaced result with QEMU_LOCK_GUARD if all unlocks at function end
> - replaced result with WITH_QEMU_LOCK_GUARD if unlock not at end
>
> Signed-off-by: D
On Fri, Mar 20, 2020 at 5:34 AM Dr. David Alan Gilbert
wrote:
>
> * dnbrd...@gmail.com (dnbrd...@gmail.com) wrote:
> > From: Daniel Brodsky
> >
> > - ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
> > - replaced result with QEMU_LOCK_GUARD if all unlocks at function end
> > - replaced
* Daniel Brodsky (dnbrd...@gmail.com) wrote:
> On Fri, Mar 20, 2020 at 5:34 AM Dr. David Alan Gilbert
> wrote:
> >
> > * dnbrd...@gmail.com (dnbrd...@gmail.com) wrote:
> > > From: Daniel Brodsky
> > >
> > > - ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
> > > - replaced result with
run:
(qemu) info migrate_parameters
announce-initial: 50 ms
...
announce-max: 550 ms
multifd-compression: none
xbzrle-cache-size: 4194304
max-postcopy-bandwidth: 0
tls-authz: '(null)'
The last line seems a bit out of place, fix it.
Signed-off-by: Mao Zhongyi
---
monitor/hmp-cmds.c | 2 +-
1 fi
On Thu, 23 Jan 2020 at 19:41, Dr. David Alan Gilbert (git)
wrote:
>
> From: Stefan Hajnoczi
>
> Do not expose lo_dirp pointers to clients.
>
> Signed-off-by: Stefan Hajnoczi
> Reviewed-by: Philippe Mathieu-Daudé
> Signed-off-by: Dr. David Alan Gilbert
> ---
> tools/virtiofsd/passthrough_ll.c
1 - 100 of 286 matches
Mail list logo
