From: Li Qiang
Signed-off-by: Li Qiang
Tested-by: Thomas Huth
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Message-Id: <20190424140643.62457-6-liq...@163.com>
Signed-off-by: Philippe Mathieu-Daudé
---
tests/fw_cfg-test.c | 20
1 file changed, 20
From: Li Qiang
The current codebase is not specific about the endianess of the
fw_cfg 'file' entry 'reboot-timeout'.
Per docs/specs/fw_cfg.txt:
=== All Other Data Items ===
Please consult the QEMU source for the most up-to-date
and authoritative list of selector keys and their respective
On Sat, 18 May 2019 at 20:19, Richard Henderson
wrote:
>
> This replaces 3 target-specific implementations for BIT, BIF, and BSL.
>
> Signed-off-by: Richard Henderson
> @@ -10916,13 +10925,13 @@ static void disas_simd_3same_logic(DisasContext *s,
> uint32_t insn)
> return;
>
> case
We allocate the QFWCFG object previous to run the qtests,
free it once we are finished.
Signed-off-by: Li Qiang
Message-Id: <20190424140643.62457-2-liq...@163.com>
Reviewed-by: Philippe Mathieu-Daudé
[PMD: Split patch, fill commit description]
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by:
On 22/5/2019 11:40 PM, Max Reitz wrote:
> On 16.05.19 16:27, Anton Nefedov wrote:
>> If COW areas of the newly allocated clusters are zeroes on the backing
>> image, efficient bdrv_write_zeroes(flags=BDRV_REQ_NO_FALLBACK) can be
>> used on the whole cluster instead of writing explicit zero buffers
On Mon, 20 May 2019 at 17:32, Philippe Mathieu-Daudé wrote:
>
> On 5/20/19 3:32 PM, Cédric Le Goater wrote:
> >> Peter,
> >>
> >> do you want me to resend with only the two first patches and include
> >> Joel's in the same series ? I would leave out the part Philippe is
> >> covering in his object
On 10.05.19 21:03, John Snow wrote:
> Don't pull events out of the queue that don't belong to us;
> be choosier so that we can use this method to drive jobs that
> were launched by transactions that may have more jobs.
>
> Signed-off-by: John Snow
> ---
> tests/qemu-iotests/iotests.py | 32 +
On 5/23/19 4:27 AM, David Hildenbrand wrote:
> On 23.05.19 04:42, Richard Henderson wrote:
>> Enable s390x, aka SYSZ, in the git submodule build.
>> Set the capstone parameters for both s390x host and guest.
>> Install a skipdata hook to keep capstone in sync with the
>> instruction stream for unkn
On 23.05.19 14:27, Richard Henderson wrote:
> On 5/23/19 3:50 AM, David Hildenbrand wrote:
>> /*
>> * Returns the number of bits composing one element.
>> */
>> static uint8_t get_element_bits(uint8_t es)
>> {
>> return (1 << es) * BITS_PER_BYTE;
>> }
>>
>> /*
>> * Returns the bitmask for a
On 23/05/2019 13:56, Cornelia Huck wrote:
> On Wed, 22 May 2019 15:22:23 +0200
> Aleksandar Markovic wrote:
>
>> The alternative way of invoking via IPCV6 (else part of “ifdef
>> __NR_MSGSND”) should work for MIPS in the present stage of headers and
>> kernel.
>
> I tried to do that so that we h
On 5/23/19 3:50 AM, David Hildenbrand wrote:
> /*
> * Returns the number of bits composing one element.
> */
> static uint8_t get_element_bits(uint8_t es)
> {
> return (1 << es) * BITS_PER_BYTE;
> }
>
> /*
> * Returns the bitmask for a single element.
> */
> static uint64_t get_single_elem
We use a ClpRspQueryPci structure to hold the information
related to zPCI Function.
This allows us to be ready to support different zPCI functions
and to retrieve the zPCI function information from the host.
Signed-off-by: Pierre Morel
---
hw/s390x/s390-pci-bus.c | 22 +-
h
We use a S390PCIGroup structure to hold the information
related to zPCI Function group.
This allows us to be ready to support multiple groups and to retrieve
the group information from the host.
Signed-off-by: Pierre Morel
---
hw/s390x/s390-pci-bus.c | 42 ++
This should be copied from Linux kernel UAPI includes.
The version used here is Linux 5.1.0
We define a new device region in vfio.h to be able to
get the ZPCI CLP information by reading this region from
userland.
We create a new file, vfio_zdev.h to define the structure
of the new region we defin
This patch implement the QEMU part to retrieve ZPCI specific
information from the host.
The Linux part has been posted on a separate patch on the LKML.
Subject: [PATCH 0/4] Retrieving zPCI specific info with VFIO
Message-Id: <1557476555-20256-1-git-send-email-pmo...@linux.ibm.com>
We use the
We use the VFIO_REGION_SUBTYPE_ZDEV_CLP subregion of
PCI_VENDOR_ID_IBM to retrieve the CLP information the
kernel exports.
To be compatible with previous kernel versions we fall back
on previous predefined values, same as the emulation values,
when the region is not found or when any problem happe
To have a clean separation between s390-pci-bus.h
and s390-pci-inst.h headers we export the PCI CLP
instructions in a dedicated header.
Signed-off-by: Pierre Morel
Reviewed-by: Collin Walling
---
hw/s390x/s390-pci-bus.h | 1 +
hw/s390x/s390-pci-clp.h | 211 ++
On 5/22/19 4:20 AM, Paolo Bonzini wrote:
> On 21/05/19 22:37, Eduardo Habkost wrote:
>>> But this is the one we're going with? Do we have a plan for teaching it
>>> not to panic for our use of named custom types?
>>
>> If I understood correctly, the patch from Paolo that I have
>> forwarded to t
Sphinx, through Pygments, does not like annotated json examples very
much. In some versions of Sphinx (1.7), it will render the non-json
portions of code blocks in red, but in newer versions (2.0) it will
throw an exception and not highlight the block at all. Though we can
suppress this warning, it
QMP isn't json. It turns out Pygments cares about this.
Teach Pygments to go with the annotated flow.
V2:
- Change GPL2 to GPLv2+ (Peter Maydell)
- Change "highlights" to "lexes" in docstrings
- Fix typo ("Sphinx()" => "Sphinx") in docstring
Reported-by: Aarushi Mehta
John Snow (2):
sphinx
The annotated style json we use in QMP documentation is not strict json
and depending on the version of Sphinx (2.0+) or Pygments installed,
might cause the build to fail.
Use the new QMP lexer.
Further, some versions of Sphinx can not apply custom lexers to "code"
directives and require the use
On Thu, 23 May 2019 at 13:09, Markus Armbruster wrote:
> Registering qbus_reset_all_fn() in main() is kind of ugly, but it works.
> There's a comment pointing out it's ugly. Right now it's a TODO
> comment, which maybe expresses more hope for cleanup than there really
> is. I'd leave it alone an
Peter Maydell writes:
> On Thu, 23 May 2019 at 07:39, Markus Armbruster wrote:
>>
>> Peter Maydell writes:
>> > It's a well-defined order, but it doesn't actually help in a
>> > lot of cases, because often the thing you care about ordering
>> > on is not a device or is not in the same tree as t
Hi
On Thu, May 23, 2019 at 9:54 AM P J P wrote:
>
> +-- On Wed, 22 May 2019, Marc-André Lureau wrote --+
> | On Sun, May 19, 2019 at 10:55 AM P J P wrote:
> | > Qemu guest agent while executing user commands does not seem to
> | > check length of argument list and/or environment variables passed
On 5/23/19 1:27 PM, Thomas Huth wrote:
> On 22/05/2019 20.19, Aaro Koskinen wrote:
>> Hi,
>>
>> On Wed, May 22, 2019 at 11:33:41AM +0200, Corentin Labbe wrote:
>>> qemu-system-arm -M help |grep OMAP
>>> cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310)
>>> n800 Nokia N
On Wed, May 22, 2019 at 03:02:38PM +0200, Johannes Berg wrote:
> Hi,
>
> While my main interest is mostly in UML right now [1] I've CC'ed the
> qemu and virtualization lists because something similar might actually
> apply to other types of virtualization.
>
> I'm thinking about adding virt-io su
On Wed, 22 May 2019 15:22:23 +0200
Aleksandar Markovic wrote:
> The alternative way of invoking via IPCV6 (else part of “ifdef
> __NR_MSGSND”) should work for MIPS in the present stage of headers and
> kernel.
I tried to do that so that we have at least a workaround for now; but
this fails build
On Wed, 22 May 2019 at 17:13, Laurent Vivier wrote:
>
> The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
> staging (2019-05-21 16:30:13 +0100)
>
> are available in the Git repository at:
>
>
Hello Cédric,
How stupid of me. I overlooked that the SPI is for the host flash device.
The remainder of the solution was clear and understood.
Best regards and thanks for the quick response,
Wim
-Original Message-
From: Cédric Le Goater [mailto:c...@kaod.org]
Sent: Thursday, May 23,
On Tue, May 07, 2019 at 02:00:59PM -0700, Elena Ufimtseva wrote:
> On Mon, Mar 11, 2019 at 10:20:06AM +, Daniel P. Berrangé wrote:
> > On Thu, Mar 07, 2019 at 03:29:41PM -0800, John G Johnson wrote:
> > >
> > >
>
> Hi Daniel, Stefan
>
> We have not replied in a while as we were trying to fi
Hi Peter,
On 05/22/19 23:15, Peter Maydell wrote:
> On Wed, 22 May 2019 at 15:22, Laszlo Ersek wrote:
>> This is very interesting. I had obviously tested booting
>> "bios-tables-test.aarch64.iso.qcow2" against "edk2-aarch64-code.fd",
>> using TCG, on my x86_64 laptop. (And, I've run the above exa
Daniel P. Berrangé writes:
> On Wed, May 22, 2019 at 10:42:27PM -0400, Richard Henderson wrote:
>> Since v4.0, capstone.h has moved to .
>
> NB this was a regression bug in capstone pkg-config file which has been
> fixed upstream
>
>https://github.com/aquynh/capstone/pull/1276
>
> In Fedora
On Thu, May 23, 2019 at 01:17:40PM +0200, Philippe Mathieu-Daudé wrote:
> On 5/23/19 1:07 PM, Daniel P. Berrangé wrote:
> > On Wed, May 22, 2019 at 10:42:27PM -0400, Richard Henderson wrote:
> >> Since v4.0, capstone.h has moved to .
> >
> > NB this was a regression bug in capstone pkg-config file
On 22/05/2019 20.19, Aaro Koskinen wrote:
> Hi,
>
> On Wed, May 22, 2019 at 11:33:41AM +0200, Corentin Labbe wrote:
>> qemu-system-arm -M help |grep OMAP
>> cheetah Palm Tungsten|E aka. Cheetah PDA (OMAP310)
>> n800 Nokia N800 tablet aka. RX-34 (OMAP2420)
>> n810
Roman Kagan writes:
> I came across the following AB-BA deadlock:
>
> vCPU thread main thread
> --- ---
> async_safe_run_on_cpu(self,
> async_synic_update)
> ...
On 5/23/19 1:07 PM, Daniel P. Berrangé wrote:
> On Wed, May 22, 2019 at 10:42:27PM -0400, Richard Henderson wrote:
>> Since v4.0, capstone.h has moved to .
>
> NB this was a regression bug in capstone pkg-config file which has been
> fixed upstream
>
>https://github.com/aquynh/capstone/pull/1
On 5/23/19 4:42 AM, Richard Henderson wrote:
> Update to fbb20ea83c5a. Choose this over the 4.0.1 tag because
> master now includes the s390x z13 vector opcodes.
Cool! I was watching few fixed issues on the capstone repo, which are
now fixed in QEMU too :)
Various riscv/arm64 improvement too.
>
On 5/23/19 12:05 PM, Wim Vervoorn wrote:
> Hello Cédric,
>
> I have another question regarding the ASPEED Qemu support. This is regarding
> the SPI support.
>
> I noticed that in general the fmc_model and the spi_model for the flash device
> are different even though there is only one flash devi
Hi Jag and Elena,
Do you think a call would help to move discussion along more quickly?
We could use the next KVM Community Call on June 4th to discuss
remaining concerns and the next steps:
https://calendar.google.com/calendar/embed?src=dG9iMXRqcXAzN3Y4ZXZwNzRoMHE4a3BqcXNAZ3JvdXAuY2FsZW5kYXIuZ29v
On Wed, May 22, 2019 at 10:42:27PM -0400, Richard Henderson wrote:
> Since v4.0, capstone.h has moved to .
NB this was a regression bug in capstone pkg-config file which has been
fixed upstream
https://github.com/aquynh/capstone/pull/1276
In Fedora we pulled in the fix to our v4.0 builds and
On Wed, 22 May 2019 at 14:51, Markus Armbruster wrote:
>
> The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
> staging (2019-05-21 16:30:13 +0100)
>
> are available in the Git repository at:
On 5/23/19 4:42 AM, Richard Henderson wrote:
> Since v4.0, capstone.h has moved to .
>
> Signed-off-by: Richard Henderson
> ---
> include/disas/capstone.h | 4
> configure| 6 ++
> 2 files changed, 10 insertions(+)
>
> diff --git a/include/disas/capstone.h b/include/dis
David Hildenbrand writes:
> On 22.05.19 13:09, Richard Henderson wrote:
>> On 5/22/19 7:01 AM, David Hildenbrand wrote:
>>>
I also think that, if we create a bunch more of these wrappers:
> +DEF_VFAE_HELPER(8)
> +DEF_VFAE_HELPER(16)
> +DEF_VFAE_HELPER(32)
then RT
Assert that the cpu-exclusive sections are never entered/left with the
BQL taken.
Signed-off-by: Roman Kagan
---
cpus-common.c | 4
1 file changed, 4 insertions(+)
diff --git a/cpus-common.c b/cpus-common.c
index 023cfebfa3..9aa75fe1ba 100644
--- a/cpus-common.c
+++ b/cpus-common.c
@@ -174
Jon Doron writes:
> This patch series refactors the old gdbstub command packets handler
> with a new infrastructure which should ease extending and adding new
> and missing gdb command packets.
>
> version 10 changes:
> - Remove kvm added API as this is not really required and can be
> accomp
It was introduced in commit b129972c8b41e15b0521895a46fd9c752b68a5e,
with the following motivation:
Because start_exclusive uses CPU_FOREACH, merge exclusive_lock with
qemu_cpu_list_lock: together with a call to exclusive_idle (via
cpu_exec_start/end) in cpu_list_add, this protects exclusive
From: Richard Henderson
This provides the bootstrap and low level helper functions for an
alpha kernel. We use direct access to the DP264 serial port for
test output, and hard machine halt to exit the emulation.
Signed-off-by: Richard Henderson
Message-Id: <20190501184306.15208-1-richard.hende
On Tue, May 07, 2019 at 03:00:52PM -0400, Jag Raman wrote:
> Hi Stefan,
>
> Thank you very much for your feedback. Following is a summary of the
> discussions our team had regarding your feedback.
>
> On 4/25/2019 11:44 AM, Stefan Hajnoczi wrote:
> >
> > Can multiple LSI SCSI controllers be laun
I came across the following AB-BA deadlock:
vCPU thread main thread
--- ---
async_safe_run_on_cpu(self,
async_synic_update)
... [cpu hot-add]
process_queued
From: Thomas Huth
Currently, all tests are in the "auto" group. This is a little bit pointless.
OTOH, we need a group for the tests that we can automatically run during
"make check" each time, too. Tests in this new group are supposed to run
with every possible QEMU configuration, for example the
From: Gerd Hoffmann
Based on the ubuntu.docker file.
Used to reproduce the build failure Peter was seeing.
Others might find this useful too ;)
Signed-off-by: Gerd Hoffmann
Message-Id: <20190503070241.24786-1-kra...@redhat.com>
Signed-off-by: Alex Bennée
Tested-by: Philippe Mathieu-Daudé
Revi
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
tests/tcg/minilib/printf.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/tests/tcg/minilib/printf.c b/tests/tcg/minilib/printf.c
index 121620cb162..10472b4f585 100644
--- a/tests/tcg/minilib/printf.c
+++ b/tests/tcg/minilib/p
From: Thomas Huth
People often forget to run the iotests before submitting patches or
pull requests - this is likely due to the fact that we do not run the
tests during our mandatory "make check" tests yet. Now that we've got
a proper "auto" group of iotests that should be fine to run in every
en
Commit 337f2311f actually claimed to do this in the commit log but
didn't actually. Oops.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 155f066a206..40561993c40 100644
--- a/Ma
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
Makefile | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/Makefile b/Makefile
index 40561993c40..e8a886aac79 100644
--- a/Makefile
+++ b/Makefile
@@ -998,7 +998,9 @@ $(filter %.1 %.7 %.8,$(DOCS)): scripts/texi2po
Add support for generating a single targets coverage report. Execute:
make coverage-report
In the target build directory. This coverage report only cares about
target specific blobs so only searches the target build subdirectory.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
This attempts to clean-up the output to better match the output of the
rest of the QEMU check system when called with -makecheck. This includes:
- formatting as " TESTiotest-FMT: nnn"
- only dumping config on failure (when -makecheck enabled)
The non-make check output has been cleaned up
From: David Hildenbrand
Print the memory device info just like for PCDIMM/NVDIMM.
Reviewed-by: Dr. David Alan Gilbert
Signed-off-by: David Hildenbrand
---
hmp.c | 27 +++
1 file changed, 15 insertions(+), 12 deletions(-)
diff --git a/hmp.c b/hmp.c
index 92941142af..e1
We need a proxy device for virtio-pmem, and this device has to be the
actual memory device so we can cleanly hotplug it.
Forward memory device class functions either to the actual device or use
properties of the virtio-pmem device to implement these in the proxy.
virtio-pmem will only be compiled
Sync linux headers for virtio pmem.
Signed-off-by: Pankaj Gupta
---
include/standard-headers/linux/virtio_ids.h | 1 +
include/standard-headers/linux/virtio_pmem.h | 35
2 files changed, 36 insertions(+)
create mode 100644 include/standard-headers/linux/virtio_pme
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 6fd89b3d915..b053a836a32 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -284,5 +284,5 @@ matrix:
# Run check-tcg aga
Expand the memory test to cover move of the softmmu code. Specifically
we:
- improve commentary
- add some helpers (for later BE support)
- reduce boiler plate into helpers
- add signed reads at various sizes/offsets
- required -DCHECK_UNALIGNED
Signed-off-by: Alex Bennée
Reviewed-by:
There is nothing inherently architecture specific about the memory
test although we may have to manage different restrictions of
unaligned access across architectures.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
tests/tcg/{i386 => multiarch}/system/memory.c | 0
1 file changed
From: David Hildenbrand
Account the memory to node 0 for now. Once (if ever) virtio-pmem
supports NUMA, we can account it to the right node.
Signed-off-by: David Hildenbrand
---
numa.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/numa.c b/numa.
We can certainly support some common tests for system emulation that
make use of our minimal defined boot.S support. It will still be up to
individual architectures to ensure they build so we provide a
MULTIARCH_TESTS variable that they can tack onto TESTS themselves.
Signed-off-by: Alex Bennée
R
This cleans up a number of the block comments to fit the proper style.
While we are at it we also reference the official specification and
document what the return register value can be.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
---
target/arm/arm-semi.c | 40 ++
This is the implementation of virtio-pmem device. Support will require
machine changes for the architectures that will support it, so it will
not yet be compiled. It can be unlocked with VIRTIO_PMEM_SUPPORTED per
machine and disabled globally via VIRTIO_PMEM.
We cannot use the "addr" property as t
From: David Hildenbrand
Override the device hotplug handler to properly handle the memory device
part via virtio-pmem-pci callbacks from the machine hotplug handler and
forward to the actual PCI bus hotplug handler.
As PCI hotplug has not been properly factored out into hotplug handlers,
most ma
From: David Hildenbrand
Let's allow to specify additional interfaces for the base type (e.g.
later TYPE_MEMORY_DEVICE), something that was possible before the
rework of virtio PCI device instantiation.
Reviewed-by: Cornelia Huck
Signed-off-by: David Hildenbrand
---
hw/virtio/virtio-pci.c | 1
This provides two functions for handling console output that handle
the common backend behaviour for semihosting.
Signed-off-by: Alex Bennée
---
gdbstub.c| 5 +++
hw/semihosting/Makefile.objs | 1 +
hw/semihosting/console.c | 70 +
We are starting to add assembler foe tests/tcg so lets make sure we
get the mode right.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
.editorconfig | 5 +
1 file changed, 5 insertions(+)
diff --git a/.editorconfig b/.editorconfig
index 15828833938..df6db65531d 100644
--- a/
From: Philippe Mathieu-Daudé
Install optional dependencies of QEMU to get better coverage.
The following components are now enabled:
$ ./configure
...
Multipath support yes
VNC SASL support yes
RDMA support yes
PVRDMA supportyes
libiscsi support yes
seccomp support
The is_uhi gates all semihosting calls and always returns false for
CONFIG_USER_ONLY builds. There is no reason to build and link
mips-semi for these builds so lets fix that.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Aleksandar Markovic
---
target/mips/Makefil
Clean-up our unimplemented bits with a proper message.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
---
target/arm/arm-semi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/target/arm/arm-semi.c b/target/arm/arm-semi.c
index 253c66b172a..a3bbef18ef7 1
This is not really i386 only, we can have the same test for all
architectures supporting system tests.
Signed-off-by: Alex Bennée
Reviewed-by: Richard Henderson
---
tests/tcg/i386/Makefile.softmmu-target | 2 +-
tests/tcg/{i386 => multiarch}/system/hello.c | 0
2 files changed, 1 insertio
Seeing as I touched it I should at least keep an eye on it.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
---
MAINTAINERS | 7 +++
1 file changed, 7 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a6948ebc63b..c4f209898a9 100644
--- a/MAINTAINERS
+++ b/MAINTAINE
The documentation says the write should return the number of bytes not
written on an error (0 means everything was written). Read provides a
buffer length and the return value should be the buffer length - bytes
actually read. Remove the incorrect FIXME's and return the correct
values.
Signed-off-
It will be useful for a number of use-cases to be able to re-direct
output to a file like we do with serial output. This does the wiring
to allow us to treat then semihosting console like just another
character output device.
Signed-off-by: Alex Bennée
---
hw/semihosting/config.c | 26
Rather than printing directly to stdout lets use our common
semihosting code. There is one minor difference in that the output
currently defaults to stderr instead of stdout however this can be
controlled by connecting semihosting to a chardev.
Signed-off-by: Alex Bennée
Reviewed-by: Aleksandar M
Now we have a common semihosting console interface use that for our
string output. However ARM is currently unique in also supporting
semihosting for linux-user so we need to replicate the API in
linux-user. If other architectures gain this support we can move the
file later.
Signed-off-by: Alex B
This patch series has implementation for "virtio pmem"
device. "virtio pmem" is persistent memory(nvdimm) device in
guest which allows to bypass the guest page cache. This
also implements a VIRTIO based asynchronous flush mechanism.
Details of project idea for 'virtio pmem' flushing interfa
In preparation for having some more common semihosting code let's
excise the current config magic from vl.c into its own file. We shall
later add more conditionals to the build configurations so we can
avoid building this if we don't need it.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathi
This provides the bootstrap and low level helper functions for an
aarch64 kernel. We use semihosting to handle test output and exiting
the emulation. semihosting's parameter passing is a little funky so we
end up using the stack and pointing to that as the parameter block.
Signed-off-by: Alex Benn
Hi,
This is the current status of my testing/next tree. I had to delay
sending a PR as I refactored the semihosting changes (used by softmmu
tests) to be more generic. I've also addressed comments and merged in
Kevin's tweaks to the iotest check script.
The following patches still need review
There isn't much point building semihosting for platforms that don't
support it. Introduce a new symbol and enable it only for the softmmu
targets that need it.
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
---
default-configs/arm-softmmu.mak
* rkir--- via Qemu-devel (qemu-devel@nongnu.org) wrote:
> From: Roman Kiryanov
>
> VMSTATE_OPAQUE allows passing user defined functions to save
> and load vmstate for cases when data structures do not fit
> into int/struct/array terms.
>
> Signed-off-by: Roman Kiryanov
Hi Roman,
Thanks for t
On Wed, 22 May 2019 at 09:32, Gerd Hoffmann wrote:
>
> The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
> staging (2019-05-21 16:30:13 +0100)
>
> are available in the Git repository at:
>
>
Hello Cédric,
I have another question regarding the ASPEED Qemu support. This is regarding
the SPI support.
I noticed that in general the fmc_model and the spi_model for the flash device
are different even though there is only one flash device connected.
I would expect that in this case the mo
monitor_fdset_dup_fd_find_remove() and monitor_fdset_dup_fd_find()
return mon_fdset->id which is int64_t. Downcasting from int64_t to int
leads to a bug with removing fd from fdset with id >= 2^32.
So, fix return types for these function.
Signed-off-by: Yury Kotov
Reviewed-by: Markus Armbruster
On Tue, May 21, 2019 at 11:45:19AM +0300, Vladimir Sementsov-Ogievskiy wrote:
> Hi all!
>
> Here is idea of adding qiov_offset parameter to io path, to avoid
> a lot of places with same pattern of creating local_qiov or hd_qiov
> variables. Here is only read path for qcow2, if we like it, I'll
> m
On 5/23/19 1:07 AM, Eduardo Habkost wrote:
> On Wed, May 22, 2019 at 05:46:06PM -0400, Cleber Rosa wrote:
>> - Original Message -
>>> From: "Eduardo Habkost"
>>> On Tue, May 21, 2019 at 01:19:06AM +0200, Philippe Mathieu-Daudé wrote:
Hi,
It was a rainy week-end here, so I in
22.05.2019, 19:40, "Markus Armbruster" :
> Yury Kotov writes:
>
>> Now, fdset_id is int64, but in some places we work with it as int.
>> It seems that there is no sense to use int64 for fdset_id, so it's
>> better to fix inconsistency by changing fdset_id type to int and by
>> fixing the refer
On Tue, 21 May 2019 09:33:48 +0200
Laurent Vivier wrote:
> On pseries, core-ids are strongly binded to a node-id by the command
> line option. If an user tries to add a CPU to the wrong node, he has
> an error but it is not really helpful:
>
> qemu-system-ppc64 ... -smp 1,maxcpus=64,cores=1,th
On Wed, 22 May 2019 at 05:46, David Gibson wrote:
>
> The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
> staging (2019-05-21 16:30:13 +0100)
>
> are available in the Git repository at:
>
>
On 5/22/19 11:05 PM, Cleber Rosa wrote:
> - Original Message -
>> From: "Eduardo Habkost"
>> On Wed, Mar 13, 2019 at 12:45:41AM +0100, Philippe Mathieu-Daudé wrote:
>>> From: Philippe Mathieu-Daudé
>>>
>>> Similar to the x86_64/pc test, it boots a Linux kernel on a raspi2
>>> board and ve
On 22/05/2019 18:21, Chen-Yu Tsai wrote:
From: Chen-Yu Tsai
Since Linux 2.6 the stat syscalls have mostly supported nanosecond
components for each of the file-related timestamps.
QEMU user mode emulation currently does not pass through the nanosecond
portion of the timestamp, even when the hos
On Tue, 21 May 2019 at 19:51, Eduardo Habkost wrote:
>
> The following changes since commit a4f667b6714916683408b983cfe0a615a725775f:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20190521-3' into
> staging (2019-05-21 16:30:13 +0100)
>
> are available in the Git repository at:
>
On Thu, 23 May 2019 at 07:39, Markus Armbruster wrote:
>
> Peter Maydell writes:
> > It's a well-defined order, but it doesn't actually help in a
> > lot of cases, because often the thing you care about ordering
> > on is not a device or is not in the same tree as the thing
> > it depends on.
>
>
On Wed, 2019-05-15 at 13:54 +0200, Andrew Jones wrote:
> On Wed, May 15, 2019 at 12:52:29PM +0200, Igor Mammedov wrote:
> > since using magic numbers is not very descriptive
> > (but if there is some spec where they come from that we could point users to
> > it might be acceptable too, but I'd rese
On Thu, 23 May 2019 at 01:51, Laszlo Ersek wrote:
> I have narrowed down the issue sufficiently that I think I can hand it
> over to Peter and Ard now -- because they know AARCH32 and AARCH64
> assembly, and "target/arm/translate-a64.c" and "tcg/arm/*" too.
>
> The summarize the issue for Ard, the
301 - 400 of 416 matches
Mail list logo
