On 03/09/2019 17:28, Kevin Wolf wrote:
> Am 03.09.2019 um 16:22 hat Andrey Shinkevich geschrieben:
>>
>>
>> On 03/09/2019 13:02, Kevin Wolf wrote:
>>> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
In the current implementation of the QEMU bash iotests, only qemu-io
processes
Am 03.09.2019 um 16:22 hat Andrey Shinkevich geschrieben:
>
>
> On 03/09/2019 13:02, Kevin Wolf wrote:
> > Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
> >> In the current implementation of the QEMU bash iotests, only qemu-io
> >> processes may be run under the Valgrind with the swit
On 03/09/2019 13:02, Kevin Wolf wrote:
> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
>> In the current implementation of the QEMU bash iotests, only qemu-io
>> processes may be run under the Valgrind with the switch '-valgrind'.
>> Let's allow the common.rc bash script running all o
On 03/09/2019 13:02, Kevin Wolf wrote:
> Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
>> In the current implementation of the QEMU bash iotests, only qemu-io
>> processes may be run under the Valgrind with the switch '-valgrind'.
>> Let's allow the common.rc bash script running all o
Am 01.09.2019 um 13:53 hat Andrey Shinkevich geschrieben:
> In the current implementation of the QEMU bash iotests, only qemu-io
> processes may be run under the Valgrind with the switch '-valgrind'.
> Let's allow the common.rc bash script running all other QEMU processes,
> such as qemu-kvm, qemu-
In the current implementation of the QEMU bash iotests, only qemu-io
processes may be run under the Valgrind with the switch '-valgrind'.
Let's allow the common.rc bash script running all other QEMU processes,
such as qemu-kvm, qemu-img, qemu-ndb and qemu-vxhs, under the Valgrind.
v7:
01: The co
Patchew URL:
https://patchew.org/QEMU/20190803210803.5701-1-richard.hender...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Type: series
Subject: [Qemu-devel] [PATCH v7 0/6] target/arm: Implement ARMv8.5-BTI for
linux-user
Changes since v6:
* Rebased on the ARMv8.1-VHE patch set.
* Review from Dave Martin:
+ Remove PSTATE.BTYPE adjustment on syscall entry.
+ Rely on PT_GNU_PROPERTY to find the NT_GNU_PROPERTY_TYPE_0 note.
+ For the test case, add a linker script to create the PHDR.
Changes since v5:
This patch series has implementation for "virtio pmem".
"virtio pmem" is fake persistent memory(nvdimm) in guest
which allows to bypass the guest page cache. This also
implements a VIRTIO based asynchronous flush mechanism.
Sharing guest kernel driver in this patchset with the
changes
> From: Mateja Marjanovic
> Subject: [PATCH v7 0/6] target/mips: Optimize MSA interleave instructions
>
> From: Mateja Marjanovic
>
> Optimize and refactor MSA instructions ILVEV.,
> ILVOD., ILVL. and ILVR..
Patch number 5/6 seems to be for some reason lost. Please resend the
complete series.
From: Mateja Marjanovic
Optimize and refactor MSA instructions ILVEV.,
ILVOD., ILVL. and ILVR..
v7:
- Use tcg constants, instead of uint64_t constants in
ILVEV. and ILVOD. instructions.
- Refactor gen_ilvod_b and gen_ilvod_h functions. Use
the shared function gen_ilvod_bh, which has two
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 passed on to
the kernel for handling by raising machine check
exception (an NMI). Upon such machine check exceptions,
if the address in error belon
On Tue, Dec 18, 2018 at 04:16:44PM +0800, Zhang Yi wrote:
> Linux 4.15 introduces a new mmap flag MAP_SYNC, which can be used to
> guarantee the write persistence to mmap'ed files supporting DAX (e.g.,
> files on ext4/xfs file system mounted with '-o dax').
>
> A description of MAP_SYNC and MAP_SH
Linux 4.15 introduces a new mmap flag MAP_SYNC, which can be used to
guarantee the write persistence to mmap'ed files supporting DAX (e.g.,
files on ext4/xfs file system mounted with '-o dax').
A description of MAP_SYNC and MAP_SHARED_VALIDATE can be found at
https://patchwork.kernel.org/patch
v5 was here:
https://lists.gnu.org/archive/html/qemu-devel/2018-04/msg04542.html
since then:
- 5/6: update iotest number, add R-b
(git-backport-diff doesn't handle renames well)
001/6:[] [--] 'qcow2: Prefer byte-based calls into bs->file'
002/6:[] [--] 'qcow2: Document some maximum size
On Thu, Sep 28, 2017 at 12:47:51PM -0400, Programmingkid wrote:
>
> > This patch series is an update to:
> >
> > v1: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02047.html
> > v2: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02471.html
> > v3: https://lists.gnu.org/arc
> This patch series is an update to:
>
> v1: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02047.html
> v2: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02471.html
> v3: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02517.html
> v4: https://lists.gnu.org/arch
Hi,
This series failed build test on s390x host. Please find the details below.
Type: series
Subject: [Qemu-devel] [PATCH v7 0/6] Initial support for keycodemapdb GIT
submodule
Message-id: 20170928120621.30288-1-berra...@redhat.com
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be
This patch series is an update to:
v1: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02047.html
v2: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02471.html
v3: https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg02517.html
v4: https://lists.gnu.org/archive/html/
This series adds a throttle block driver filter. Currently throttling is done
at the BlockBackend level. Using block driver interfaces we can move the
throttling to any point in the BDS graph using a throttle node which uses the
existing throttling code. This allows for potentially more complex
con
Pradeep Jagadeesh writes:
> On 7/7/2017 8:14 AM, Markus Armbruster wrote:
>> Pradeep Jagadeesh writes:
>>
>>> These patches provide the qmp interface, to query the io throttle
>>> status of the all fsdev devices that are present in a vm.
>>> also, it provides an interface to set the io throttle
On 7/7/2017 8:14 AM, Markus Armbruster wrote:
Pradeep Jagadeesh writes:
These patches provide the qmp interface, to query the io throttle
status of the all fsdev devices that are present in a vm.
also, it provides an interface to set the io throttle parameters of a
fsdev to a required value. s
On 7/14/2017 4:26 PM, Manos Pitsidianakis wrote:
On Fri, Jul 14, 2017 at 03:15:06PM +0200, Pradeep Jagadeesh wrote:
Hi Manos,
Thanks for sharing the link to your code patch.
On 7/14/2017 2:22 PM, Manos Pitsidianakis wrote:
Hello Pradeep, you might be interested in my work on refactoring the
b
On Fri, Jul 14, 2017 at 03:15:06PM +0200, Pradeep Jagadeesh wrote:
Hi Manos,
Thanks for sharing the link to your code patch.
On 7/14/2017 2:22 PM, Manos Pitsidianakis wrote:
Hello Pradeep, you might be interested in my work on refactoring the
block layer's throttling interface in my series:
ht
Hi Manos,
Thanks for sharing the link to your code patch.
On 7/14/2017 2:22 PM, Manos Pitsidianakis wrote:
Hello Pradeep, you might be interested in my work on refactoring the
block layer's throttling interface in my series:
https://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg04191.html
Hello Pradeep, you might be interested in my work on refactoring the
block layer's throttling interface in my series:
https://lists.nongnu.org/archive/html/qemu-devel/2017-07/msg04191.html
In this series you copy the existing legacy interface we want to get rid
of. I think it will be easier wor
On 7/7/2017 8:14 AM, Markus Armbruster wrote:
Pradeep Jagadeesh writes:
These patches provide the qmp interface, to query the io throttle
status of the all fsdev devices that are present in a vm.
also, it provides an interface to set the io throttle parameters of a
fsdev to a required value. s
PS: Sorry for the late review, got a bit overwhelmed...
Pradeep Jagadeesh writes:
> These patches provide the qmp interface, to query the io throttle
> status of the all fsdev devices that are present in a vm.
> also, it provides an interface to set the io throttle parameters of a
> fsdev to a required value. some of the patches also remove the dupli
These patches provide the qmp interface, to query the io throttle
status of the all fsdev devices that are present in a vm.
also, it provides an interface to set the io throttle parameters of a
fsdev to a required value. some of the patches also remove the duplicate
code that was present in block
Am 23.08.2016 um 16:21 hat Peter Lieven geschrieben:
> I decided to split this from the rest of the Qemu RSS usage series as
> it contains the more or less non contentious patches.
>
> I omitted the MAP_GROWSDOWN flag in mmap as we are not 100% sure which
> side effects it has.
>
> I kept the gua
On 23/08/2016 16:21, Peter Lieven wrote:
> I decided to split this from the rest of the Qemu RSS usage series as
> it contains the more or less non contentious patches.
>
> I omitted the MAP_GROWSDOWN flag in mmap as we are not 100% sure which
> side effects it has.
>
> I kept the guard page wh
I decided to split this from the rest of the Qemu RSS usage series as
it contains the more or less non contentious patches.
I omitted the MAP_GROWSDOWN flag in mmap as we are not 100% sure which
side effects it has.
I kept the guard page which is now nicely makes the stacks visible in
smaps. The
On 2 April 2016 at 15:29, Jean-Christophe Dubois wrote:
> This patch series adds support for the Freescale i.MX6 processor.
>
> For now we only support the following devices:
> * up to 4 Cortex A9 cores
> * A9 MPCORE (SCU, GIC, TWD)
> * 5 i.MX UARTs
> * 2 EPIT timers
> * 1 GPT timer
> * 7 GPIO con
This patch series adds support for the Freescale i.MX6 processor.
For now we only support the following devices:
* up to 4 Cortex A9 cores
* A9 MPCORE (SCU, GIC, TWD)
* 5 i.MX UARTs
* 2 EPIT timers
* 1 GPT timer
* 7 GPIO controllers
* 6 SDHC controllers
* 5 SPI controllers
* 1 CCM device
* 1 SRC d
Changes from v6->v7:
* Patch 1 - Cannot move cpu_model default setting to machine instance_init,
as vl.c can overwrite it again with a NULL during startup. Left check
in s390_init_cpus.
* Drop cpu_last patch (Andreas)
* Patch 4 - merged with patch that adds hotplug handler / set cpu propert
On 15 January 2016 at 22:38, Alistair Francis
wrote:
> I also need to make some changes to the actual SPI device to
> improve the functionality, but for the time being this works.
>
> V7
> - Use g_strdup_printf() for the bus names
> V6 (From Peter C):
> - Allow use of QOM paths for referencing q
I also need to make some changes to the actual SPI device to
improve the functionality, but for the time being this works.
V7
- Use g_strdup_printf() for the bus names
V6 (From Peter C):
- Allow use of QOM paths for referencing qbusses
- Use Alias to implement bus pinout.
V5:
- Fix a typo
- U
This series introduces support for GICv3 by KVM. Software emulation is
currently not supported.
Differences from v6:
- Wrap own GIC type definitions on top of KVM ones. Fixed build on
non-ARM-Linux hosts
Differences from v5:
- Fixed various checkpatch.pl style warnings
- Removed TODO in gicv3_i
On Thu, Jun 11, 2015 at 04:32:23PM +0530, Nikunj A Dadhania wrote:
> The patch series creates PCI device tree(DT) nodes in QEMU. The new
> hotplug code needs the device node creation in QEMU. While during
> boot, nodes were created in SLOF. It makes more sense to consolidate
> the code to one place
The patch series creates PCI device tree(DT) nodes in QEMU. The new
hotplug code needs the device node creation in QEMU. While during
boot, nodes were created in SLOF. It makes more sense to consolidate
the code to one place for better maintainability.
Based on David's spapr-next
https://github.c
*INTRODUCTION*
The goal of virtual Trusted Platform Module (vTPM) is to provide a TPM
functionality to virtual machines (Fedora, Ubuntu, Redhat, Windows .etc). This
allows programs to interact with a TPM in a virtual machine the same way they
interact with a TPM on the physical system. Each virt
Rebased on top of 2.0-rc0 so the only change was the way of QEMUMachine's
object creation. Too late/raw/controversial for 2.0? Thanks.
Alexey Kardashevskiy (5):
boot: extend get_boot_devices_list() to ignore suffixes
spapr-llan: add to boot device list
spapr-vio: fix firmware names
spapr:
On Thu, Dec 05, 2013 at 08:02:46PM +0800, Wenchao Xia wrote:
> V2:
> 1: all fail case will goto fail section.
> 2: add the goto code.
>
> v3:
> Address Stefan's comments:
> 2: don't goto fail after allocation failure.
> 3: use sn->l1size correctly in qcow2_free_cluster().
> 4-7: add te
On Wed, Dec 18, 2013 at 10:13:40AM +0800, Wenchao Xia wrote:
> Hello, any comments? I hope to have a new year gift
It's in the queue, I hope to review it this week.
Hello, any comments? I hope to have a new year gift
ping?
[PATCH v7 1/6] hw/arm: add very initial support for Canon DIGIC SoC
[PATCH v7 2/6] hw/arm/digic: prepare DIGIC-based boards support
[PATCH v7 3/6] hw/arm/digic: add timer support
[PATCH v7 4/6] hw/arm/digic: add UART support
[PATCH v7 5/6] hw/arm/digic: add NOR ROM support
[PATCH v7 6/6] MAINTAINER
hello, OK to merge?
V2:
1: all fail case will goto fail section.
2: add the goto code.
v3:
Address Stefan's comments:
2: don't goto fail after allocation failure.
3: use sn->l1size correctly in qcow2_free_cluster().
4-7: add test case to verify the error paths.
Other:
1: new patch fix a existing bug,
On Wed, Dec 04, 2013 at 05:10:53PM +0800, Wenchao Xia wrote:
> This series allow user to read internal snapshot's contents without qemu-img
> convert.
>
> V2:
> Address Stefan's comments:
> 02: add 'fall through' comments in the case statement.
> 03: add doc about the difference of internal
This series allow user to read internal snapshot's contents without qemu-img
convert.
V2:
Address Stefan's comments:
02: add 'fall through' comments in the case statement.
03: add doc about the difference of internal snapshot and backing chain
snapshot, which is used in previous '--snapshot'
This series adds support for three new instructions added in ARMv8 -
VSEL, VMINNM and VMAXNM.
Will Newton (6):
target-arm: Move call to disas_vfp_insn out of disas_coproc_insn.
target-arm: Implement ARMv8 VSEL instruction.
softfloat: Remove unused argument from MINMAX macro.
softfloat: Add
qemu-img info provides only pretty general information about an image.
For any image format, there might be specific options which cannot be
represented in a universal way; for instance, qcow2 provides the
compatibility and lazy_refcount options whose values are certainly
interesting but currently
Hi Paolo, Anthony
No doubts I'm a nice guy :)
We'll be glad to amend this implementation with tests as soon as
infrastructure is ready.
Dmitry
On Fri, Nov 30, 2012 at 6:17 PM, Anthony Liguori wrote:
> Paolo Bonzini writes:
>
> >> Yes, we tested this device with various guests (both Linux and
Paolo Bonzini writes:
>> Yes, we tested this device with various guests (both Linux and
>> Windows) and it also passed WHQL tests for Windows Server 2008 R2
>> OS. The issue is Anthony asked us to write a basic test for the device (a
>> packet transmission test) and we are trying to get some refe
> Yes, we tested this device with various guests (both Linux and
> Windows) and it also passed WHQL tests for Windows Server 2008 R2
> OS. The issue is Anthony asked us to write a basic test for the device (a
> packet transmission test) and we are trying to get some reference
> code or documentatio
Hello Stefan
Yes, we tested this device with various guests (both Linux and Windows) and
it also passed WHQL tests for Windows Server 2008 R2 OS.
The issue is Anthony asked us to write a basic test for the device (a
packet transmission test) and we are trying to get some reference code or
document
On Fri, Nov 16, 2012 at 2:55 PM, Dmitry Fleytman wrote:
> We didn't succeed to find any guide or sample for the
> king of tests required (packets transmission).
> If someone can provide a pointer to the relevant
> information we'll be very grateful.
QEMU does not have a NI
Thanks, Stefan.
Sent from my iPhone
On 21 בנוב 2012, at 10:37, Stefan Hajnoczi wrote:
> On Fri, Nov 16, 2012 at 03:55:29PM +0200, Dmitry Fleytman wrote:
>> NOTE: This is not a final patches for commit,
>> they are just for the latest fixes review.
>> This set of patches still misses t
On Fri, Nov 16, 2012 at 03:55:29PM +0200, Dmitry Fleytman wrote:
> NOTE: This is not a final patches for commit,
> they are just for the latest fixes review.
> This set of patches still misses test for the device.
>
> We didn't succeed to find any guide or sample for the
>
NOTE: This is not a final patches for commit,
they are just for the latest fixes review.
This set of patches still misses test for the device.
We didn't succeed to find any guide or sample for the
king of tests required (packets transmission).
If someone can provide
On Mon, 27 Aug 2012 15:23:31 +0800
Amos Kong wrote:
> On 20/08/12 23:08, Luiz Capitulino wrote:
> > On Mon, 20 Aug 2012 07:25:13 -0600
> > Eric Blake wrote:
> >
> >> On 08/19/2012 10:39 PM, Amos Kong wrote:
> >>> This series converted 'sendkey' command to qapi. The raw value
> >>> in hexadecimal
On 20/08/12 23:08, Luiz Capitulino wrote:
On Mon, 20 Aug 2012 07:25:13 -0600
Eric Blake wrote:
On 08/19/2012 10:39 PM, Amos Kong wrote:
This series converted 'sendkey' command to qapi. The raw value
in hexadecimal format is not supported by 'send-key' of qmp.
Are we still trying to get this
On Mon, 20 Aug 2012 07:25:13 -0600
Eric Blake wrote:
> On 08/19/2012 10:39 PM, Amos Kong wrote:
> > This series converted 'sendkey' command to qapi. The raw value
> > in hexadecimal format is not supported by 'send-key' of qmp.
>
> Are we still trying to get this into 1.2, or have we missed that
On 08/19/2012 10:39 PM, Amos Kong wrote:
> This series converted 'sendkey' command to qapi. The raw value
> in hexadecimal format is not supported by 'send-key' of qmp.
Are we still trying to get this into 1.2, or have we missed that deadline?
--
Eric Blake ebl...@redhat.com+1-919-301-3266
This series converted 'sendkey' command to qapi. The raw value
in hexadecimal format is not supported by 'send-key' of qmp.
Amos Kong (6):
fix doc of using raw values with sendkey
monitor: rename keyname '<' to 'less'
hmp: rename arguments
qapi: generate list struct and visit_list for enum
On Wed, Aug 8, 2012 at 7:51 PM, Corey Bryant wrote:
>
>
> On 08/08/2012 11:58 AM, Stefan Hajnoczi wrote:
>>
>> On Wed, Aug 8, 2012 at 3:54 PM, Corey Bryant
>> wrote:
>>>
>>>
>>>
>>> On 08/08/2012 09:04 AM, Stefan Hajnoczi wrote:
On Tue, Aug 7, 2012 at 4:58 PM, Corey Bryant
wr
On 08/08/2012 11:58 AM, Stefan Hajnoczi wrote:
On Wed, Aug 8, 2012 at 3:54 PM, Corey Bryant wrote:
On 08/08/2012 09:04 AM, Stefan Hajnoczi wrote:
On Tue, Aug 7, 2012 at 4:58 PM, Corey Bryant
wrote:
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes
On Wed, Aug 8, 2012 at 3:54 PM, Corey Bryant wrote:
>
>
> On 08/08/2012 09:04 AM, Stefan Hajnoczi wrote:
>>
>> On Tue, Aug 7, 2012 at 4:58 PM, Corey Bryant
>> wrote:
>>>
>>> libvirt's sVirt security driver provides SELinux MAC isolation for
>>> Qemu guest processes and their corresponding image f
On 08/08/2012 09:04 AM, Stefan Hajnoczi wrote:
On Tue, Aug 7, 2012 at 4:58 PM, Corey Bryant wrote:
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from op
On Tue, Aug 7, 2012 at 4:58 PM, Corey Bryant wrote:
> libvirt's sVirt security driver provides SELinux MAC isolation for
> Qemu guest processes and their corresponding image files. In other
> words, sVirt uses SELinux to prevent a QEMU process from opening
> files that do not belong to it.
>
> sV
libvirt's sVirt security driver provides SELinux MAC isolation for
Qemu guest processes and their corresponding image files. In other
words, sVirt uses SELinux to prevent a QEMU process from opening
files that do not belong to it.
sVirt provides this support by labeling guests and resources with
Hi all,
this is the seventh version of the Xen save/restore patch series.
We have been discussing this issue for quite a while on #qemu and
qemu-devel:
http://marc.info/?l=qemu-devel&m=132346828427314&w=2
http://marc.info/?l=qemu-devel&m=132377734605464&w=2
Please review the second patch: Intro
This patch series adds support for the Calxeda Highbank SoC.
It depends on my previous patch series "various ARM fixes for
Calxeda Highbank" and "ahci: convert ahci_reset to use AHCIState".
Some of the patches are carried voer from "Various ARM fixes
for Calxeda Highbank" and were reviewed but not
This patch series is v7 of the pcie switch emulators.
Now the express part has been merged, so the aer part is left.
This patch series is for the master branch because the current pci branch
seems a bit behind.
. I didn't changed the way to pass argument by pcie_aer_inject_error
qmp command.
I
Hello,
This series lets interested callers ask for an -EAGAIN return from the
chardev backends (only unix and tcp sockets as of now) to implement
their own flow control.
A new call, qemu_chr_write_nb() is added, that will fallback to
qemu_chr_write() if the backend file isn't non-blocking or if n
77 matches
Mail list logo
