> On Mar 12, 2019, at 18:03, Kevin Wolf wrote:
>
> Am 12.03.2019 um 03:18 hat Fam Zheng geschrieben:
>>> On Mar 11, 2019, at 19:06, Kevin Wolf wrote:
>>> Am 09.03.2019 um 02:46 hat Yaowei Bai geschrieben:
Thanks for explaining the background. It comes to my mind that actually we
Hi,
I sympathize with your situation, but the things on macOS seems a little
different.
The QEMU Cocoa UI starts in the `main` thread and detach a `qemu_main` thread
which runs stuff in vl.c etc. On the contrary, QEMU with gtk and other UIs just
scheduled its event loop in the qemu_main
On Tue, Mar 12, 2019 at 03:49:23PM -0700, Richard Henderson wrote:
> Within a delay slot, we were squishing both DISAS_IAQ_N_STALE and
> DISAS_IAQ_N_STALE_EXIT to DISAS_IAQ_N_UPDATED. This lost the
> required exit to the main loop, and could result in interrupts
> never being delivered.
>
>
On Tue, Mar 12, 2019 at 11:46:29AM +0100, Greg Kurz wrote:
> On Mon, 11 Mar 2019 19:57:09 -0300
> "Maxiwell S. Garcia" wrote:
>
> > This adds a handler for ibm,get-vpd RTAS calls, allowing pseries guest
> > to collect host information. It is disabled by default to avoid unwanted
> > information
On Tue, Mar 12, 2019 at 10:40:19AM +0100, Cédric Le Goater wrote:
> On 2/28/19 6:15 AM, David Gibson wrote:
> > On Fri, Feb 22, 2019 at 02:13:21PM +0100, Cédric Le Goater wrote:
> >> The interrupt mode is chosen by the CAS negotiation process and
> >> activated after a reset to take into account
Now we have two identical build_mcfg function.
Extract them to aml-build.c.
Signed-off-by: Wei Yang
---
hw/acpi/aml-build.c | 30 ++
hw/arm/virt-acpi-build.c| 16
hw/i386/acpi-build.c| 31 +--
mcfg_start points to the start of MCFG table and is used in
build_header. While this information could be derived from mcfg.
This patch removes the unnecessary variable mcfg_start.
Signed-off-by: Wei Yang
---
hw/arm/virt-acpi-build.c | 5 +
1 file changed, 1 insertion(+), 4 deletions(-)
On Tue, Mar 12, 2019 at 06:36:05PM +0100, Markus Armbruster wrote:
> Dear board code maintainers,
>
> This is a (rather late) follow-up to the last QEMU summit. Minutes[*]:
>
> * Deprecating unmaintained features (devices, targets, backends) in QEMU
>
>QEMU has a mechanism to deprecate
On Mon, Mar 11, 2019 at 09:59:32PM +0100, Cédric Le Goater wrote:
> On 2/26/19 5:17 AM, David Gibson wrote:
> > On Fri, Feb 22, 2019 at 02:13:22PM +0100, Cédric Le Goater wrote:
> >> Instead of switching off the sources, set their state to PENDING to
> >> possibly catch a hotplug event occuring
To build MCFG, two information is necessary:
* bus number
* base address
Abstract these two information to AcpiMcfgInfo so that build_mcfg and
build_mcfg_q35 will have the same declaration.
Signed-off-by: Wei Yang
---
hw/arm/virt-acpi-build.c| 28
This patch set tries to generalize MCFG table build process.
[1]: use acpi_get_mcfg() to get necessary information to build MCFG
[2]: remove an unnecessary variable mcfg_start
[3]: Extract build_mcfg to aml-build.c
Wei Yang (3):
hw/arm/virt-acpi-build: use acpi_get_mcfg() to calculate bus
On Fri, Mar 08, 2019 at 04:09:56PM -0300, Fabiano Rosas wrote:
> David Gibson writes:
>
> >> +/* Whether the KVM_SET_GUEST_DEBUG ioctl supports single stepping */
> >> +int kvm_has_guestdbg_singlestep(void)
> >> +{
> >> +/* return kvm_check_extension(kvm_state, KVM_CAP_GUEST_DEBUG_SSTEP);
>
On Sun, Mar 10, 2019 at 06:53:37PM +0100, Cédric Le Goater wrote:
> It includes better support for POWER9 processor and the QEMU platform.
> DD1.0 workarounds have been removed which simplifies a bit the XIVE
> PowerNV model.
>
> Built from submodule.
>
> Signed-off-by: Cédric Le Goater
> ---
>
On Tue, Mar 12, 2019 at 11:01:15AM -0400, Cleber Rosa wrote:
> On Sun, Mar 10, 2019 at 07:27:00PM +1100, David Gibson wrote:
> > From: Cédric Le Goater
> >
> > We now have enough support to boot a PowerNV machine with a POWER9
> > processor. Allow HV mode on POWER9.
> >
> > Signed-off-by:
176dccee "target/ppc/spapr: Clear partition table entry when allocating
hash table" reworked the H_REGISTER_PROCESS_TABLE hypercall, but
unfortunately due to a small error no longer correctly sets the LPCR[GTSE]
bit which allows the guest to directly execute (some types of) tlbie (TLB
flush)
On Wed, Mar 13, 2019 at 01:32:00PM +1100, David Gibson wrote:
> On Tue, Mar 12, 2019 at 11:01:15AM -0400, Cleber Rosa wrote:
> > On Sun, Mar 10, 2019 at 07:27:00PM +1100, David Gibson wrote:
> > > From: Cédric Le Goater
> > >
> > > We now have enough support to boot a PowerNV machine with a
On Wed, 13 Mar 2019 at 09:08, Michael S. Tsirkin wrote:
>
> On Thu, Feb 28, 2019 at 04:53:48PM +0800, elohi...@gmail.com wrote:
> > From: Xie Yongji
> >
> > This patchset is aimed at supporting qemu to reconnect
> > vhost-user-blk backend after vhost-user-blk backend crash or
> > restart.
> >
>
Add "Reviewed-by" from Richard because Richard has reviewed it in patch v2[1],
thanks.
Reviewed-by: Richard Henderson
[1]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg604509.html
On 2019/3/12 20:52, Dongjiu Geng wrote:
> Some generic arch timer registers are Config-RW in the EL0,
>
On 2019/3/12 23:02, Richard Henderson wrote:
>> [INFO ]@(dump_registers:68): X6=0020 X7=0c00b030
>> ---
>> target/arm/helper.c | 30 +++---
>> 1 file changed, 15 insertions(+), 15 deletions(-)
> Reviewed-by: Richard Henderson
Thanks for this
The following changes since commit 9d867123659ac32edd2a0b64cabe2dca544f1d0e:
Merge remote-tracking branch 'remotes/ehabkost/tags/python-next-pull-request'
into staging (2019-03-12 18:31:56 +)
are available in the Git repository at:
git://git.kernel.org/pub/scm/virt/kvm/mst/qemu.git
From: "Liu, Yi L"
Per Intel(R) VT-d 3.0, the qi_desc is 256 bits in Scalable
Mode. This patch adds emulation of 256bits qi_desc.
Signed-off-by: Liu, Yi L
[Yi Sun is co-developer to rebase and refine the patch.]
Signed-off-by: Yi Sun
Reviewed-by: Peter Xu
Message-Id:
From: Wei Yang
At the beginning or nvdimm_build_common_dsm(), variable *function* is
already allocated for Arg2.
This patch reuse variable *function* instead of allocating it again.
Signed-off-by: Wei Yang
Message-Id: <20190227075101.6263-3-richardw.y...@linux.intel.com>
Reviewed-by: Michael
On Wed, 13 Mar 2019 at 09:16, Michael S. Tsirkin wrote:
>
> On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > From: Xie Yongji
> >
> > Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> > and VHOST_USER_SET_INFLIGHT_FD. The backend is able to restart
> > safely
From: Yi Sun
This patch adds an option to provide flexibility for user to expose
Scalable Mode to guest. User could expose Scalable Mode to guest by
the config as below:
"-device intel-iommu,caching-mode=on,scalable-mode=on"
The Linux iommu driver has supported scalable mode. Please refer
From: Wei Yang
The IO range is defined to 4 bytes with NVDIMM_ACPI_IO_LEN, so it is
more proper to use this macro instead of calculating it by sizeof.
Signed-off-by: Wei Yang
Message-Id: <20190227075101.6263-4-richardw.y...@linux.intel.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by:
From: Knut Omang
Claim ACS support in the generic PCIe root port to allow
passthrough of individual functions of a device to different
guests (in a nested virt.setting) with VFIO.
Without this patch, all functions of a device, such as all VFs of
an SR/IOV device, will end up in the same IOMMU
From: "Liu, Yi L"
Intel(R) VT-d 3.0 spec introduces scalable mode address translation to
replace extended context mode. This patch extends current emulator to
support Scalable Mode which includes root table, context table and new
pasid table format change. Now intel_iommu emulates both legacy
From: Wei Yang
>From dsm_dma_arrea to dsm_dma_area.
Signed-off-by: Wei Yang
Message-Id: <20190227075101.6263-2-richardw.y...@linux.intel.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
Reviewed-by: Igor Mammedov
---
hw/acpi/nvdimm.c | 4 ++--
1 file changed, 2
From: Xie Yongji
The vu_check_queue_msg_file() has checked the FD flag. So let's
delete the redundant check after it.
Signed-off-by: Xie Yongji
Signed-off-by: Zhang Yu
Message-Id: <20190228085355.9614-3-xieyon...@baidu.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
From: Xie Yongji
This patch adds support for VHOST_USER_GET_INFLIGHT_FD and
VHOST_USER_SET_INFLIGHT_FD message to set/get shared buffer
to/from qemu. Then backend can track inflight I/O in this buffer.
Signed-off-by: Xie Yongji
Signed-off-by: Zhang Yu
Message-Id:
From: Wei Yang
Currently we do device realization like below:
hotplug_handler_pre_plug()
dc->realize()
hotplug_handler_plug()
Before we do device realization and plug, we should allocate necessary
resources and check if memory-hotplug-support property is enabled.
At the piix4 and
From: Xie Yongji
Introduce vu_queue_map_desc() which should be
independent with vu_queue_pop();
Signed-off-by: Xie Yongji
Signed-off-by: Zhang Yu
Reviewed-by: Marc-André Lureau
Message-Id: <20190228085355.9614-4-xieyon...@baidu.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S.
From: Xie Yongji
This patch adds support for vhost-user-blk device to get/set
inflight buffer from/to backend.
Signed-off-by: Xie Yongji
Signed-off-by: Zhang Yu
Message-Id: <20190228085355.9614-6-xieyon...@baidu.com>
Reviewed-by: Michael S. Tsirkin
Signed-off-by: Michael S. Tsirkin
---
From: Knut Omang
Implementing an ACS capability on downstream ports and multifunction
endpoints indicates isolation and IOMMU visibility to a finer
granularity. This creates smaller IOMMU groups in the guest and thus
more flexibility in assigning endpoints to guest userspace or an L2
guest.
From: Xie Yongji
This patch introduces two new messages VHOST_USER_GET_INFLIGHT_FD
and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared
buffer between qemu and backend.
Firstly, qemu uses VHOST_USER_GET_INFLIGHT_FD to get the
shared buffer from backend. Then qemu should send it back
On Fri, Mar 08, 2019 at 03:04:48PM +0100, Marc-André Lureau wrote:
> Create a vhost-user-backend object that holds a connection to a
> vhost-user backend and can be referenced from virtio devices that
> support it. See later patches for input & gpu usage.
>
> Signed-off-by: Marc-André Lureau
>
On Tue, Mar 12, 2019 at 11:15 AM Jason Andryuk wrote:
> I'll test to verify whether MSI-X works with
> permissive mode.
Dropping this patch and enabling permissive mode allowed MSI-X to work.
{"execute": "device_add", "arguments": {"driver":
"xen-pci-passthrough", "id":
On Wed, 13 Mar 2019 at 00:49, Michael S. Tsirkin wrote:
>
> On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> > From: Xie Yongji
> >
> > Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> > and VHOST_USER_SET_INFLIGHT_FD. The backend is able to restart
> > safely
Dear all,
Really appreciate your comments and information. For "Live Physical Time", is
there any document to tell the whole story? And may I know the timeline to make it happen?
Thanks,
Heyi
On 2019/3/12 22:12, Marc Zyngier wrote:
Hi Peter,
On 12/03/2019 10:08, Peter Maydell wrote:
On
Hi Lukas,
On Tue, Mar 12, 2019 at 10:39 PM Auer, Lukas
wrote:
>
> Hi Bin,
>
> On Mon, 2019-03-11 at 23:28 +0800, Bin Meng wrote:
> > Hi Lukas,
> >
> > On Mon, Mar 11, 2019 at 2:03 AM Auer, Lukas
> > wrote:
> > > Hi Bin,
> > >
> > > On Sun, 2019-03-10 at 22:57 +0800, Bin Meng wrote:
> > > > Hi
Hi Richard,
On 2019/3/12 22:59, Richard Henderson wrote:
On 3/12/19 12:57 AM, Heyi Guo wrote:
int kvm_arm_vcpu_init(CPUState *cs)
{
ARMCPU *cpu = ARM_CPU(cs);
struct kvm_vcpu_init init;
+/*
+ * Only add change state handler for arch timer once, for KVM will help
On Fri, Feb 15, 2019 at 10:32:37AM +, Daniel P. Berrangé wrote:
> Changed in v2:
>
> - Fix properties set for v2.6 machine type compat so that it
>only affects the virtio devices which support both legacy
>and modern modes.
> - Revert unneccessary patch allowing optional properties
hi Alex
Any comments to the sequence below?
Actaully we have some concerns and suggestions to userspace-opaque migration
data.
1. if data is opaque to userspace, kernel interface must be tightly bound to
migration.
e.g. vendor driver has to know state (running + not logging) should not
On Thu, Feb 28, 2019 at 04:53:54PM +0800, elohi...@gmail.com wrote:
> From: Xie Yongji
>
> Since we now support the message VHOST_USER_GET_INFLIGHT_FD
> and VHOST_USER_SET_INFLIGHT_FD. The backend is able to restart
> safely because it can track inflight I/O in shared memory.
> This patch allows
On Thu, Feb 28, 2019 at 04:53:48PM +0800, elohi...@gmail.com wrote:
> From: Xie Yongji
>
> This patchset is aimed at supporting qemu to reconnect
> vhost-user-blk backend after vhost-user-blk backend crash or
> restart.
>
> The patch 1 introduces two new messages VHOST_USER_GET_INFLIGHT_FD
>
'
On Tue, Mar 12, 2019 at 6:44 PM Markus Armbruster wrote:
>
> Dear board code maintainers,
>
> This is a (rather late) follow-up to the last QEMU summit. Minutes[*]:
>
> * Deprecating unmaintained features (devices, targets, backends) in QEMU
>
>QEMU has a mechanism to deprecate features
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 verify the serial is working.
>
> If ARM is a target being built, "make check-acceptance" will
>
On Wed, Mar 13, 2019 at 12:45:40AM +0100, Philippe Mathieu-Daudé wrote:
> Debian binary package format supports various compressions.
>
> Per man deb(5):
>
> NAME
> deb - Debian binary package format
>
> FORMAT
> ...
> The third, last required member is named data.tar. It
On Wed, Mar 13, 2019 at 10:25:27AM +1100, David Gibson wrote:
> On Tue, Mar 12, 2019 at 09:46:14PM +0100, Cédric Le Goater wrote:
> > On 3/12/19 6:18 PM, Cleber Rosa wrote:
> > > Because of the changes in da874d90a, the Fedora 29 kernel doesn't
> > > boot with the modified version of the Power9
On Tue, Mar 12, 2019 at 07:20:22PM +, Alex Bennée wrote:
>
> David Gibson writes:
>
> > On Mon, Mar 11, 2019 at 10:40:54AM +, Alex Bennée wrote:
> >>
[snip]
> >> > MALLOC_PERTURB_=${MALLOC_PERTURB_:-$(( ${RANDOM:-0} % 255 + 1))}
> >> > QTEST_QEMU_BINARY=ppc64-softmmu/qemu-system-ppc64
Add the raspi2 to the list of boards tested by the
boot_linux_console Avocado test.
Based on "Acceptance Tests: target architecture support" v5:
https://lists.gnu.org/archive/html/qemu-devel/2019-03/msg04111.html
Based-on: <20190312171824.5134-1-cr...@redhat.com>
Philippe Mathieu-Daudé (2):
On Tue, Mar 12, 2019 at 03:26:27PM +0100, Greg Kurz wrote:
> On Tue, 12 Mar 2019 15:32:51 +0530
> Aravinda Prasad wrote:
>
> > This patch set adds support for FWNMI in PowerKVM guests.
> >
> > System errors such as SLB multihit and memory errors
> > that cannot be corrected by hardware is
Debian binary package format supports various compressions.
Per man deb(5):
NAME
deb - Debian binary package format
FORMAT
...
The third, last required member is named data.tar. It contains the
filesystem as a tar archive, either not compressed (supported since
dpkg
On Tue, Mar 12, 2019 at 09:46:14PM +0100, Cédric Le Goater wrote:
> On 3/12/19 6:18 PM, Cleber Rosa wrote:
> > Because of the changes in da874d90a, the Fedora 29 kernel doesn't
> > boot with the modified version of the Power9 CPU. Let's set the
> > power8 CPU instead.
> >
> > Signed-off-by:
On Tue, Mar 12, 2019 at 01:18:20PM -0400, Cleber Rosa wrote:
> Because of the changes in da874d90a, the Fedora 29 kernel doesn't
> boot with the modified version of the Power9 CPU. Let's set the
> power8 CPU instead.
>
> Signed-off-by: Cleber Rosa
> CC: Cédric Le Goater
> CC: David Gibson
From: Philippe Mathieu-Daudé
Similar to the x86_64/pc test, it boots a Linux kernel on a raspi2
board and verify the serial is working.
If ARM is a target being built, "make check-acceptance" will
automatically include this test by the use of the "arch:arm" tags.
Alternatively, this test can
Daniel P. Berrangé writes:
...
> +
> +int
> +qemu_file_monitor_add_watch(QFileMonitor *mon,
> +const char *dirpath,
> +const char *filename,
> +QFileMonitorHandler cb,
> +void *opaque,
On 3/12/19 4:33 PM, Laszlo Ersek wrote:
> On 03/10/19 12:21, Philippe Mathieu-Daudé wrote:
>> On 3/10/19 4:56 AM, Michael S. Tsirkin wrote:
>>> On Sat, Mar 09, 2019 at 01:48:16AM +0100, Laszlo Ersek wrote:
Repo: https://github.com/lersek/qemu.git
Branch: edk2_build
This
On 3/9/19 1:48 AM, Laszlo Ersek wrote:
> The edk2-stabe201903 release introduced Python3 support to edk2's
> BaseTools; however the Python3 enablement breaks in a corner case (which
> is nevertheless supported by the edk2 community), namely the in-module
> parallelization that we utilize.
>
>
On 3/13/19 1:08 AM, Pintu Agarwal wrote:
> On Tue, Mar 12, 2019 at 7:41 PM Suzuki K Poulose
> wrote:
>>
>>
>>
>> On 12/03/2019 14:02, Pintu Agarwal wrote:
-netdev user,id=unet,hostfwd=tcp::-:22 \
-net user \
and you 'll get guest's port 22 to be forwarded to hosts
On Wed, 13 Mar 2019, at 07:07, Cédric Le Goater wrote:
> On 3/12/19 6:36 PM, Markus Armbruster wrote:
> > Dear board code maintainers,
> >
> > This is a (rather late) follow-up to the last QEMU summit. Minutes[*]:
> >
> > * Deprecating unmaintained features (devices, targets, backends) in
The Edk2Crypto object is used to hold configuration values specific
to EDK2.
The edk2_add_host_crypto_policy() function loads crypto policies
from the host, and register them as fw_cfg named file items.
So far only the 'https' policy is supported.
A usercase example is the 'HTTPS Boof' feature
Add a function to read the full content of file on the host, and add
a new 'file' name item to the fw_cfg device.
Signed-off-by: Philippe Mathieu-Daudé
---
v2: s/ptr/data, corrected documentation (Laszlo)
v3: inverted the if() logic
v4: does not return pointer to alloc'd data (Markus)
---
Hi,
This series consists of:
- add fw_cfg_add_file_from_host()
- add edk2_add_host_crypto_policy() and the Edk2Crypto object
The Edk2Crypto object is used to hold configuration values specific
to EDK2.
The edk2_add_host_crypto_policy() function loads crypto policies
from the host, and register
Enable the EDK2 Crypto Policy features on the Virt machine.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/arm/virt.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/arm/virt.c b/hw/arm/virt.c
index ce2664a30b..927d4ff31a 100644
--- a/hw/arm/virt.c
+++ b/hw/arm/virt.c
@@ -56,6 +56,7
Enable the EDK2 Crypto Policy features on the PC machine.
Signed-off-by: Philippe Mathieu-Daudé
---
hw/i386/pc.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/hw/i386/pc.c b/hw/i386/pc.c
index 1cdaff5f4d..f0bef84ccf 100644
--- a/hw/i386/pc.c
+++ b/hw/i386/pc.c
@@ -38,6 +38,7 @@
Within a delay slot, we were squishing both DISAS_IAQ_N_STALE and
DISAS_IAQ_N_STALE_EXIT to DISAS_IAQ_N_UPDATED. This lost the
required exit to the main loop, and could result in interrupts
never being delivered.
Reported-by: Sven Schnelle
Signed-off-by: Richard Henderson
---
Sven, this
On Mon, Mar 11, 2019 at 7:27 PM Philippe Mathieu-Daudé
wrote:
> On 3/11/19 8:26 AM, Markus Armbruster wrote:
> > Philippe Mathieu-Daudé writes:
> >
> >> The Edk2Crypto object is used to hold configuration values specific
> >> to EDK2.
> >>
> >> The edk2_add_host_crypto_policy() function loads
2019/3/12 22:56, Eric Blake:
> On 3/12/19 4:39 PM, Unai Martinez Corral wrote:
> > 2019/3/12, Eric Blake:
> >>
> >> On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
> >>> This patch breaks backward compatibility.
> >>
> >> Is it worth a mention why we don't consider backwards-compatibility for
>
Alex Bennée, le mar. 12 mars 2019 19:34:56 +, a ecrit:
> I know Richard's is right because I asked him in the pub. I'm guessing
> Fredrik's based on the fact I vaguely remember an Atari demo. The
> others I attributed to academic institutions last time I posted so
> have moved them to
2019/3/12 22:13, Eric Blake:
> On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
> > @@ -186,9 +186,11 @@ Usage: qemu-binfmt-conf.sh [--qemu-path
> > PATH][--debian][--systemd CPU]
> >(default: $SYSTEMDDIR or $DEBIANDIR)
>
> Remember, this is in an unquoted heredoc, so it
On 3/12/19 4:39 PM, Unai Martinez Corral wrote:
> 2019/3/12, Eric Blake:
>>
>> On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
>>> This patch breaks backward compatibility.
>>>
>>
>> Is it worth a mention why we don't consider backwards-compatibility for
>> this script to be very important?
>
>
2019/3/12, Eric Blake:
>
> On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
> > This patch breaks backward compatibility.
> >
>
> Is it worth a mention why we don't consider backwards-compatibility for
> this script to be very important?
'persistent' is a quite recent feature (8 monts) which seems
This bug is invalid. MSI/MSI-X interrupts are properly serviced when
dataplane batching is used. The original problem was in the incorrect
virtio driver initialization sequence (virtqueues and MSI-X interrupts
configured after DRIVER_OK bit is set).
This bug can be closed as INVALID.
--
You
On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
> Allow to set options '--persistent' and/or '--credential' through
> environment variables. If not defined, defaults are used ('no').
> Anyway, command-line arguments have priority over environment variables.
>
> Signed-off-by: Unai Martinez-Corral
On 3/12/19 4:15 PM, Laszlo Ersek wrote:
> On 03/11/19 13:09, Eric Blake wrote:
>> On 3/10/19 10:10 AM, Philippe Mathieu-Daudé wrote:
>>> Hi Laszlo,
>>>
>>> On 3/9/19 5:48 PM, Philippe Mathieu-Daudé wrote:
On 3/9/19 1:48 AM, Laszlo Ersek wrote:
> Add the "efi" target to "Makefile".
>
On 3/12/19 2:51 PM, Unai Martinez-Corral wrote:
> This patch breaks backward compatibility.
>
Is it worth a mention why we don't consider backwards-compatibility for
this script to be very important?
> Both '--persistent' and '--credential' default to 'no'. Hence, '-p no'
> or '-c no' are
On Tue, 12 Mar 2019 at 02:17, Eduardo Habkost wrote:
>
> The following changes since commit 336cfef495f0cd5b1606251c52628d0372e9a809:
>
> Makefile: Don't install non-sphinx files in sphinx docs install (2019-03-11
> 11:10:44 +)
>
> are available in the Git repository at:
>
>
On Tue, 12 Mar 2019 at 19:23, Alex Bennée wrote:
> Someone applying for one of the outreach projects mentioned another
> attack vector "side-channel leakages in qemu translation from ARM to
> x86" to which I replied the same "not a security boundary" response. But
> I guess there are some papers
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
On Tue, 12 Mar 2019 at 19:00, Bandan Das wrote:
>
>
> Spotted by Coverity: CID 1399414
>
> mtp delete allows the return status of delete succeeded,
> partial_delete or readonly - when none of the objects could be
> deleted. Give more meaningful names to return values of the
> delete function.
>
>
On 12.03.19 18:36, Markus Armbruster wrote:
> Make sure to include a complete QEMU command line:
> ...
> = hw/hppa/machine.c =
> Richard Henderson (maintainer:HPPA (PA-RISC))
> Helge Deller (reviewer:Dino)
Linux:
Download http://backup.parisc-linux.org/qemu/debian-10-hdd-img.tar.bz2
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
On 3/12/19 2:31 PM, Kevin Wolf wrote:
>> ...but patch itself is correct. Not worth a v2 pull request, since it is
>> not user-visible.
>
> I just updated the tag without sending a formal v2, so Peter will pull
> the corrected version.
Only works insofar that we currently only require pull
On 3/12/19 6:18 PM, Cleber Rosa wrote:
> Because of the changes in da874d90a, the Fedora 29 kernel doesn't
> boot with the modified version of the Power9 CPU. Let's set the
> power8 CPU instead.
>
> Signed-off-by: Cleber Rosa
> CC: Cédric Le Goater
> CC: David Gibson
Looks fine to me as
Patchew URL: https://patchew.org/QEMU/jpgsgvsc5ls@linux.bootlegged.copy/
Hi,
This series failed the docker-mingw@fedora 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 ===
On 12/03/2019 21:25, Unai Martinez Corral wrote:
I could not see the indentation problems you mentioned before. Hope it
is fixed in v7 anyway.
It seemed in the code I've reviewed, but not in my reply...
I will fix manually before the pull request if needed.
Thanks,
Laurent
El mar., 12 mar.
On 3/12/19 6:36 PM, Markus Armbruster wrote:
> Dear board code maintainers,
>
> This is a (rather late) follow-up to the last QEMU summit. Minutes[*]:
>
> * Deprecating unmaintained features (devices, targets, backends) in QEMU
>
>QEMU has a mechanism to deprecate features but there
From: Vladimir Sementsov-Ogievskiy
We already use (we didn't notice it) IN_USE flag for marking bitmap
metadata outdated, such as AUTO flag, which mirrors enabled/disabled
bitmaps. Now we are going to support bitmap resize, so it's good to
write IN_USE meaning with more details.
Signed-off-by:
2019/3/12 21:03, Laurent Vivier:
> QEMU_PATH appears to be an Env-Variable whereas it is not. But we need
> to define it because we want to display its default value. And it is
> changed into an env-variable in PATCH 6/9... so I think it's acceptable
> as is.
Yes, you are correct. This is because
I could not see the indentation problems you mentioned before. Hope it
is fixed in v7 anyway.
El mar., 12 mar. 2019 a las 20:56, Laurent Vivier
() escribió:
>
> On 12/03/2019 20:54, Unai Martinez-Corral wrote:
> > This is a partial implementation.
> >
> > Allows to remove a single or a list of
drive and blockdev backup cannot use readonly bitmaps, because the
sync=incremental mechanism actually edits the bitmaps on success.
If you really want to do this operation, use a copied bitmap.
Signed-off-by: John Snow
Reviewed-by: Eric Blake
Reviewed-by: Vladimir Sementsov-Ogievskiy
From: Vladimir Sementsov-Ogievskiy
We are going to allow image resize when there are persistent bitmaps.
It may lead to appearing of inconsistent bitmaps (IN_USE=1) with
inconsistent size. But we still want to load them as inconsistent.
Signed-off-by: Vladimir Sementsov-Ogievskiy
Message-id:
Patchew URL: https://patchew.org/QEMU/20190312195009.GA6@99bbefa4bcea/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Message-id: 20190312195009.GA6@99bbefa4bcea
Subject: [Qemu-devel] [PATCH v7 0/9] qemu-binfmt-conf.sh
=== TEST
This adds a simple test that ensures the busy bit works for push backups,
as well as doubling as bonus test for incremental backups that get interrupted
by EIO errors.
Recording bit tests are already handled sufficiently by 236.
Signed-off-by: John Snow
Reviewed-by: Eric Blake
Tested-by: Eric
Test that we can actually resize qcow2 images with persistent bitmaps
correctly. Throw some other goofy stuff at the test while we're at it,
like adding bitmaps of different granularities and at different times.
Signed-off-by: John Snow
Signed-off-by: Vladimir Sementsov-Ogievskiy
Tested-by:
From: Eric Blake
Commit a88b179f introduced the ability to set and query bitmap
persistence, but with an atypical spelling.
Signed-off-by: Eric Blake
Message-id: 20190308205845.25734-1-ebl...@redhat.com
Signed-off-by: John Snow
---
include/block/dirty-bitmap.h | 4 ++--
1 - 100 of 692 matches
Mail list logo
