Test 030 is still occasionally failing in the CI ... so for the
time being, let's disable it in the "auto" group. We can add it
back once it got more stable.
Signed-off-by: Thomas Huth
---
I just saw the problem here:
https://cirrus-ci.com/task/5449330930745344?command=main#L6482
and Peter
Ping.
>
> The ivshmem me now mapped to vhost memory regions, and it reduces
> the number of available memslots of vhost backend, which may
> causes vhost backend memory slots limit check failure in
> vhost dev init.
>
> Since ivshmem_bar2 not normal RAM in Guest, and it shouldn't
> have vhost
On 2020/9/4 上午12:14, Eugenio Pérez wrote:
Device IOTLB invalidations can unmap arbitrary ranges, eiter outside of
the memory region or even [0, ~0ULL] for all the space. The assertion
could be hit by a guest, and rhel7 guest effectively hit it.
Signed-off-by: Eugenio Pérez
Reviewed-by: Peter
On Fri, Sep 4, 2020 at 8:18 AM Paolo Bonzini wrote:
> test "$vhost_net_user" = "" && vhost_net_user=$vhost_user
>> if test "$vhost_net_user" = "yes" && test "$vhost_user" = "no"; then
>> - error_exit "--enable-vhost-net-user requires --enable-vhost-user"
>> + error_exit "--enable-vhost-net
From: Daniel Henrique Barboza
The next step to centralize all NUMA/associativity handling in
the spapr machine is to create a 'one stop place' for all
things ibm,associativity.
This patch introduces numa_assoc_array, a 2 dimensional array
that will store all ibm,associativity arrays of all NUMA
From: Thiago Jung Bauermann
We rely on cpu_common_reset() to set cs->halted to 0, it's redundant to do
it in main_cpu_reset().
Signed-off-by: Thiago Jung Bauermann
Message-Id: <20200826055535.951207-7-bauer...@linux.ibm.com>
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: David Gibson
---
From: Daniel Henrique Barboza
The NVLink2 GPUs works like a regular NUMA node with its
own associativity values, regardless of user input.
This can be handled inside spapr_numa_associativity_init(),
initializing NVGPU_MAX_NUM associativity arrays that can
be used by the GPUs.
Signed-off-by:
From: Daniel Henrique Barboza
This function is only used inside spapr_nvdimm.c.
Signed-off-by: Daniel Henrique Barboza
Message-Id: <20200901125645.118026-3-danielhb...@gmail.com>
Signed-off-by: David Gibson
---
hw/ppc/spapr_nvdimm.c | 22 +++---
From: Thiago Jung Bauermann
Instead of setting CPUState::halted to 1 in secondary_cpu_reset(), use the
start-powered-off property which makes cpu_common_reset() initialize it
to 1 in common code.
Now secondary_cpu_reset() becomes equivalent to main_cpu_reset() so rename
the function to
From: Daniel Henrique Barboza
Vcpus have an additional paramenter to be appended, vcpu_id. This
also changes the size of the of property itself, which is being
represented in index 0 of numa_assoc_array[cpu->node_id],
and defaults to MAX_DISTANCE_REF_POINTS for all cases but
vcpus.
All this
Hi,I found some problems, but I don't know if how to solve it better(I'm
not really familiar with the source code).
When I use ioctl() and use a structure like this:
struct drm_mode_card_res {
__u64 fb_id_ptr;
__u64 crtc_id_ptr;
__u64 connector_id_ptr;
__u64
From: Philippe Mathieu-Daudé
Replace the magic '4' by ARRAY_SIZE(s->irq) which is more explicit.
Signed-off-by: Philippe Mathieu-Daudé
Message-Id: <20200901104043.91383-4-f4...@amsat.org>
Reviewed-by: Richard Henderson
Reviewed-by: Cédric Le Goater
Signed-off-by: David Gibson
---
From: Thiago Jung Bauermann
There are other platforms which also have CPUs that start powered off, so
generalize the start-powered-off property so that it can be used by them.
Note that ARMv7MState also has a property of the same name but this patch
doesn't change it because that class isn't a
From: Daniel Henrique Barboza
In a similar fashion as the previous patch, let's move the
handling of ibm,associativity-lookup-arrays from spapr.c to
spapr_numa.c. A spapr_numa_write_assoc_lookup_arrays() helper was
created, and spapr_dt_dynamic_reconfiguration_memory() can now
use it to
From: Daniel Henrique Barboza
The NVDIMM support for pSeries was introduced in 5.1, but it
didn't contemplate the 'nvdimm' machine option that other
archs uses. For every other arch, if no '-machine nvdimm(=on)'
is present, it is assumed that the NVDIMM support is disabled.
The user must
From: Philippe Mathieu-Daudé
We call pci_register_root_bus() to register 4 IRQs with the
ppc4xx_pci_set_irq() handler. As it can only be called with
values in the [0-4[ range, replace the pointless warning by
an assert().
Signed-off-by: Philippe Mathieu-Daudé
Message-Id:
From: Thiago Jung Bauermann
Instead of setting CPUState::halted to 1 in s390_cpu_initfn(), use the
start-powered-off property which makes cpu_common_reset() initialize it
to 1 in common code.
Note that this changes behavior by setting cs->halted to 1 on reset, which
didn't happen before.
From: Cédric Le Goater
The sPAPR machine has four different IRQ backends, each implementing
the XICS or XIVE interrupt mode or both in the case of the 'dual'
backend.
If a machine is started in P8 compat mode, QEMU should necessarily
support the XICS interrupt mode and in that case, the
From: Thiago Jung Bauermann
This change is in a separate patch because it's not so obvious that it
won't cause a regression.
Suggested-by: Eduardo Habkost
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: David Gibson
Reviewed-by: Greg Kurz
Signed-off-by: Thiago Jung Bauermann
Message-Id:
From: Daniel Henrique Barboza
We do not implement hotplug in the vscsi bus, but we forgot to
tell qdev about it. The result is that users are able to hotplug
devices in the vscsi bus, the devices appear in qdev, but they
aren't usable by the guest OS unless the user reboots it first.
Setting
From: Thiago Jung Bauermann
Instead of setting CPUState::halted to 1 in main_cpu_reset(), use the
start-powered-off property which makes cpu_common_reset() initialize it
to 1 in common code.
Also change creation of CPU object from cpu_create() to object_new() and
qdev_realize_and_unref()
From: Daniel Henrique Barboza
NVDIMM has different contraints and conditions than the regular
DIMM and we'll need to add at least one more.
Instead of relying on 'if (nvdimm)' conditionals in the body of
spapr_memory_pre_plug(), use the existing spapr_nvdimm_validate_opts()
and put all NVDIMM
From: Daniel Henrique Barboza
We're going to make changes in how spapr handles all
ibm,associativity* related properties to enhance our current NUMA
support.
At this moment we have associativity code scattered all around
spapr_* files, with hardcoded values and array sizes. This
makes it harder
From: Cédric Le Goater
It was missing the instance_size field.
Cc: Eduardo Habkost
Signed-off-by: Cédric Le Goater
Message-Id: <20200822083920.2668930-1-...@kaod.org>
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: David Gibson
---
hw/ppc/pnv_lpc.c | 3 +--
1 file changed, 1
From: Thiago Jung Bauermann
PowerPC sPAPR CPUs start in the halted state, and spapr_reset_vcpu()
attempts to implement this by setting CPUState::halted to 1. But that's too
late for the case of hotplugged CPUs in a machine configure with 2 or more
threads per core.
By then, other parts of QEMU
From: Thiago Jung Bauermann
Instead of setting CPUState::halted to 1 in ppce500_cpu_reset_sec(), use
the start-powered-off property which makes cpu_common_reset() initialize it
to 1 in common code.
Also change creation of CPU object from cpu_create() to object_new() and
qdev_realize_and_unref()
From: Cédric Le Goater
The vCPU IPIs are now allocated in kvmppc_xive_cpu_connect() when the
vCPU connects to the KVM device and not when all the sources are reset
in kvmppc_xive_source_reset()
This requires extra care for hotplug vCPUs and VM restore.
Signed-off-by: Cédric Le Goater
spapr_drc.h includes typechecker macro boilerplate for the many different
DRC subclasses. However, most of these types don't actually have different
data in their class and/or instance, making these unneeded, unused, and in
fact a bad idea. Remove them.
Signed-off-by: David Gibson
Reviewed-by:
From: Cédric Le Goater
When QEMU switches to the XIVE interrupt mode, it creates all the
guest interrupts at the level of the KVM device. These interrupts are
backed by real HW interrupts from the IPI interrupt pool of the XIVE
controller.
Currently, this is done from the QEMU main thread,
From: Daniel Henrique Barboza
Since we're using the string just once, just use g_autofree and
avoid leaking it without calling g_free().
Signed-off-by: Daniel Henrique Barboza
Message-Id: <20200825215749.213536-2-danielhb...@gmail.com>
Signed-off-by: David Gibson
---
hw/ppc/spapr_nvdimm.c |
The TypeInfo incorrectly just lets the class size be inherited. It won't
actually break things, since the class is abstract, but we should get it
right.
Signed-off-by: David Gibson
Reviewed-by: Cédric Le Goater
Reviewed-by: Philippe Mathieu-Daudé
---
hw/input/adb.c | 1 +
1 file changed, 1
From: Cédric Le Goater
We will use to check if a vCPU IPI has been created.
Signed-off-by: Cédric Le Goater
Message-Id: <20200820134547.2355743-2-...@kaod.org>
Signed-off-by: David Gibson
---
hw/intc/spapr_xive_kvm.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
From: Cédric Le Goater
This is doing an extra loop but should be equivalent.
It also differentiate the reset of the sources from the restore of the
sources configuration. This will help in allocating the vCPU IPIs
independently.
Signed-off-by: Cédric Le Goater
Message-Id:
The following changes since commit 67a7bfe560a1bba59efab085cb3430f45176d382:
Merge remote-tracking branch
'remotes/huth-gitlab/tags/pull-request-2020-09-03' into staging (2020-09-03
16:58:25 +0100)
are available in the Git repository at:
git://github.com/dgibson/qemu.git
From: Cédric Le Goater
The OPAL test suite runs a read-erase-write test on the PNOR :
https://github.com/open-power/op-test/blob/master/testcases/OpTestPNOR.py
which revealed that the IPMI HIOMAP handlers didn't support
HIOMAP_C_ERASE. Implement the sector erase command by writing 0xFF in
From: Cédric Le Goater
On POWER9, the KVM XIVE device uses priority 7 for the escalation
interrupts. On POWER10, the host can use a reduced set of priorities
and KVM will configure the escalation priority to a lower number. In
any case, the guest is allowed to use priorities in a single range :
On 2020/9/4 上午3:46, Edgar E. Iglesias wrote:
On Thu, Sep 03, 2020 at 07:53:33PM +0200, Paolo Bonzini wrote:
On 03/09/20 17:50, Edgar E. Iglesias wrote:
Hmm, I guess it would make sense to have a configurable option in KVM
to isolate passthrough devices so they only can DMA to guest RAM...
On 2020/9/3 下午7:19, Peter Maydell wrote:
On Thu, 3 Sep 2020 at 12:11, Li Qiang wrote:
Peter Maydell 于2020年9月3日周四 下午6:53写道：
On Thu, 3 Sep 2020 at 04:55, Jason Wang wrote:
I think we still need to seek a way to address this issue completely.
How about adding a flag in MemoryRegionOps and
sg devices have different major/minor than their corresponding
block devices. Using sysfs to get max segments never really worked
for them.
Fortunately the sg driver provides an ioctl to get sg_tablesize,
which is apparently equivalent to max segments.
Signed-off-by: Tom Yan
---
We can and should get max transfer length and max segments for all host
devices / cdroms (on Linux).
Also use MIN_NON_ZERO instead when we clamp max transfer length against
max segments.
Signed-off-by: Tom Yan
---
v2: fix get_max_transfer_length for non-sg devices; also add/fix
sg devices have different major/minor than their corresponding
block devices. Using sysfs to get max segments never really worked
for them.
Fortunately the sg driver provides an ioctl to get sg_tablesize,
which is apparently equivalent to max segments.
Signed-off-by: Tom Yan
---
We can and should get max transfer length and max segments for all host
devices / cdroms (on Linux).
Also use MIN_NON_ZERO instead when we clamp max transfer length against
max segments.
Signed-off-by: Tom Yan
---
v2: fix get_max_transfer_length for non-sg devices; also add/fix
sg devices have different major/minor than their corresponding
block devices. Using sysfs to get max segments never really worked
for them.
Fortunately the sg driver provides an ioctl to get sg_tablesize,
which is apparently equivalent to max segments.
Signed-off-by: Tom Yan
---
We can and should get max transfer length and max segments for all host
devices / cdroms (on Linux).
Also use MIN_NON_ZERO instead when we clamp max transfer length against
max segments.
Signed-off-by: Tom Yan
---
v2: fix get_max_transfer_length for non-sg devices; also add/fix
The current implementation of h_home_node_associativity hard codes
the values of associativity domains of the vcpus. Let's make
it consider the values already initialized in spapr->numa_assoc_array,
via the spapr_numa_get_vcpu_assoc() helper.
We want to set it and forget it, and for that we also
The work to be done in h_home_node_associativity() intersects
with what is already done in spapr_numa_fixup_cpu_dt(). This
patch creates a new helper, spapr_numa_get_vcpu_assoc(), to
be used for both spapr_numa_fixup_cpu_dt() and
h_home_node_associativity().
While we're at it, use memcpy()
Kindly ping.
On 2020/8/26 18:15, AlexChen wrote:
> From: AlexChen
>
> The 'kdgb' is allocating memory in get_kdbg(), but it is not freed
> in both fill_header() and fill_context() failed branches, fix it.
>
> Signed-off-by: AlexChen
> ---
> contrib/elf2dmp/main.c | 4 ++--
> 1 file changed,
The implementation of this hypercall will be modified to use
spapr->numa_assoc_arrays input. Moving it to spapr_numa.c makes
make more sense.
Signed-off-by: Daniel Henrique Barboza
---
hw/ppc/spapr_hcall.c | 40 ---
hw/ppc/spapr_numa.c | 45
Hi,
Another spin for this rework of the existing NUMA support
for pSeries, prior to incoming changes in how we calculate
NUMA distance in the pseries machine. Changes here were
made based on David Gibson's review of v3.
This patches were rebased using David's ppc-for-5.2 tree.
changes from v3:
sg devices have different major/minor than their corresponding
block devices. Using sysfs to get max segments never really worked
for them.
Fortunately the sg driver provides an ioctl to get sg_tablesize,
which is apparently equivalent to max segments.
Signed-off-by: Tom Yan
---
We can and should get max transfer length and max segments for all host
devices / cdroms (on Linux).
Also use MIN_NON_ZERO instead when we clamp max transfer length against
max segments.
Signed-off-by: Tom Yan
---
v2: fix get_max_transfer_length for non-sg devices; also add/fix
On Wed, Jul 29, 2020 at 11:16:29AM +0100, Stefan Hajnoczi wrote:
> On Wed, Jul 08, 2020 at 10:46:57PM -0400, Cleber Rosa wrote:
>
> Awesome, thanks for creating this stuff! Minor suggestions:
>
> > diff --git a/docs/devel/testing.rst b/docs/devel/testing.rst
> > index c1ff24370b..f8dab788ea
On 9/3/20 8:23 PM, David Gibson wrote:
On Thu, Sep 03, 2020 at 07:06:34PM -0300, Daniel Henrique Barboza wrote:
Vcpus have an additional paramenter to be appended, vcpu_id. This
also changes the size of the of property itself, which is being
represented in index 0 of
>
> test "$vhost_net_user" = "" && vhost_net_user=$vhost_user
> if test "$vhost_net_user" = "yes" && test "$vhost_user" = "no"; then
> - error_exit "--enable-vhost-net-user requires --enable-vhost-user"
> + error_exit "--enable-vhost-net requires --enable-vhost-user"
> fi
>
This change seems
On Thu, Jul 09, 2020 at 01:28:27PM +0200, Andrea Bolognani wrote:
> On Thu, 2020-07-09 at 11:30 +0100, Daniel P. Berrangé wrote:
> > On Wed, Jul 08, 2020 at 10:46:57PM -0400, Cleber Rosa wrote:
> > > +- name: Installation of basic packages to build QEMU
> > > + hosts: all
> > > + vars_files:
> >
On Thu, Jul 09, 2020 at 11:30:29AM +0100, Daniel P. Berrangé wrote:
> On Wed, Jul 08, 2020 at 10:46:57PM -0400, Cleber Rosa wrote:
> > This is a mapping of Peter's "remake-merge-builds" and
> > "pull-buildtest" scripts, gone through some updates, adding some build
> > option and removing others.
>
Oops I forgot max_transfer needs to be in bytes (and BLKSECTGET in sg
has always been implemented wrongly). Will send a new version.
On Fri, 4 Sep 2020 at 06:37, Tom Yan wrote:
>
> sg_get_max_transfer_length() and sg_get_max_segments() have nothing
> to do with the sg driver or SG_IO at all.
On 9/2/20 6:42 PM, Eduardo Habkost wrote:
Make the type checking macro name consistent with the TYPE_*
constant.
Signed-off-by: Eduardo Habkost
Reviewed-by: Stefan Berger
---
Cc: Stefan Berger
Cc: qemu-devel@nongnu.org
---
hw/tpm/tpm_spapr.c | 14 +++---
1 file changed, 7
On 9/2/20 6:42 PM, Eduardo Habkost wrote:
Make the type checking macro name consistent with the TYPE_*
constant.
Signed-off-by: Eduardo Habkost
Reviewed-by: Stefan Berger
---
Cc: Stefan Berger
Cc: qemu-devel@nongnu.org
---
hw/tpm/tpm_crb.c | 14 +++---
1 file changed, 7
On Thu, Sep 03, 2020 at 07:06:37PM -0300, Daniel Henrique Barboza wrote:
> The implementation of this hypercall will be modified to use
> spapr->numa_assoc_arrays input. Moving it to spapr_numa.c makes
> make more sense.
>
> Signed-off-by: Daniel Henrique Barboza
> ---
> hw/ppc/spapr_hcall.c
On Thu, Sep 03, 2020 at 07:06:39PM -0300, Daniel Henrique Barboza wrote:
> The current implementation of h_home_node_associativity hard codes
> the values of associativity domains of the vcpus. Let's make
> it consider the values already initialized in spapr->numa_assoc_array,
> via the
On Thu, Sep 03, 2020 at 07:06:34PM -0300, Daniel Henrique Barboza wrote:
> Vcpus have an additional paramenter to be appended, vcpu_id. This
> also changes the size of the of property itself, which is being
> represented in index 0 of numa_assoc_array[cpu->node_id],
> and defaults to
On Thu, Sep 03, 2020 at 07:06:32PM -0300, Daniel Henrique Barboza wrote:
> Hi,
>
> This spin attempts to cover all suggestions and concerns pointed
> out by David Gibson in the v2 review.
>
> The patches were rebased with David's ppc-for-5.2 at 615ae3763144.
> They can also be cloned from
>
On Thu, Sep 03, 2020 at 07:06:38PM -0300, Daniel Henrique Barboza wrote:
> The work to be done in h_home_node_associativity() intersects
> with what is already done in spapr_numa_fixup_cpu_dt(). This
> patch creates a new helper, spapr_numa_get_vcpu_assoc(), to
> be used for both
On 9/3/20 2:19 PM, 罗勇刚(Yonggang Luo) wrote:
> No, really, as I asked before: what symbol is present in tcg-op-gvec.c.obj
> without this patch?
>
> The tcg-op-gvec.c.obj are missing now, maybe skip this patch first?
Yes, please.
> Anyway have same name with function and macro is not
On Thu, Jul 09, 2020 at 12:07:32PM +0200, Philippe Mathieu-Daudé wrote:
> On 7/9/20 4:46 AM, Cleber Rosa wrote:
> > This is a mapping of Peter's "remake-merge-builds" and
> > "pull-buildtest" scripts, gone through some updates, adding some build
> > option and removing others.
> >
> > The jobs
Host CPU : Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Host Memory : 15.49 GB
Start Time (UTC) : 2020-09-03 22:30:01
End Time (UTC) : 2020-09-03 23:02:32
Execution Time : 0:32:30.542730
Status : SUCCESS
Note:
Changes denoted by '-' are less than 0.01%.
On Thu, Sep 3, 2020 at 10:33 PM Thomas Huth wrote:
> On 03/09/2020 11.18, 罗勇刚(Yonggang Luo) wrote:
> [...]
> > TESTcheck-unit: tests/test-replication.exe
> > **
> > ERROR:C:/work/xemu/qemu/tests/test-replication.c:136:make_temp:
> > assertion failed: (fd >= 0)
> > ERROR
sg_get_max_transfer_length() and sg_get_max_segments() have nothing
to do with the sg driver or SG_IO at all. They can be and should be
used on all host devices / cdroms (on Linux).
Also use MIN_NON_ZERO instead when we clamp max_sectors against
max_segments.
Signed-off-by: Tom Yan
---
The NVLink2 GPUs works like a regular NUMA node with its
own associativity values, regardless of user input.
This can be handled inside spapr_numa_associativity_init(),
initializing NVGPU_MAX_NUM associativity arrays that can
be used by the GPUs.
Signed-off-by: Daniel Henrique Barboza
---
In a similar fashion as the previous patch, let's move the
handling of ibm,associativity-lookup-arrays from spapr.c to
spapr_numa.c. A spapr_numa_write_assoc_lookup_arrays() helper was
created, and spapr_dt_dynamic_reconfiguration_memory() can now
use it to advertise the lookup-arrays.
The original CAN_PCI config option enables multiple SJA1000 PCI boards
emulation build. These boards bridge SJA1000 into I/O or memory
address space of the host CPU and depend on SJA1000 emulation.
Signed-off-by: Pavel Pisa
---
hw/net/Kconfig | 7 +++
1 file changed, 3 insertions(+), 4
From: Jan Charvat
Definitions of registers and CAN FD frame message box of CTU CAN FD
IP core are generated the specification in CACTUS/IP-XACT format.
CTU CAN FD IP core repository
https://gitlab.fel.cvut.cz/canbus/ctucanfd_ip_core
The location of the CTU CAN IP core specification within
Signed-off-by: Yonggang Luo
---
tests/test-replication.c | 17 +
1 file changed, 13 insertions(+), 4 deletions(-)
diff --git a/tests/test-replication.c b/tests/test-replication.c
index 9ab3666a90..d0e06f8d77 100644
--- a/tests/test-replication.c
+++ b/tests/test-replication.c
@@
The current implementation of h_home_node_associativity hard codes
the values of associativity domains of the vcpus. Let's make
it consider the values already initialized in spapr->numa_assoc_array,
via the spapr_numa_get_vcpu_assoc() helper.
We want to set it and forget it, and for that we also
On 03/09/20 15:18, Philippe Mathieu-Daudé wrote:
> As of this patch, all the non-PCI, but I plan to add a similar
> check for USB on top of this series.
Do you mean for memory-mapped USB host controllers?
>> I'm worried that there are cases of MMIO reads that would be broken.
>> They are
The work to be done in h_home_node_associativity() intersects
with what is already done in spapr_numa_fixup_cpu_dt(). This
patch creates a new helper, spapr_numa_get_vcpu_assoc(), to
be used for both spapr_numa_fixup_cpu_dt() and
h_home_node_associativity().
Signed-off-by: Daniel Henrique Barboza
The implementation of this hypercall will be modified to use
spapr->numa_assoc_arrays input. Moving it to spapr_numa.c makes
make more sense.
Signed-off-by: Daniel Henrique Barboza
---
hw/ppc/spapr_hcall.c| 37 +
hw/ppc/spapr_numa.c | 36
This has no functional change.
The current function structure is:
inline QEMU_ALWAYSINLINE
store_memop() {
switch () {
...
default:
qemu_build_not_reached();
}
}
inline QEMU_ALWAYSINLINE
store_helper() {
...
if
The next step to centralize all NUMA/associativity handling in
the spapr machine is to create a 'one stop place' for all
things ibm,associativity.
This patch introduces numa_assoc_array, a 2 dimensional array
that will store all ibm,associativity arrays of all NUMA nodes.
This array is
Vcpus have an additional paramenter to be appended, vcpu_id. This
also changes the size of the of property itself, which is being
represented in index 0 of numa_assoc_array[cpu->node_id],
and defaults to MAX_DISTANCE_REF_POINTS for all cases but
vcpus.
All this logic makes more sense in
The following changes since commit 3dd23a4fb8fd72d2220a90a809f213999ffe7f3a:
Merge remote-tracking branch 'remotes/legoater/tags/pull-aspeed-20200901'
into staging (2020-09-03 14:12:48 +0100)
are available in the Git repository at:
https://github.com/rth7680/qemu.git tags/pull-tcg-20200903
From: Jan Charvat
Signed-off-by: Jan Charvat
Signed-off-by: Pavel Pisa
Reviewed-by: Vikram Garhwal
---
hw/net/can/can_sja1000.c | 2 ++
include/net/can_emu.h| 8 ++-
net/can/can_socketcan.c | 47 +---
3 files changed, 53 insertions(+), 4
Signed-off-by: Yonggang Luo
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configure b/configure
index e42d210e5f..ae63c4fd54 100755
--- a/configure
+++ b/configure
@@ -2545,7 +2545,7 @@ fi
# vhost-user backends
test "$vhost_net_user" = "" &&
Hi,
This spin attempts to cover all suggestions and concerns pointed
out by David Gibson in the v2 review.
The patches were rebased with David's ppc-for-5.2 at 615ae3763144.
They can also be cloned from
https://github.com/danielhb/qemu/tree/spapr_numa_v3.
Changes from v2:
- patches 1 and 2 from
We already support duplication of 128-bit blocks. This extends
that support to 256-bit blocks. This will be needed by SVE2.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
tcg/tcg-op-gvec.c | 52 ---
1 file changed, 49
From: Pavel Pisa
CTU CAN FD is an open source soft core written in VHDL.
It originated in 2015 as Ondrej Ille's project at the
Department of Measurement of FEE at CTU.
Integration for Xilinx Zynq and Intel based SoCs is available
as well as support for PCIe integration of the core.
The core
Your pipeline has failed.
Project: QEMU ( https://gitlab.com/qemu-project/qemu )
Branch: master ( https://gitlab.com/qemu-project/qemu/-/commits/master )
Commit: 67a7bfe5 (
https://gitlab.com/qemu-project/qemu/-/commit/67a7bfe560a1bba59efab085cb3430f45176d382
)
Commit Message: Merge
Quoting Alistair Francis (2020-09-01 18:59:29)
> On Mon, Aug 31, 2020 at 10:59 PM Nathan Chancellor
> wrote:
> >
> > When shutting down the machine running a mainline Linux kernel, the
> > following error happens:
> >
> > $ build/riscv64-softmmu/qemu-system-riscv64 -bios default -M virt \
> >
Updated MAINTAINERS for CAN bus related emulation as well.
Signed-off-by: Pavel Pisa
---
MAINTAINERS | 9
docs/can.txt | 113 ++-
2 files changed, 111 insertions(+), 11 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index
From: David Hildenbrand
In case we don't have an iothread, we mark the feature as abscent but
still add the queue. 'free_page_bh' remains set to NULL.
qemu-system-i386 \
-M microvm \
-nographic \
-device virtio-balloon-device,free-page-hint=true \
-nographic \
From: Yuri Benditovich
Removal of duplicated RSC definitions. Changing names of the
fields to ones defined in the Linux header.
Signed-off-by: Yuri Benditovich
Signed-off-by: Jason Wang
(cherry picked from commit dd3d85e89123c907be7628957457af3d03e3b85b)
Conflicts:
From: Jan Charvat
The implementation of the model of complete open-source/design/hardware
CAN FD controller. The IP core project has been started and is maintained
by Ondrej Ille at Czech Technical University in Prague.
CTU CAN FD project pages:
Do not store back to the exact memory from which we just loaded.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
tcg/tcg-op-gvec.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/tcg/tcg-op-gvec.c b/tcg/tcg-op-gvec.c
index 793d4ba64c..fcc25b04e6
From: Graeme Gregory
Fixing a typo in a previous patch that translated an "i" to a 1
and therefore breaking the allocation of PCIe interrupts. This was
discovered when virtio-net-pci devices ceased to function correctly.
Cc: qemu-sta...@nongnu.org
Fixes: 48ba18e6d3f3 ("hw/arm/sbsa-ref: Simplify
Do not set parallel_cpus if there is only one cpu instantiated.
This will allow tcg to use serial code to implement atomics.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
softmmu/cpus.c | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
From: Max Reitz
Signed-off-by: Max Reitz
Message-Id: <20200728120806.265916-3-mre...@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy
Tested-by: Vladimir Sementsov-Ogievskiy
Tested-by: Claudio Fontana
(cherry picked from commit ae159450e161b3e1e2c5b815d19632acd1a1)
Signed-off-by:
From: Eric Blake
Ever since commit 36683283 (v2.8), the server code asserts that error
strings sent to the client are well-formed per the protocol by not
exceeding the maximum string length of 4096. At the time the server
first started sending error messages, the assertion could not be
From: Jan Charvat
Signed-off-by: Jan Charvat
Signed-off-by: Pavel Pisa
Reviewed-by: Vikram Garhwal
---
include/net/can_emu.h | 4
net/can/can_core.c| 36
2 files changed, 40 insertions(+)
diff --git a/include/net/can_emu.h
On Fri, Sep 4, 2020 at 1:20 AM Richard Henderson <
richard.hender...@linaro.org> wrote:
> On 9/3/20 1:31 AM, Yonggang Luo wrote:
> > Rename function dup_const to dup_const_eval for avoid confliction with
> macro dup_const
> >
> > The link error on msys2
> >
> > Linking target
1 - 100 of 640 matches
Mail list logo
