Calling error_report() in a function that takes an Error ** argument
is suspicious. parse_numa() does that, and then fails without setting
an error. Its caller main(), via qemu_opts_foreach(), is fine with
it, but clean it up anyway.
While there, give parse_numa() internal linkage.
Cc: Eduardo
When -netdev l2tpv3 fails, it first reports a specific error, then a
generic one, like this:
$ qemu-system-x86_64 -netdev l2tpv3,id=foo,src=,dst=,txsession=1
qemu-system-x86_64: -netdev l2tpv3,id=foo,src=,dst=,txsession=1:
l2tpv3_open : could not resolve src, errno = Name or service not
main() checks for parse_name() failure even though it can't actually
fail. That's okay. Simplify it to check by passing _fatal,
like the other users of qemu_opts_foreach().
Signed-off-by: Markus Armbruster
---
vl.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/vl.c
Calling error_report() in a function that takes an Error ** argument
is suspicious. chardev_init_func() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Signed-off-by: Markus Armbruster
---
vl.c | 8
Calling error_report() in a function that takes an Error ** argument
is suspicious. parse_sandbox() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Cc: Eduardo Otubo
Signed-off-by: Markus Armbruster
---
Calling error_report() from within a a function that takes an Error **
argument is suspicious. qemu_fsdev_add() does that, and its caller
fsdev_init_func() then fails without setting an error. Its caller
main(), via qemu_opts_foreach(), is fine with it, but clean it up
anyway.
Cc: Greg Kurz
The conversion of "xen-pci-passthrough" to realize() (commit
5a11d0f7549, v2.6.0) neglected to convert the xen_pt_config_init()
error path. If xen_pt_config_init() fails, xen_pt_realize() reports
the error, then returns success without completing its job. I don't
know the exact impact, but it
Calling error_report() in a function that takes an Error ** argument
is suspicious. machine_set_property() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Signed-off-by: Markus Armbruster
---
vl.c | 9
Calling error_report() in a function that takes an Error ** argument
is suspicious. smbios_entry_add() does that, and then exit()s. It
also passes _fatal to qemu_opts_validate(). Both wrong, but
currently harmless, as its only caller passes _fatal. Messed up
in commit 1007a37e208. Clean it
Calling error_report() in a function that takes an Error ** argument
is suspicious. net_socket_fd_init() does that, and then fails without
setting an error. Wrong. I didn't analyze how exactly this can
break. A caller that reports the error on failure would crash.
Broken when commit
Calling error_report() in a function that takes an Error ** argument
is suspicious. parse_add_fd() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Also change call of cleanup_add_fd(), which can't fail, for
Calling error_report() in a function that takes an Error ** argument
is suspicious. Convert a few that are actually help and such to
error_printf().
Improves output of -chardev help from
qemu-system-x86_64: -chardev help: Available chardev backend types:
serial
...
to
Calling error_report() in a function that takes an Error ** argument
is suspicious. Convert a few that are actually warnings to
warn_report().
While there, split a warning consisting of multiple sentences to
conform to conventions spelled out in warn_report()'s contract.
Cc: Alex Bennée
Cc:
Calling error_report() in a function that takes an Error ** argument
is suspicious. add_channel() does that, and then exit()s. Its caller
main(), via qemu_opts_foreach(), is fine with it, but clean it up
anyway.
Cc: Gerd Hoffmann
Signed-off-by: Markus Armbruster
---
ui/spice-core.c | 13
Calling error_report() in a function that takes an Error ** argument
is suspicious. parse_numa_node() does that, and then exit()s. It
also passes _fatal to machine_set_cpu_numa_node(). Both wrong.
Attempting to configure numa when the machine doesn't support it kills
the VM:
$
The previous commit changed vfio's warning messages from
vfio warning: DEV-NAME: Could not frobnicate
to
warning: vfio DEV-NAME: Could not frobnicate
To match this change, change error messages from
vfio error: DEV-NAME: On fire
to
vfio DEV-NAME: On fire
Note the loss of
Calling error_report() or similar in a function that takes an Error **
argument is suspicious. Fux a number of instances that are actually
wrong. Clean up a few more that are merely fragile / bad examples.
Markus Armbruster (31):
Use error_fatal to simplify obvious fatal errors (again)
Calling error_report() in a function that takes an Error ** argument
is suspicious. pc.c's pc_machine_set_nvdimm_persistence() does that,
and then exit()s. Wrong. Attempting to set machine property
nvdimm-persistence to a bad value instantly kills the VM:
$ qemu-system-x86_64 -nodefaults
The vfio code reports warnings like
error_report(WARN_PREFIX "Could not frobnicate", DEV-NAME);
where WARN_PREFIX is defined so the message comes out as
vfio warning: DEV-NAME: Could not frobnicate
This usage predates the introduction of warn_report() & friends in
commit 97f40301f1d.
Calling error_report() in a function that takes an Error ** argument
is suspicious. user_creatable_add_opts_foreach() does that, and then
fails without setting an error. Its caller main(), via
qemu_opts_foreach(), is fine with it, but clean it up anyway.
Cc: Daniel P. Berrangé
Signed-off-by:
Calling error_report() in a function that takes an Error ** argument
is suspicious. vnc_init_func() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Cc: Gerd Hoffmann
Signed-off-by: Markus Armbruster
---
Calling error_report() in a function that takes an Error ** argument
is suspicious. Convert a few that are actually warnings to
warn_report().
While there, split warnings consisting of multiple sentences to
conform to conventions spelled out in warn_report()'s contract, and
improve a rather
If creating (empty) default drives fails, it's a bug. Therefore,
assert() is more appropriate than exit(1).
Cc: Kevin Wolf
Cc: Max Reitz
Signed-off-by: Markus Armbruster
---
vl.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/vl.c b/vl.c
index 4aa976c4cc..0d25956b2f
Calling error_report() in a function that takes an Error ** argument
is suspicious. mon_init_func() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Signed-off-by: Markus Armbruster
---
vl.c | 14
Calling error_report() in a function that takes an Error ** argument
is suspicious. ioapic_realize() does that, and then exit()s.
Currently mostly harmless, as the device cannot be hot-plugged.
Fixes: 20fd4b7b6d9282fe0cb83601f1821f31bd257458
Cc: Peter Xu
Signed-off-by: Markus Armbruster
---
Add a slight improvement of the Coccinelle semantic patch from commit
07d04a0219b, and use it to clean up. It leaves dead Error * variables
behind, cleaned up manually.
Cc: David Gibson
Cc: Alexander Graf
Cc: Eric Blake
Cc: Paolo Bonzini
Signed-off-by: Markus Armbruster
---
Calling error_report() in a function that takes an Error ** argument
is suspicious. save_snapshot() and load_snapshot() do that, and then
fail without setting an error. Wrong. The HMP commands survive this
unscathed, since hmp_handle_error() does nothing when no error has
been set. Callers
Calling error_report() in a function that takes an Error ** argument
is suspicious. device_init_func() does that, and then fails without
setting an error. Its caller main(), via qemu_opts_foreach(), is fine
with it, but clean it up anyway.
Signed-off-by: Markus Armbruster
---
vl.c | 10
Calling error_report() in a function that takes an Error ** argument
is suspicious. tpm_init_tpmdev() does that, and then fails without
setting an error. Its caller main(), via tpm_init() and
qemu_opts_foreach(), is fine with it, but clean it up anyway.
Cc: Stefan Berger
Signed-off-by: Markus
Gentle ping on v2 of this series.
(I noticed 1st patch of series was already applied)
Thanks,
-Liran
> On 16 Sep 2018, at 15:46, Liran Alon wrote:
>
> Hi,
>
> This series aims to add support for QEMU to be able to migrate VMs that
> are running nested hypervisors. In order to do so, it
On 8 October 2018 at 17:40, Kevin Wolf wrote:
> By the way, can you reproduce this with virtio-blk/scsi and an iothread
> in a real QEMU or is it only the test case that fails? In theory, I
> don't see what would prevent QEMU from hanging at shutdown.
I haven't tested, but I suspect this is less
On 10/07/2018 07:51 PM, Max Reitz wrote:
> On 26.09.18 20:05, Jeff Cody wrote:
>> I'll not be involved in day-to-day qemu development. Remove myself as
>> maintainer from the remainder of the network block drivers, and revert
>> them to the general block layer maintainership.
>>
>> Move
Am 08.10.2018 um 18:04 hat Anton Nefedov geschrieben:
>
>
> On 8/10/2018 6:46 PM, Kevin Wolf wrote:
> > Am 08.10.2018 um 17:25 hat Anton Nefedov geschrieben:
> >>
> >>
> >> On 8/10/2018 6:03 PM, Kevin Wolf wrote:
> >>> Am 08.10.2018 um 16:38 hat Anton Nefedov geschrieben:
> On 4/10/2018
Hi Alex,
On Mon, Oct 8, 2018 at 5:21 PM Alex Bennée wrote:
> We have reached the point where the MacOSX build was regularly timing
> out. So as before I've reduced the target list to "major"
> architectures to try and bring the build time down. I've added an
> additional MacOSX build with the
Am 08.10.2018 um 17:43 hat Peter Maydell geschrieben:
> Looking at the backtraces I'm wondering if this is the result of
> an implicit reliance on the order in which per-thread destructors
> are called (which is left unspecified by POSIX) -- the destructor
> function qemu_thread_atexit_run() is
Hi Li,
On Sun, Oct 7, 2018 at 7:48 PM Philippe Mathieu-Daudé wrote:
> On 10/7/18 6:33 AM, Li Qiang wrote:
> > It makes sense to print the error message while reading
> > file failed.
> >
> > Signed-off-by: Li Qiang
> > ---
> > vl.c | 5 +++--
> > 1 file changed, 3 insertions(+), 2 deletions(-)
Userspace submits a USB Request Buffer to the kernel, optionally
discards it, and finally reaps the URB. Thunk buffers from target
to host and back.
Tested by running an i386 scanner driver on ARMv7 and by running
the PowerPC lsusb utility on x86_64. The discardurb ioctl is
not exercised in
In preparation for adding user mode emulation support for the
Linux usbfs interface, check for its kernel header.
Signed-off-by: Cortland Tölva
Reviewed-by: Laurent Vivier
Message-Id: <20180925071228.32040-2-...@tolva.net>
Signed-off-by: Laurent Vivier
---
configure | 12 +++-
1 file
Provide ioctl definitions for the generic thunk mechanism to
convert most usbfs calls. Calculate arg size at runtime.
Signed-off-by: Cortland Tölva
---
Changes from v1:
move some type definitions to patch 3/3
Changes from v2:
calculate ioctl arg size at runtime
linux-user/ioctls.h
This patch series enables programs running under QEMU Linux user mode
emulation to implement user-space USB drivers via the USBFS ioctl()s.
Support is limited to control, bulk, and possibly interrupt transfers.
The series compiles for i386, ppc64, ppc64le, mips, mipsel, xtensa, and
xtensaeb with
On 10/08/2018 10:44 AM, Thomas Huth wrote:
On 2018-10-08 16:20, Tony Krowiak wrote:
On 09/27/2018 08:52 AM, Cornelia Huck wrote:
On Thu, 27 Sep 2018 14:29:01 +0200
Thomas Huth wrote:
On 2018-09-27 00:54, Tony Krowiak wrote:
From: Tony Krowiak
Introduces the base object model for
On Mon, 8 Oct 2018 17:32:04 +0200
David Hildenbrand wrote:
> linux-user should always enable AFP, otherwise our emulated binary
> might crash once it tries to make use of additional floating-point
> registers or instructions.
>
> Cc: Peter Maydell
> Cc: Alex Bennée
> Fixes: db0504154e
David Hildenbrand writes:
> linux-user should always enable AFP, otherwise our emulated binary
> might crash once it tries to make use of additional floating-point
> registers or instructions.
>
> Cc: Peter Maydell
> Cc: Alex Bennée
> Fixes: db0504154e ("s390x/tcg: check for AFP-register,
On Mon, 8 Oct 2018 17:32:04 +0200
David Hildenbrand wrote:
> linux-user should always enable AFP, otherwise our emulated binary
> might crash once it tries to make use of additional floating-point
> registers or instructions.
>
> Cc: Peter Maydell
> Cc: Alex Bennée
> Fixes: db0504154e
On 8/10/2018 6:46 PM, Kevin Wolf wrote:
> Am 08.10.2018 um 17:25 hat Anton Nefedov geschrieben:
>>
>>
>> On 8/10/2018 6:03 PM, Kevin Wolf wrote:
>>> Am 08.10.2018 um 16:38 hat Anton Nefedov geschrieben:
On 4/10/2018 6:33 PM, Kevin Wolf wrote:
> Am 21.08.2018 um 11:46 hat Anton Nefedov
On 10/8/18 8:32 AM, David Hildenbrand wrote:
> linux-user should always enable AFP, otherwise our emulated binary
> might crash once it tries to make use of additional floating-point
> registers or instructions.
>
> Cc: Peter Maydell
> Cc: Alex Bennée
> Fixes: db0504154e ("s390x/tcg: check for
POSTCOPY_NOTIFY_INBOUND_END handlers will remove userfault fds
from the postcopy_remote_fds array which could be still in
use by the fault thread. Let's stop the thread before
notification to avoid possible accessing wrong memory.
Fixes: 46343570c06e ("vhost+postcopy: Wire up POSTCOPY_END
'fd' received from the vhost side is never freed.
Also, everything (including 'postcopy_listen' state) should be
cleaned up on vhost cleanup.
Fixes: 46343570c06e ("vhost+postcopy: Wire up POSTCOPY_END notify")
Fixes: f82c11165ffa ("vhost+postcopy: Register shared ufd with postcopy")
Cc:
Sending as RFC because it's not fully tested yet.
Ilya Maximets (2):
migration: Stop postcopy fault thread before notifying
vhost-user: Fix userfaultfd leak
hw/virtio/vhost-user.c | 7 +++
migration/postcopy-ram.c | 11 ++-
2 files changed, 13 insertions(+), 5 deletions(-)
Am 08.10.2018 um 17:25 hat Anton Nefedov geschrieben:
>
>
> On 8/10/2018 6:03 PM, Kevin Wolf wrote:
> > Am 08.10.2018 um 16:38 hat Anton Nefedov geschrieben:
> >> On 4/10/2018 6:33 PM, Kevin Wolf wrote:
> >>> Am 21.08.2018 um 11:46 hat Anton Nefedov geschrieben:
> Signed-off-by: Anton
On 17.08.18 14:22, Vladimir Sementsov-Ogievskiy wrote:
> Reduce number of structures ignored in overlap check: when checking
> active table ignore active tables, when checking inactive table ignore
> inactive ones.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> block/qcow2-refcount.c |
On 8 October 2018 at 10:12, Peter Maydell wrote:
> I looked back at the backtrace/etc that I posted earlier in this
> thread, and it looked to me like maybe a memory corruption issue.
> So I tried running the test under valgrind on Linux, and:
...which goes away if I do a complete build from
On 17.08.18 14:22, Vladimir Sementsov-Ogievskiy wrote:
> Separate offset and size of compressed cluster.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> block/qcow2-refcount.c | 15 ++-
> 1 file changed, 10 insertions(+), 5 deletions(-)
>
> diff --git
On 2018-10-08 17:32, David Hildenbrand wrote:
> linux-user should always enable AFP, otherwise our emulated binary
> might crash once it tries to make use of additional floating-point
> registers or instructions.
>
> Cc: Peter Maydell
> Cc: Alex Bennée
> Fixes: db0504154e ("s390x/tcg: check for
26.06.2018 11:44, Vladimir Sementsov-Ogievskiy wrote:
> 25.06.2018 20:50, Dr. David Alan Gilbert wrote:
>> * Dr. David Alan Gilbert (dgilb...@redhat.com) wrote:
>>> * Vladimir Sementsov-Ogievskiy (vsement...@virtuozzo.com) wrote:
15.06.2018 15:06, Dr. David Alan Gilbert wrote:
> *
On 17.08.18 14:22, Vladimir Sementsov-Ogievskiy wrote:
> qcow2_inc_refcounts_imrt() (through realloc_refcount_array()) can eat
> an unpredictable amount of memory on corrupted table entries, which are
> referencing regions far beyond the end of file.
>
> Prevent this, by skipping such regions
linux-user should always enable AFP, otherwise our emulated binary
might crash once it tries to make use of additional floating-point
registers or instructions.
Cc: Peter Maydell
Cc: Alex Bennée
Fixes: db0504154e ("s390x/tcg: check for AFP-register, BFP and DFP data
exceptions")
Reported-by:
On 17.08.18 14:22, Vladimir Sementsov-Ogievskiy wrote:
> Increase corruptions_fixed only after successful fix.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy
> ---
> block/qcow2-refcount.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/block/qcow2-refcount.c
On 8/10/2018 6:03 PM, Kevin Wolf wrote:
> Am 08.10.2018 um 16:38 hat Anton Nefedov geschrieben:
>> On 4/10/2018 6:33 PM, Kevin Wolf wrote:
>>> Am 21.08.2018 um 11:46 hat Anton Nefedov geschrieben:
Signed-off-by: Anton Nefedov
Reviewed-by: Alberto Garcia
---
hw/ide/core.c
We have reached the point where the MacOSX build was regularly timing
out. So as before I've reduced the target list to "major"
architectures to try and bring the build time down. I've added an
additional MacOSX build with the latest XCode with a minimal list of
"most likely" targets on MacOS.
On Sun, Oct 7, 2018 at 11:59 PM Laurent Vivier wrote:
>
> Le 08/10/2018 à 06:27, Cortland Tölva a écrit :
> > From: Cortland Setlow Tölva
> >
> > This patch series enables programs running under QEMU Linux user mode
> > emulation to implement user-space USB drivers via the USBFS ioctl()s.
> >
On 08/10/2018 17:02, Alex Bennée wrote:
>
> Peter Maydell writes:
>
>> On 4 October 2018 at 16:28, Cornelia Huck wrote:
>>> The following changes since commit dafd95053611aa14dda40266857608d12ddce658:
>>>
>>> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
>>> staging
ping
Hi, what about this?
17.08.2018 15:22, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> v2:
> 02, 06: check bdrv_getlength error return code
>
> v1:
>
> We've faced the following problem: after host fs corruption, vm images
> becomes invalid. And which is interesting, starting qemu-img
From: Yongbok Kim
The optional Data Scratch Pad RAM (DSPRAM) block provides a
general scratch pad RAM used for temporary storage of data. The
DSPRAM provides a connection to on-chip memory or memory-mapped
registers, which are accessed in parallel with the L1 data
cache to minimize access
From: Dimitrije Nikolic
Implement emulation of nanoMIPS EVA instructions. They are all
part of P.LS.E0 instruction pool, or one of its subpools.
Signed-off-by: Dimitrije Nikolic
Signed-off-by: Aleksandar Markovic
---
target/mips/translate.c | 79
From: Yongbok Kim
Update the ITU to utilise SAARI/SAAR registers and add new ITU
Control Register (ICR0).
Signed-off-by: Yongbok Kim
Signed-off-by: Aleksandar Markovic
---
hw/mips/cps.c | 8 ++
hw/misc/mips_itu.c | 72 +-
From: Stefan Markovic
Add MIPS_ABI_FP_XXX constants to elf.h. The source of information
is kernel header arch/mips/include/asm/elf.h.
Signed-off-by: Stefan Markovic
Signed-off-by: Aleksandar Markovic
---
include/elf.h | 8
1 file changed, 8 insertions(+)
diff --git a/include/elf.h
Am 08.10.2018 um 16:38 hat Anton Nefedov geschrieben:
> On 4/10/2018 6:33 PM, Kevin Wolf wrote:
> > Am 21.08.2018 um 11:46 hat Anton Nefedov geschrieben:
> >> Signed-off-by: Anton Nefedov
> >> Reviewed-by: Alberto Garcia
> >> ---
> >> hw/ide/core.c | 12
> >> 1 file changed, 12
From: Yongbok Kim
SAARI (Special Address Access Register Index) provides an index
into the SAAR register to indicate whether the ITU or other block
is being accessed. SAAR (Special Address Access Register) stores
the base address where the ITU will be located, as well as the
block size.
From: Stefan Markovic
Add DSP R3 ASE related bit definition for insn_flags and hflags.
Reviewed-by: Aleksandar Markovic
Signed-off-by: Stefan Markovic
Signed-off-by: Aleksandar Markovic
---
target/mips/cpu.h | 1 +
target/mips/mips-defs.h | 1 +
2 files changed, 2 insertions(+)
diff
Peter Maydell writes:
> On 4 October 2018 at 16:28, Cornelia Huck wrote:
>> The following changes since commit dafd95053611aa14dda40266857608d12ddce658:
>>
>> Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into
>> staging (2018-10-02 18:27:18 +0100)
>>
>> are available in
From: Yongbok Kim
WatchHi is extended by the field MemoryMapID with the GINVT
instruction. The field is accessible by MTHC0/MFHC0 in 32-bit
architectures and DMTC0/DMFC0 in 64-bit architectures.
Signed-off-by: Yongbok Kim
Signed-off-by: Aleksandar Markovic
---
target/mips/cpu.h | 2 +-
From: Stefan Markovic
Add Mips_elf_abiflags_v0 structure to elf.h. The source of information
is kernel header arch/mips/include/asm/elf.h.
Signed-off-by: Stefan Markovic
Signed-off-by: Aleksandar Markovic
---
include/elf.h | 15 +++
1 file changed, 15 insertions(+)
diff --git
From: Yongbok Kim
Add I6500 core configuration. Note that this configuration is
supported only by best-effort due to lack of certain features
in QEMU.
Signed-off-by: Yongbok Kim
Signed-off-by: Aleksandar Markovic
---
target/mips/translate_init.inc.c | 43
From: Stefan Markovic
Add infrastructure for availability control for DSP R3 ASE MIPS
instructions. Only BPOSGE32C currently belongs to DSP R3 ASE, but
this is likely to be changed in near future.
Reviewed-by: Aleksandar Markovic
Signed-off-by: Stefan Markovic
Signed-off-by: Aleksandar
From: Dimitrije Nikolic
Add opcodes for nanoMIPS EVA instructions: CACHEE, LBE, LBUE, LHE,
LHUE, LLE, LLWPE, LWE, PREFE, SBE, SCE, SCWPE, SHE, SWE.
Signed-off-by: Dimitrije Nikolic
Signed-off-by: Aleksandar Markovic
---
target/mips/translate.c | 34 ++
1 file
From: Stefan Markovic
Fix existing and add missing PT_MIPS_XXX constants in elf.h.
This is copied from kernel header arch/mips/include/asm/elf.h.
Signed-off-by: Stefan Markovic
Signed-off-by: Aleksandar Markovic
---
include/elf.h | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
On 10/08/2018 10:35 AM, Cornelia Huck wrote:
On Mon, 8 Oct 2018 16:22:27 +0200
David Hildenbrand wrote:
On 08/10/2018 16:20, Tony Krowiak wrote:
On 09/27/2018 08:52 AM, Cornelia Huck wrote:
On Thu, 27 Sep 2018 14:29:01 +0200
Thomas Huth wrote:
On 2018-09-27 00:54, Tony Krowiak wrote:
From: Aleksandar Markovic
This series contains support for MIPS ABI flags in elf.h, DSP R3
availability control, and emulation of nanoMIPS EVA instructions.
MIPS ABI flags will be used in near future for linux user mode
support for certain MIPS-specific parts of prctl() system call.
This series
On 4/10/2018 6:33 PM, Kevin Wolf wrote:
> Am 21.08.2018 um 11:46 hat Anton Nefedov geschrieben:
>> Signed-off-by: Anton Nefedov
>> Reviewed-by: Alberto Garcia
>> ---
>> hw/ide/core.c | 12
>> 1 file changed, 12 insertions(+)
>>
>> diff --git a/hw/ide/core.c b/hw/ide/core.c
>>
On Thu, Sep 13, 2018 at 01:06:00PM +0200, Igor Mammedov wrote:
> Changelog since v7:
> * drop repetitive sentence in deprication doc (Eric Blake
> )
> Changelog since v5:
> * add(v6) and then remove(v7) Notes section to/from deprication doc
> (Eduardo Habkost )
> * fix up wording and
On 09/27/2018 08:52 AM, Cornelia Huck wrote:
On Thu, 27 Sep 2018 14:29:01 +0200
Thomas Huth wrote:
On 2018-09-27 00:54, Tony Krowiak wrote:
From: Tony Krowiak
Introduces the base object model for virtualizing AP devices.
Signed-off-by: Tony Krowiak
---
+typedef struct APBridge {
+
On 4/10/2018 6:47 PM, Kevin Wolf wrote:
> Am 21.08.2018 um 11:46 hat Anton Nefedov geschrieben:
>> Signed-off-by: Anton Nefedov
>> Reviewed-by: Vladimir Sementsov-Ogievskiy
>> Reviewed-by: Alberto Garcia
>> ---
>> hw/scsi/scsi-disk.c | 9 -
>> 1 file changed, 8 insertions(+), 1
ing changes since commit 079911cb6e26898e16f5bb56ef4f9d33cf92d32d:
>
> Merge remote-tracking branch 'remotes/rth/tags/pull-fpu-20181005' into
> staging (2018-10-08 12:44:35 +0100)
>
> are available in the Git repository at:
>
> https://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-tar
On 04/10/2018 18:08, Wei Huang wrote:
> This patch adds migration test support for aarch64. The test code, which
> implements the same functionality as x86, is booted as a kernel in qemu.
> Here are the design choices we make for aarch64:
>
> * We choose this -kernel approach because aarch64
On Sun, Oct 07, 2018 at 19:09:01 -0700, Richard Henderson wrote:
> On 10/6/18 2:45 PM, Emilio G. Cota wrote:
> > Currently we evict an entry to the victim TLB when it doesn't match
> > the current address. But it could be that there's no match because
> > the current entry is invalid. Do not evict
On 2018-10-08 16:20, Tony Krowiak wrote:
> On 09/27/2018 08:52 AM, Cornelia Huck wrote:
>> On Thu, 27 Sep 2018 14:29:01 +0200
>> Thomas Huth wrote:
>>
>>> On 2018-09-27 00:54, Tony Krowiak wrote:
From: Tony Krowiak
Introduces the base object model for virtualizing AP devices.
From: Dongjiu Geng
The parameter of kvm_arm_init_cpreg_list() is ARMCPU instead of
CPUState, so correct the note to make it match the code.
Signed-off-by: Dongjiu Geng
Message-id: 1538069046-5757-1-git-send-email-gengdong...@huawei.com
Reviewed-by: Peter Maydell
Signed-off-by: Peter Maydell
Emilio G. Cota writes:
> On Mon, Oct 08, 2018 at 14:57:18 +0100, Alex Bennée wrote:
>> Emilio G. Cota writes:
>> > The readers that do not hold tlb_lock must use atomic reads when
>> > reading .addr_write, since this field can be updated by other threads;
>> > the conversion to atomic reads
From: Richard Henderson
Check for EL3 before testing CPTR_EL3.EZ. Return 0 when the exception
should be routed via AdvSIMDFPAccessTrap. Mirror the structure of
CheckSVEEnabled more closely.
Fixes: 5be5e8eda78
Reviewed-by: Peter Maydell
Tested-by: Laurent Desnogues
Signed-off-by: Richard
Emilio G. Cota writes:
> On Mon, Oct 08, 2018 at 11:28:38 +0100, Alex Bennée wrote:
>> Emilio G. Cota writes:
>> > Again, for performance you'd avoid the tracepoint (i.e. calling
>> > a helper to call another function) and embed directly the
>> > callback from TCG. Same thing applies to TB's.
From: Richard Henderson
We are going to want to determine whether sve is enabled
for EL other than current.
Tested-by: Laurent Desnogues
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
Message-id: 20181005175350.30752-4-richard.hender...@linaro.org
Signed-off-by: Peter Maydell
Add the v8M stack checks for:
* LDRD (immediate)
* STRD (immediate)
Loads and stores are more complicated than ADD/SUB/MOV, because we
must ensure that memory accesses below the stack limit are not
performed, so we can't simply do the check when we actually update
SP.
For these instructions,
On Mon, 8 Oct 2018 16:22:27 +0200
David Hildenbrand wrote:
> On 08/10/2018 16:20, Tony Krowiak wrote:
> > On 09/27/2018 08:52 AM, Cornelia Huck wrote:
> >> On Thu, 27 Sep 2018 14:29:01 +0200
> >> Thomas Huth wrote:
> >>
> >>> On 2018-09-27 00:54, Tony Krowiak wrote:
> From: Tony
Add v8M stack checks for the 16-bit Thumb push/pop
encodings: STMDB, STMFD, LDM, LDMIA, LDMFD.
Signed-off-by: Peter Maydell
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Richard Henderson
Message-id: 20181002163556.10279-12-peter.mayd...@linaro.org
---
target/arm/translate.c | 16
On 3 October 2018 at 16:07, Edgar E. Iglesias wrote:
> In QEMU we'd like to have a virtual developer board with the Versal SoC
> and a selected set of peripherals under the control of QEMU.
> We'd like to gradually extend this board as QEMU gains more support
> for Versal hardware components.
> From: Dimitrije Nikolic
>
> Add opcodes for nanoMIPS EVA instructions: CACHEE, LBE, LBUE, LHE,
LHUE, LLE, LLWPE, LWE, PREFE, SBE, SCE, SCWPE, SHE, SWE.
>
> Signed-off-by: Aleksandar Markovic
This patch is incomplete. The pool P.LS.E0 has three subpools, and, for each of
them,
Coverity complains (CID 1395628) that the multiply in the calculation
of the framebuffer base is performed as 32x32 but then used in a
context that takes a 64-bit hwaddr. This can't actually ever
overflow the 32-bit result, because of the constraints placed on
the s->config values in
On 08/10/2018 16:20, Tony Krowiak wrote:
> On 09/27/2018 08:52 AM, Cornelia Huck wrote:
>> On Thu, 27 Sep 2018 14:29:01 +0200
>> Thomas Huth wrote:
>>
>>> On 2018-09-27 00:54, Tony Krowiak wrote:
From: Tony Krowiak
Introduces the base object model for virtualizing AP devices.
On Mon, 8 Oct 2018 14:41:50 +0200
David Hildenbrand wrote:
> On 08/10/2018 14:19, Igor Mammedov wrote:
> > On Mon, 8 Oct 2018 13:47:53 +0200
> > David Hildenbrand wrote:
> >
> >>> That way using [2] and [1 - modulo it should match only concrete type]
> >>> machine would be able to override
101 - 200 of 293 matches
Mail list logo
