Hey Klaus,
Sorry for the late reply! I finally found this message amid the pile of
emails Qemu dumped on me.
I don't know what the right answer is here... NVMe is designed in a way
where you *do* "carve up" the flash into logical groupings and the nvme
firmware decides on how that's done.
Public bug reported:
We just ran into an issue with the Perl package on Debian/m68k when
being built with qemu-user [1].
The problem can be boiled down to qemu-user always reporting absolute
paths for the shell variable $0 no matter on how the command was
invoked.
A simple reproducer is this:
Ok, I'll add it to my to do list then
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1835827
Title:
HTIF symbols no longer recognized by RISC-V spike board
Status in QEMU:
New
Bug description:
Flow during _RESUMING device state:
- If Vendor driver defines mappable region, mmap migration region.
- Load config state.
- For data packet, till VFIO_MIG_FLAG_END_OF_STATE is not reached
- read data_size from packet, read buffer of data_size
- read data_offset from where QEMU should
Hook vfio_get_object callback for PCI devices.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
Suggested-by: Cornelia Huck
---
hw/vfio/pci.c | 8
include/hw/vfio/vfio-common.h | 1 +
2 files changed, 9 insertions(+)
diff --git a/hw/vfio/pci.c b/hw/vfio/pci.c
index
- Migration functions are implemented for VFIO_DEVICE_TYPE_PCI device in this
patch series.
- VFIO device supports migration or not is decided based of migration region
query. If migration region query is successful and migration region
initialization is successful then migration is
Public bug reported:
$ qemu-system-mips --version
QEMU emulator version 4.0.50 (v4.0.0-1975-gf34edbc760)
$ qemu-system-mips -machine malta -bios /dev/null -nodefaults -monitor stdio -S
(qemu) o 0xaf00 0
qemu-system-mips: hw/acpi/cpu.c:197: cpu_hotplug_hw_init: Assertion
On Thu, Jul 04, 2019 at 09:33:22AM +0200, Igor Mammedov wrote:
> On Wed, 3 Jul 2019 16:37:02 -0300
> Eduardo Habkost wrote:
> > [...]
> > > +TestData data = { .ram_size = 128 };
> > >
> > > -if (strcmp(arch, "aarch64") == 0) {
> > > -args = "-machine virt";
> > > +if
On 7/8/2019 9:20 PM, Eric Blake wrote:
On 7/7/19 9:29 AM, Tao Xu wrote:
In ACPI 6.3 chapter 5.2.27 Heterogeneous Memory Attribute Table (HMAT),
The initiator represents processor which access to memory. And in 5.2.27.3
Memory Proximity Domain Attributes Structure, the attached initiator is
On Fri, Jul 05, 2019 at 07:01:36PM +0800, Liu Yi L wrote:
> +void pci_setup_pasid_ops(PCIDevice *dev, PCIPASIDOps *ops)
> +{
> +assert(ops && !dev->pasid_ops);
> +dev->pasid_ops = ops;
> +}
> +
> +bool pci_device_is_ops_set(PCIBus *bus, int32_t devfn)
Name should be
On Fri, Jul 05, 2019 at 07:01:38PM +0800, Liu Yi L wrote:
> This patch adds vfio implementation PCIPASIDOps.alloc_pasid/free_pasid().
> These two functions are used to propagate guest pasid allocation and
> free requests to host via vfio container ioctl.
>
> Cc: Kevin Tian
> Cc: Jacob Pan
> Cc:
VM state change handler gets called on change in VM's state. This is used to set
VFIO device state to _RUNNING.
VM state change handler, migration state change handler and log_sync listener
are called asynchronously, which sometimes lead to data corruption in migration
region. Initialised mutex
This function is used in follwing patch in this series.
Migration region is mmaped when migration starts and will be unmapped when
migration is complete.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
---
hw/vfio/common.c | 20
hw/vfio/trace-events
On Thu, 2019-07-04 at 14:59 +1000, David Gibson wrote:
> On Thu, Jul 04, 2019 at 01:41:59PM +1000, Suraj Jitindar Singh wrote:
> > On Wed, 2019-07-03 at 16:12 +1000, David Gibson wrote:
> > > On Mon, Jul 01, 2019 at 04:19:46PM +1000, Suraj Jitindar Singh
> > > wrote:
> > > > The
On 7/8/2019 5:09 PM, Igor Mammedov wrote:
On Tue, 2 Jul 2019 16:50:24 +0800
Tao Xu wrote:
On 7/1/2019 7:25 PM, Igor Mammedov wrote:
On Fri, 14 Jun 2019 23:56:24 +0800
Tao Xu wrote:
...
@@ -2710,6 +2711,8 @@ void acpi_build(AcpiBuildTables *tables, MachineState
*machine)
On Fri, Jul 05, 2019 at 07:01:37PM +0800, Liu Yi L wrote:
> Intel VT-d 3.0 introduces scalable mode, and it has a bunch of
> capabilities related to scalable mode translation, thus there
> are multiple combinations. While this vIOMMU implementation
> wants simplify it for user by providing typical
On Fri, Jul 05, 2019 at 07:01:39PM +0800, Liu Yi L wrote:
> This patch adds virtual command support to Intel vIOMMU per Intel VT-d 3.1
> spec. This patch adds two virtual commands: alloc_pasid and free_pasid.
>
> Cc: Kevin Tian
> Cc: Jacob Pan
> Cc: Peter Xu
> Cc: Yi Sun
> Signed-off-by: Liu
On Fri, Jul 05, 2019 at 07:01:35PM +0800, Liu Yi L wrote:
> This patch imports the vIOMMU related definitions from kernel
> uapi/vfio.h. e.g. pasid allocation, guest pasid bind, guest pasid
> table bind and guest iommu cache invalidation.
>
> Cc: Kevin Tian
> Cc: Jacob Pan
> Cc: Peter Xu
> Cc:
- Defined MIGRATION region type and sub-type.
- Used 3 bits to define VFIO device states.
Bit 0 => _RUNNING
Bit 1 => _SAVING
Bit 2 => _RESUMING
Combination of these bits defines VFIO device's state during migration
_STOPPED => All bits 0 indicates VFIO device stopped.
Dirty page tracking (.log_sync) is part of RAM copying state, where
vendor driver provides the bitmap of pages which are dirtied by vendor
driver through migration region and as part of RAM copy, those pages
gets copied to file stream.
To get dirty page bitmap:
- write start address, page_size
Added .save_live_pending, .save_live_iterate and .save_live_complete_precopy
functions. These functions handles pre-copy and stop-and-copy phase.
In _SAVING|_RUNNING device state or pre-copy phase:
- read pending_bytes
- read data_offset - indicates kernel driver to write data to staging
buffer
Add migration support for VFIO device
This Patch set include patches as below:
- Define KABI for VFIO device for migration support.
- Added save and restore functions for PCI configuration space
- Generic migration functionality for VFIO device.
* This patch set adds functionality only for PCI
On Mon, Jun 24, 2019 at 01:22:07PM +0200, Markus Armbruster wrote:
> Daniel P. Berrangé writes:
>
> > On Wed, Jun 19, 2019 at 10:10:40PM +0200, Markus Armbruster wrote:
> >> Suggested-by: Paolo Bonzini
> >> Cc: Eduardo Habkost
> >> Cc: Marcel Apfelbaum
> >> Signed-off-by: Markus Armbruster
>
Define flags to be used as delimeter in migration file stream.
Added .save_setup and .save_cleanup functions. Mapped & unmapped migration
region from these functions at source during saving or pre-copy phase.
Set VFIO device state depending on VM's state. During live migration, VM is
running when
> On 8 Jul 2019, at 21:21, Jan Kiszka wrote:
>
> On 21.06.19 13:30, Paolo Bonzini wrote:
>> From: Liran Alon
>
> This broke bisection (which I currently have to do because this pull manages
> to
> lock up 5.1 host kernels): cpu_has_nested_virt will only come later in this
> series.
>
>
No, patch sign-off requires a legal name.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1835827
Title:
HTIF symbols no longer recognized by RISC-V spike board
Status in QEMU:
New
Bug
Patchew URL:
https://patchew.org/QEMU/1562637554-22439-1-git-send-email-kwankh...@nvidia.com/
Hi,
This series failed build test on s390x host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to
On Fri, Jul 5, 2019 at 6:43 AM Stefano Garzarella wrote:
>
> On Fri, Jul 05, 2019 at 11:58:43AM +0200, Max Reitz wrote:
> > On 05.07.19 11:32, Stefano Garzarella wrote:
> > > This patch allows 'qemu-img info' to show the 'disk size' for
> > > the RBD images that have the fast-diff feature
These functions save and restore PCI device specific data - config
space of PCI device.
Tested save and restore with MSI and MSIX type.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
---
hw/vfio/pci.c | 114 ++
Added migration state change notifier to get notification on migration state
change. These states are translated to VFIO device state and conveyed to vendor
driver.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
---
hw/vfio/migration.c | 54
Call vfio_migration_probe() and vfio_migration_finalize() functions for
vfio-pci device to enable migration for vfio PCI device.
Removed vfio_pci_vmstate structure.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
---
hw/vfio/pci.c | 15 +--
1 file changed, 9 insertions(+), 6
vfio_listerner_log_sync gets list of dirty pages from vendor driver and mark
those pages dirty when in _SAVING state.
Return early for the RAM block section of mapped MMIO region.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
---
hw/vfio/common.c | 35 +++
Patchew URL:
https://patchew.org/QEMU/1562637554-22439-1-git-send-email-kwankh...@nvidia.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Denverton-Server is the Atom Processor of Intel Harrisonville platform.
For more information:
https://ark.intel.com/content/www/us/en/ark/products/\
codename/63508/denverton.html
Signed-off-by: Tao Xu
---
target/i386/cpu.c | 45 +
1 file changed, 45
On Fri, Jul 05, 2019 at 07:01:42PM +0800, Liu Yi L wrote:
> +static bool vtd_process_pasid_desc(IntelIOMMUState *s,
> + VTDInvDesc *inv_desc)
> +{
> +if ((inv_desc->val[0] & VTD_INV_DESC_PASIDC_RSVD_VAL0) ||
> +(inv_desc->val[1] &
Daniel P. Berrangé writes:
> On Mon, Jul 08, 2019 at 12:27:12PM +0200, Philippe Mathieu-Daudé wrote:
[...]
>> Anyway, to stop bikeshedding this thread, can you add few lines about
>> why not use getenv() in the HACKING?
>
> I don't actually think the getenv thing is a security issue in any case.
Peter Maydell writes:
> On Sun, 7 Jul 2019 at 21:26, Stefan Weil wrote:
>> This is a general problem all over the QEMU code. I usually compile with
>> nearly all warnings enabled and get now lots of errors with the latest
>> code and after updating to gcc-8.3.0 (Debian buster). It should be
>>
Stefan Weil writes:
> Am 08.07.19 um 06:40 schrieb Markus Armbruster:
>
[...]
>> However, the gnu_ in gnu_scanf tells the compiler we're linking with the
>> GNU C Library, which seems unwise. Hmm, we already use gnu_printf.
>> Commit 9c9e7d51bf0:
>>
>> Newer gcc versions support format
From: Stefan Hajnoczi
Add an API for registering vm change state handlers with a well-defined
ordering. This is necessary when handlers depend on each other.
Small coding style fixes are included to make checkpatch.pl happy.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
The following changes since commit df34fe314b5da628bc9a2664fb1b887bc0a6cc6d:
Merge remote-tracking branch 'remotes/pmaydell/tags/pull-target-arm-20190708'
into staging (2019-07-08 14:23:32 +0100)
are available in the Git repository at:
git://repo.or.cz/qemu/kevin.git tags/for-upstream
The new facility is called "Vector-Packed-Decimal-Enhancement Facility"
and not "Vector BCD enhancements facility 1". Also fixup the short
name to "vxp" to match the Linux kernel.
Fixes: 54d65de0b525 ("s390x/cpumodel: vector enhancements")
Signed-off-by: Christian Borntraeger
---
On Mon, Jul 08, 2019 at 11:24:34AM +0400, Marc-André Lureau wrote:
> Hi,
>
> With external processes or helpers participating to the VM support, it
> becomes necessary to handle their migration. Various options exist to
> transfer their state:
> 1) as the VM memory, RAM or devices (we could say
* Marcel Apfelbaum (marcel.apfelb...@gmail.com) wrote:
>
>
> On 7/5/19 2:14 PM, Sukrit Bhatnagar wrote:
> > On Fri, 5 Jul 2019 at 16:29, Dmitry Fleytman
> > wrote:
> > >
> > > > On 5 Jul 2019, at 4:07, Marcel Apfelbaum
> > > > wrote:
> > > >
> > > > At some point vmxnet3 live migration
Patchew URL:
https://patchew.org/QEMU/20190708144013.83474-1-borntrae...@de.ibm.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190708144013.83474-1-borntrae...@de.ibm.com
Type: series
Subject: [Qemu-devel] [PATCH] s390:
Am 05.07.2019 um 17:28 hat Eric Blake geschrieben:
> Commit b76b4f60 allowed '-o compat=v3' as an alias for the
> less-appealing '-o compat=1.1' for 'qemu-img create' since we want to
> use the QMP form as much as possible, but forgot to do likewise for
> qemu-img amend. Also, it doesn't help
latest series posted:
https://lists.gnu.org/archive/html/qemu-devel/2018-11/msg00191.html
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1797262
Title:
qemu arm no longer able to boot RPI Kernels
On 08/07/2019 11:19, Daniel P. Berrangé wrote:
> On Mon, Jul 08, 2019 at 12:17:12PM +0200, Philippe Mathieu-Daudé wrote:
>> On 7/8/19 11:41 AM, Daniel P. Berrangé wrote:
>>> On Sat, Jul 06, 2019 at 09:35:30PM +0100, Peter Maydell wrote:
On Sat, 6 Jul 2019 at 11:28, Mark Cave-Ayland
Hi Philippe,
On [2019 Jul 08] Mon 16:58:29, Philippe Mathieu-Daudé wrote:
> Hi Francisco,
>
> On 7/8/19 4:26 PM, Francisco Iglesias wrote:
> > Hi Philippe,
> >
> > On [2019 Jul 08] Mon 12:47:50, Philippe Mathieu-Daudé wrote:
> >> Both lqspi_read() and lqspi_load_cache() expect a 32-bit
> >>
On 7/8/19 3:41 AM, Juan Quintela wrote:
> Marc-André Lureau wrote:
>> When instanciated, this object will connect to the given D-Bus
>> bus. During migration, it will take the data from org.qemu.VMState1
>> instances.
>>
>> See documentation for further details.
>>
>> Signed-off-by: Marc-André
Hi Bin,
Thanks for this patch.
I know I am very late to the game but I have a comment here.
On 17/05/2019 17:51, Bin Meng wrote:
> +/* create PLIC hart topology configuration string */
> +plic_hart_config_len = (strlen(SIFIVE_U_PLIC_HART_CONFIG) + 1) *
> smp_cpus;
> +
From: Philippe Mathieu-Daudé
The TPM Physical Presence Interface routines are only used
by the CRB/TIS interfaces. Do not compile this file if any
of them is built.
Signed-off-by: Philippe Mathieu-Daudé
Reviewed-by: Marc-André Lureau
Reviewed-by: Stefan Berger
Signed-off-by: Stefan Berger
The following changes since commit 506179e42112be77bfd071f050b15762d3b2cd43:
Merge remote-tracking branch 'remotes/dgibson/tags/ppc-for-4.1-20190702' into
staging (2019-07-02 18:56:44 +0100)
are available in the Git repository at:
git://github.com/stefanberger/qemu-tpm.git
On Mon, 7 Jan 2019 at 12:23, Marc-André Lureau
wrote:
>
> Generalize machine compatibility properties
>
> During "[PATCH v2 05/10] qom/globals: generalize
> object_property_set_globals()" review, Eduardo suggested to rework the
>
> On Jul 4, 2019, at 08:45, Philippe Mathieu-Daudé wrote:
>
> Cc'ing PPC/taihu_405ep and ARM/Digic4 maintainers.
>
> On 7/3/19 6:36 PM, Philippe Mathieu-Daudé wrote:
>> On 7/3/19 6:20 PM, Stephen Checkoway wrote:
On Jul 3, 2019, at 12:02, Philippe Mathieu-Daudé wrote:
On 7/3/19
This series might be helpful:
https://lists.gnu.org/archive/html/qemu-devel/2018-10/msg02067.html
** Tags added: linux-user
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1828723
Title:
[RFE]
On Mon, Jul 08, 2019 at 04:44:06PM +0100, Dr. David Alan Gilbert wrote:
> * Marc-André Lureau (marcandre.lur...@redhat.com) wrote:
> > Hi,
> >
> > With external processes or helpers participating to the VM support, it
> > becomes necessary to handle their migration. Various options exist to
> >
On 7/6/19 12:03 AM, Markus Armbruster wrote:
> John Snow writes:
>
>> On 7/5/19 10:14 AM, Markus Armbruster wrote:
>>> John Snow writes:
>>>
drive-backup and blockdev-backup have an awful lot of things in common
that are the same. Let's fix that.
I don't deduplicate
Modify the behaviour of qtest_quit() to check against the expected
exit status value. The default remains 0.
Signed-off-by: Marc-André Lureau
---
tests/libqtest.c | 41 ++---
tests/libqtest.h | 9 +
2 files changed, 31 insertions(+), 19 deletions(-)
When instanciated, this object will connect to the given D-Bus
bus. During migration, it will take the data from org.qemu.VMState1
instances.
See documentation for further details.
Signed-off-by: Marc-André Lureau
---
MAINTAINERS | 6 +
backends/Makefile.objs| 4 +
Hi,
With external processes or helpers participating to the VM support, it
becomes necessary to handle their migration. Various options exist to
transfer their state:
1) as the VM memory, RAM or devices (we could say that's how
vhost-user devices can be handled today, they are expected to
Move migration helpers for strings under include/, so they can be used
outside of migration/
Signed-off-by: Marc-André Lureau
---
include/migration/qemu-file-types.h | 4
migration/qemu-file.h | 4
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
So...this is not really a use-case per-say as it is actually a thing I
would like to do but can't at present...
Win 10 is lacking an ad2p sink and this means if I'm using it to play a
windows-only game and want to stream from e.g. my phone to my computer, I
can't (natively). Enter Linux, which
Marc-André Lureau wrote:
> Modify the behaviour of qtest_quit() to check against the expected
> exit status value. The default remains 0.
>
> Signed-off-by: Marc-André Lureau
Reviewed-by: Juan Quintela
But I would like a review from anyone from qtest.
On Jul 7, 2019 10:26 PM, "Stefan Weil" wrote:
>
> Am 13.08.18 um 19:52 schrieb Aleksandar Markovic:
>
>> From: Aleksandar Markovic
>>
>> Mark switch fallthroughs with comments, in cases fallthroughs
>> are intentional.
>
>
>
> This is a general problem all over the QEMU code. I usually compile
From: Shaju Abraham
During the IDE DMA transfer for a ISCSI target,when libiscsi encounters
a SENSE KEY error, it sets the task->sense to the value "COMMAND ABORTED".
The function iscsi_translate_sense() later translaters this error to -ECANCELED
and this value is passed to the callback
Patchew URL:
https://patchew.org/QEMU/20190708072437.3339-1-marcandre.lur...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
Marc-André Lureau wrote:
> Move migration helpers for strings under include/, so they can be used
> outside of migration/
>
> Signed-off-by: Marc-André Lureau
Reviewed-by: Juan Quintela
Not that I am the biggest fan of exporting it, but we don't have
anything better to offer.
On Fri, 2019-07-05 at 09:50 +0200, Kevin Wolf wrote:
> Am 04.07.2019 um 17:16 hat wangjie (P) geschrieben:
> > Hi, everybody：
> >
> > I developed a feature named "I/O hang"，my intention is to solve the problem
> > like that：
> > If the backend storage media of VM disk is far-end storage like
From: Philippe Mathieu-Daudé
In commit e9d652824b0 we extracted the vfp_set_fpscr_to_host()
function but failed at calling it in the correct place, we call
it after xregs[ARM_VFP_FPSCR] is modified.
Fix by calling this function before we update FPSCR.
Reported-by: Laurent Desnogues
In the virt machine, we support TrustZone being either present or
absent, and so the code must deal with the secure_sysmem pointer
possibly being NULL. In the sbsa-ref machine, TrustZone is always
present, but some code and comments copied from virt still treat
it as possibly not being present.
From: John Snow
Reported-by: radmehrsae...@gmail.com
Fixes: https://bugs.launchpad.net/bugs/1832914
Signed-off-by: John Snow
Reviewed-by: Maxim Levitsky
Reviewed-by: Eric Blake
Signed-off-by: Kevin Wolf
---
block/qcow.c | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git
Hi Francisco,
On 7/8/19 4:26 PM, Francisco Iglesias wrote:
> Hi Philippe,
>
> On [2019 Jul 08] Mon 12:47:50, Philippe Mathieu-Daudé wrote:
>> Both lqspi_read() and lqspi_load_cache() expect a 32-bit
>> aligned address.
>>
>> From UG1085 datasheet [*] Chapter 22: Quad-SPI Controller:
>
>
The new facility is called "Vector-Packed-Decimal-Enhancement Facility"
and not "Vector BCD enhancements facility 1". As the shortname might
have already found its way into some backports lets keep vxbeh.
Fixes: 54d65de0b525 ("s390x/cpumodel: vector enhancements")
Signed-off-by: Christian
Good morning to all,
I am currently working on using QEMU to run a BIOS my company has developed.
In order to see if the software was working correctly, I was able to
successfully run the edk2 bios using the following command:
qemu-system-x86_64.exe -bios
The fix for this bug is now in master and will be in QEMU 4.1.
** Changed in: qemu
Status: In Progress => Won't Fix
** Changed in: qemu
Status: Won't Fix => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
Improved diagnostic message is now in master and will be in QEMU 4.1.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1794187
Title:
* Marc-André Lureau (marcandre.lur...@redhat.com) wrote:
> Hi,
>
> With external processes or helpers participating to the VM support, it
> becomes necessary to handle their migration. Various options exist to
> transfer their state:
> 1) as the VM memory, RAM or devices (we could say that's how
From: Richard Henderson
Off by one error in the EL2 and EL3 tests. Remove the test
against EL3 entirely, since it must always be true.
Signed-off-by: Richard Henderson
Reviewed-by: Peter Maydell
Message-id: 20190702104732.31154-1-richard.hender...@linaro.org
Signed-off-by: Peter Maydell
---
-arm-20190708
for you to fetch changes up to 85795187f416326f87177cabc39fae1911f04c50:
target/arm/vfp_helper: Call set_fpscr_to_host before updating to FPSCR
(2019-07-08 14:11:31 +0100)
target-arm queue:
* tests/migration-test
On 7/7/19 9:29 AM, Tao Xu wrote:
> In ACPI 6.3 chapter 5.2.27 Heterogeneous Memory Attribute Table (HMAT),
> The initiator represents processor which access to memory. And in 5.2.27.3
> Memory Proximity Domain Attributes Structure, the attached initiator is
> defined as where the memory controller
Am 08.07.2019 um 14:54 schrieb Cornelia Huck:
> ...so that the compiler properly recognizes it.
>
> Reported-by: Stefan Weil
> Fixes: f180da83c039 ("s390x/tcg: Implement VECTOR LOAD LOGICAL ELEMENT AND
> ZERO")
> Signed-off-by: Cornelia Huck
> ---
> target/s390x/translate_vx.inc.c | 2 +-
> 1
On 7/5/19 5:14 PM, Eduardo Habkost wrote:
> Export machine type deprecation status through the query-machines
> QMP command. With this, libvirt and management software will be
> able to show this information to users and/or suggest changes to
> VM configuration to avoid deprecated machines.
>
>
0)
>
> are available in the Git repository at:
>
> https://git.linaro.org/people/pmaydell/qemu-arm.git
> tags/pull-target-arm-20190708
>
> for you to fetch changes up to 85795187f416326f87177cabc39fae1911f04c50:
>
> target/arm/vfp_helper: Call set
From: Stefan Hajnoczi
When the 'cont' command resumes guest execution the vm change state
handlers are invoked. Unfortunately there is no explicit ordering
between classic qemu_add_vm_change_state_handler() callbacks. When two
layers of code both use vm change state handlers, we don't control
Hi Philippe,
On [2019 Jul 08] Mon 12:47:50, Philippe Mathieu-Daudé wrote:
> Both lqspi_read() and lqspi_load_cache() expect a 32-bit
> aligned address.
>
> From UG1085 datasheet [*] Chapter 22: Quad-SPI Controller:
s/22/24/
After above change:
Reviewed-by: Francisco Iglesias
Tested-by:
As this might have already sneaked into some distribution backports just fixing
the
description would be a "play-safe" variant.
-DEF_FEAT(VECTOR_BCD_ENH, "vxbeh", STFL, 152, "Vector BCD enhancements facility
1")
+DEF_FEAT(VECTOR_BCD_ENH, "vxbeh", STFL, 152,
"Vector-Packed-Decimal-Enhancement
On Mon, 8 Jul 2019 at 15:18, Kevin Wolf wrote:
>
> The following changes since commit df34fe314b5da628bc9a2664fb1b887bc0a6cc6d:
>
> Merge remote-tracking branch
> 'remotes/pmaydell/tags/pull-target-arm-20190708' into staging (2019-07-08
> 14:23:32 +0100)
>
>
"Guest has not initialized display" simply means that the guest code
you're running has not done anything to the display device (VGA in this
case). There are two main reasons for this:
(1) the guest code isn't intended to output to the display -- perhaps
it sends its output to the serial port
On Mon, 8 Jul 2019 17:09:31 +0200
Christian Borntraeger wrote:
> The new facility is called "Vector-Packed-Decimal-Enhancement Facility"
> and not "Vector BCD enhancements facility 1". As the shortname might
> have already found its way into some backports lets keep vxbeh.
s/lets/let's/
>
>
The test aarch64 kernel is in an array defined with
unsigned char aarch64_kernel[] = { [...] }
which means it could be any size; currently it's quite small.
However we write it to a file using init_bootfile(), which
writes exactly 512 bytes to the file. This will break if
we ever end up with a
From: Jason Dillaman
Remove Josh as per his request since he is no longer the upstream RBD
tech lead. Add myself as the maintainer since I am the current RBD tech
lead.
Signed-off-by: Jason Dillaman
Reviewed-by: Josh Durgin
Signed-off-by: Kevin Wolf
---
MAINTAINERS | 2 +-
1 file changed, 1
From: Stefan Hajnoczi
Children sometimes depend on their parent's vm change state handler
having completed. Add a vm change state handler API for devices that
guarantees tree depth ordering.
Signed-off-by: Stefan Hajnoczi
Signed-off-by: Kevin Wolf
---
include/hw/qdev-core.h| 5
Patchew URL:
https://patchew.org/QEMU/20190708132237.7911-1-peter.mayd...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20190708132237.7911-1-peter.mayd...@linaro.org
Type: series
Subject: [Qemu-devel] [PULL 0/4]
Hi,
On Sat, Jul 6, 2019 at 12:40 AM Eduardo Habkost wrote:
>
> From: Like Xu
>
> The global smp variables in vl.c are completely replaced with machine
> properties.
>
> Form this commit, the smp_cpus/smp_cores/smp_threads/max_cpus are deprecated
> and only machine properties within
Public bug reported:
This is not necessarily a bug, however I wasn't sure were to get help.
I am currently working on using QEMU to run a BIOS my company has
developed. In order to see if the software was working correctly, I was
able to successfully run the edk2 bios using the following
On 08.07.19 14:54, Cornelia Huck wrote:
> According to the comment, the bits are supposed to accumulate.
>
> Reported-by: Stefan Weil
> Fixes: 5d1abf234462 ("s390x/pci: enforce zPCI state checking")
> Signed-off-by: Cornelia Huck
This patch does not change behaviour, so it is certainly not
On Fri, 5 Jul 2019 at 10:48, Paolo Bonzini wrote:
> You're right, the compatibility causes wrong behavior for the default
> -rtc settings (the RC pauses across migration). The right thing to do
> would be to store the base rather than the offset: that is, you store
> the time at which LR was
Am 05.07.2019 um 17:28 hat Eric Blake geschrieben:
> Commit b76b4f60 allowed '-o compat=v3' as an alias for the
> less-appealing '-o compat=1.1' for 'qemu-img create' since we want to
> use the QMP form as much as possible, but forgot to do likewise for
> qemu-img amend. Also, it doesn't help
From: Eric Blake
Commit b76b4f60 allowed '-o compat=v3' as an alias for the
less-appealing '-o compat=1.1' for 'qemu-img create' since we want to
use the QMP form as much as possible, but forgot to do likewise for
qemu-img amend. Also, it doesn't help that '-o help' doesn't list our
new
Changes now in master, will be in 4.1.
** Changed in: qemu
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1823998
Title:
qemu-system-aarch64: support
1 - 100 of 203 matches
Mail list logo
