My real name is "HOU Qiming". @Marcel Apfelbaum
can you incorporate that in your v2 patch? Thanks!
Qiming
On Tue, May 7, 2019 at 2:25 PM Philippe Mathieu-Daudé
wrote:
> Hi Marcel,
>
> On 5/7/19 7:49 AM, Marcel Apfelbaum wrote:
> > From: HQM
> >
> > In a GVT-g setup with dmabuf and GTK GUI, th
Since c2077e2c "pci: Adjust PCI config limit based on bus topology",
pci_adjust_config_limit() has been used in the config space read and write
paths to only permit access to extended config space on buses which permit
it. Specifically it prevents access on devices below a vanilla-PCI bus via
some
On Tue, May 07, 2019 at 10:48:08AM +1000, Anton Blanchard wrote:
> vslv and vsrv are broken on little endian, we append 00 to the
> high byte not the low byte. Fix it by using the VsrB() accessor.
>
> Signed-off-by: Anton Blanchard
Applied, thanks.
> ---
> target/ppc/int_helper.c | 14 +++-
Cc: Peter for a libvirt perspective.
Stefano Garzarella writes:
> This patch adds the support of preallocation (off/full) for the RBD
> block driver.
> If available, we use rbd_writesame() to quickly fill the image when
> full preallocation is required.
>
> Signed-off-by: Stefano Garzarella
> -
c2077e2c "pci: Adjust PCI config limit based on bus topology"
introduced checking the availability of extended config space for
PCI-E devices which are in a bus topology that doesn't permit extended
config space access (e.g. under PCI-E to PCI then PCI to PCI-E
bridges).
This caused some problems
Hi Marcel,
On 5/7/19 7:49 AM, Marcel Apfelbaum wrote:
> From: HQM
>
> In a GVT-g setup with dmabuf and GTK GUI, the current 2D texture at
> surface_gl_update_texture is not necessarily
> surface->texture. Adding a glBindTexture fixes related crashes and
> artifacts, and is generally more secure.
These functions have an explicit test for accesses above the device's
config size. But pci_host_config_{read,write}_common() which they're
about to call already have checks against the config space limit and
do the right thing. So, remove the redundant tests.
Signed-off-by: David Gibson
Reviewe
pci_bus_is_root() currently relies on a method in the PCIBusClass.
But it's always known if a PCI bus is a root bus when we create it, so
using a dynamic method is overkill.
This replaces it with an IS_ROOT bit in a new flags field, which is set on
root buses and otherwise clear. As a bonus this
On Tue, May 07, 2019 at 10:48:09AM +1000, Anton Blanchard wrote:
> We should only look at 5 bits of each byte, not 6.
>
> Fixes: 3e00884f4e9f ("target-ppc: add vrldnmi and vrlwmi instructions")
> Signed-off-by: Anton Blanchard
Hrm. So, what lives in those extra bits in the 'w' instructions? Is
On Tue, May 07, 2019 at 10:48:06AM +1000, Anton Blanchard wrote:
> During the conversion these instructions were incorrectly treated as
> stores. We need to use set_cpu_vsr* and not get_cpu_vsr*.
>
> Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
> helpers for VSR regis
The is_bridge field in PCIDevice acts as a bool, but is declared as an int.
Declare it as a bool for clarity, and change everything that writes it to
use true/false instead of 0/1 to match.
Signed-off-by: David Gibson
---
hw/pci-bridge/dec.c| 4 ++--
hw/pci-bridge/i82801b11.c
The only remaining caller of pci_get_bus_devfn() is pci_nic_init_nofail(),
itself an old compatibility function. Fold the two together to avoid
re-using the stale interface.
While we're there replace the explicit fprintf()s with error_report().
Signed-off-by: David Gibson
---
hw/pci/pci.c | 61
On Tue, May 07, 2019 at 10:48:11AM +1000, Anton Blanchard wrote:
> A recent cleanup changed the pre zeroing of the result from 64 bit
> to 32 bit operations:
>
> -result.u64[i] = 0;
> +result.VsrW(i) = 0;
>
> This corrupts the result.
>
> Fixes: 60594fea298d ("target/ppc: remove
On Tue, May 07, 2019 at 09:43:34AM +1000, Suraj Jitindar Singh wrote:
> On Mon, 2019-05-06 at 13:23 +1000, David Gibson wrote:
> > On Mon, May 06, 2019 at 11:48:03AM +1000, Suraj Jitindar Singh wrote:
> > > The ibm,purr and ibm,spurr device tree properties are used to
> > > indicate
> > > that the
On Tue, May 07, 2019 at 10:48:05AM +1000, Anton Blanchard wrote:
> Fix a typo in xxbrq and xxbrw where we put both results into the lower
> doubleword.
>
> Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
> helpers for VSR register access")
> Signed-off-by: Anton Blanchar
On Tue, May 07, 2019 at 10:48:03AM +1000, Anton Blanchard wrote:
> Fix a typo in xvxsigdp where we put both results into the lower
> doubleword.
>
> Fixes: dd977e4f45cb ("target/ppc: Optimize x[sv]xsigdp using deposit_i64()")
> Signed-off-by: Anton Blanchard
Applied, thanks.
> ---
> target/ppc
On Tue, May 07, 2019 at 10:48:04AM +1000, Anton Blanchard wrote:
> xxspltib raises a VMX or a VSX exception depending on the register
> set it is operating on. We had a check, but it was backwards.
>
> Fixes: f113283525a4 ("target-ppc: add xxspltib instruction")
> Signed-off-by: Anton Blanchard
>
On Tue, May 07, 2019 at 10:48:07AM +1000, Anton Blanchard wrote:
> We were using set_cpu_vsr* when we should have used set_cpu_vsrl*
Commit message doesn't appear to match the code.
>
> Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
> helpers for VSR register access")
From: HQM
In a GVT-g setup with dmabuf and GTK GUI, the current 2D texture at
surface_gl_update_texture is not necessarily
surface->texture. Adding a glBindTexture fixes related crashes and
artifacts, and is generally more secure.
Signed-off-by: HQM
Tested-by: Marcel Apfelbaum
[fixed malformed
On Mon, May 06, 2019 at 03:41:58PM +0800, Zhenyu Wang wrote:
> On 2019.05.06 11:20:32 +0800, Zhenyu Wang wrote:
> > On 2019.05.05 21:51:02 -0400, Yan Zhao wrote:
> > > This feature implements the version attribute for Intel's vGPU mdev
> > > devices.
> > >
> > > version attribute is rw.
> > > It's
Hi Cédric,
On 5/6/19 4:20 PM, Cédric Le Goater wrote:
> Signed-off-by: Cédric Le Goater
> ---
> hw/arm/aspeed_soc.c | 50 ++---
> 1 file changed, 20 insertions(+), 30 deletions(-)
>
> diff --git a/hw/arm/aspeed_soc.c b/hw/arm/aspeed_soc.c
> index bd83618c
On Tue, Apr 30, 2019 at 11:29:08PM +0800, Cornelia Huck wrote:
> On Wed, 24 Apr 2019 04:15:58 -0400
> Yan Zhao wrote:
>
> > On Wed, Apr 24, 2019 at 03:56:24PM +0800, Cornelia Huck wrote:
> > > On Tue, 23 Apr 2019 23:10:37 -0400
> > > Yan Zhao wrote:
> > >
> > > > On Tue, Apr 23, 2019 at 05:59:32
On 06/05/2019 19.21, Eric Blake wrote:
> For some particular configurations of ext4, sizing an image to 84
> sectors + 1 byte causes test failures when the size of the hole is
> rounded to a 4k alignment. Let's instead size things to 128 sectors +
> 1 byte, as the 64k boundary is more likely to wor
On 06/05/2019 18.52, Eric Blake wrote:
> On 5/6/19 10:32 AM, Max Reitz wrote:
>> On 01.05.19 15:41, Thomas Huth wrote:
>>> The output of qemu-io changed recently - most tests have been fixed in
>>> commit 36b9986b08787019ef42 ("tests/qemu-iotests: Fix output of qemu-io
>>> related tests") already,
On 5/6/19 11:38 PM, Eduardo Habkost wrote:
> test-qapi.py doesn't force a specific encoding for stderr or
> stdout, but the reference files used by check-qapi-schema are in
> UTF-8. This breaks check-qapi-schema under certain circumstances
> (e.g. if using the C locale and Python < 3.7).
>
> We n
On Mon, 6 May 2019 at 14:21, Cédric Le Goater wrote:
>
> This will simplify the definition of new SoCs, like the AST2600 which
> should use a slightly different address space and have a different set
> of controllers.
>
> Signed-off-by: Cédric Le Goater
Reviewed-by: Joel Stanley
On Mon, 6 May 2019 at 14:21, Cédric Le Goater wrote:
>
> Signed-off-by: Cédric Le Goater
Reviewed-by: Joel Stanley
On Mon, 6 May 2019 at 14:21, Cédric Le Goater wrote:
>
> This will simplify the definition of new SoCs, like the AST2600 which
> should use a different CPU and a different IRQ number layout.
>
> Signed-off-by: Cédric Le Goater
Reviewed-by: Joel Stanley
On 5/6/19 11:41 PM, Eduardo Habkost wrote:
> On Sat, May 04, 2019 at 01:52:51PM +0200, Philippe Mathieu-Daudé wrote:
>> On 3/13/19 12:45 AM, Philippe Mathieu-Daudé wrote:
>>> Add the raspi2 to the list of boards tested by the
>>> boot_linux_console Avocado test.
>>>
>>> Based on "Acceptance Tests:
Zhang Chen writes:
> From: Zhang Chen
>
> No one to maintain qemu-options related file, add it to Markus's
> Command line option argument parsing field.
>
> Signed-off-by: Zhang Chen
> ---
> MAINTAINERS | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index
On Fri, Apr 26, 2019 at 04:40:17PM +1000, Alexey Kardashevskiy wrote:
>
>
> On 24/04/2019 14:19, David Gibson wrote:
> > Since c2077e2c "pci: Adjust PCI config limit based on bus topology",
> > pci_adjust_config_limit() has been used in the config space read and write
> > paths to only permit acc
Eduardo Habkost writes:
> This series adds machine type deprecation information to the
> output of 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 mach
On 4/29/19 7:40 AM, Peter Maydell wrote:
>> diff --git a/target/s390x/cpu.c b/target/s390x/cpu.c
>> index 698dd9cb82..790670ebeb 100644
>> --- a/target/s390x/cpu.c
>> +++ b/target/s390x/cpu.c
>> @@ -282,17 +282,18 @@ static void s390_cpu_initfn(Object *obj)
>> {
>> CPUState *cs = CPU(obj);
>>
Hi Alexey,
> Out of curiosity - how did you find this one and (especially) the next
> one - "Fix xxspltib"? Is there some testsuite, or by just looking at
> the code? Thanks,
I'm running test cases and comparing results between QEMU and real
hardware.
Thanks,
Anton
During migration, we would sync bitmap from ram_list.dirty_memory to
RAMBlock.bmap in cpu_physical_memory_sync_dirty_bitmap().
Since we set RAMBlock.bmap and ram_list.dirty_memory both to all 1, this
means at the first round this sync is meaningless and is a duplicated
work.
Leaving RAMBlock->bma
This is a question I have encountered while using QEMU.
I want to compile the source directly rather than through apt or yum and
install QEMU and input the output statement to the source to check the
output value.
When I compiled QEMU using dpkg-buildpackage in Ubuntu, I verified that
when QEMU's
On Mon, 2019-05-06 at 16:15 +1000, David Gibson wrote:
> On Fri, May 03, 2019 at 03:53:05PM +1000, Suraj Jitindar Singh wrote:
> > The Processor Utilisation of Resources Register (PURR) and Scaled
> > Processor Utilisation of Resources Register (SPURR) provide an
> > estimate
> > of the resources u
On 07/05/2019 10:48, Anton Blanchard wrote:
> Fix a typo in xvxsigdp where we put both results into the lower
> doubleword.
>
> Fixes: dd977e4f45cb ("target/ppc: Optimize x[sv]xsigdp using deposit_i64()")
> Signed-off-by: Anton Blanchard
> ---
> target/ppc/translate/vsx-impl.inc.c | 2 +-
> 1
A recent cleanup changed the pre zeroing of the result from 64 bit
to 32 bit operations:
-result.u64[i] = 0;
+result.VsrW(i) = 0;
This corrupts the result.
Fixes: 60594fea298d ("target/ppc: remove various HOST_WORDS_BIGENDIAN hacks in
int_helper.c")
Signed-off-by: Anton Blanchar
The immediate field is 6 bits, not 5.
Fixes: 217f6b88058f ("target-ppc: add dtstsfi[q] instructions")
Signed-off-by: Anton Blanchard
---
target/ppc/internal.h | 2 ++
target/ppc/translate/dfp-impl.inc.c | 2 +-
2 files changed, 3 insertions(+), 1 deletion(-)
diff --git a/target/pp
On Mon, May 06, 2019 at 04:12:02PM +0200, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > Python 2 will reach end of life in January 1 2020. Declare it as
> > deprecated.
> >
> > Signed-off-by: Eduardo Habkost
> > ---
> > configure| 8
> > qemu-deprecated.texi | 8
vslv and vsrv are broken on little endian, we append 00 to the
high byte not the low byte. Fix it by using the VsrB() accessor.
Signed-off-by: Anton Blanchard
---
target/ppc/int_helper.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/target/ppc/int_helper.c b/
During the conversion these instructions were incorrectly treated as
stores. We need to use set_cpu_vsr* and not get_cpu_vsr*.
Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
helpers for VSR register access")
Signed-off-by: Anton Blanchard
---
target/ppc/translate/vsx-
We should only look at 5 bits of each byte, not 6.
Fixes: 3e00884f4e9f ("target-ppc: add vrldnmi and vrlwmi instructions")
Signed-off-by: Anton Blanchard
---
target/ppc/int_helper.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/target/ppc/int_helper.c b/tar
We were using set_cpu_vsr* when we should have used set_cpu_vsrl*
Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
helpers for VSR register access")
Signed-off-by: Anton Blanchard
---
target/ppc/translate/vsx-impl.inc.c | 4 ++--
1 file changed, 2 insertions(+), 2 delet
xxspltib raises a VMX or a VSX exception depending on the register
set it is operating on. We had a check, but it was backwards.
Fixes: f113283525a4 ("target-ppc: add xxspltib instruction")
Signed-off-by: Anton Blanchard
---
target/ppc/translate/vsx-impl.inc.c | 9 +
1 file changed, 5 in
Fix a typo in xvxsigdp where we put both results into the lower
doubleword.
Fixes: dd977e4f45cb ("target/ppc: Optimize x[sv]xsigdp using deposit_i64()")
Signed-off-by: Anton Blanchard
---
target/ppc/translate/vsx-impl.inc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/targ
Fix a typo in xxbrq and xxbrw where we put both results into the lower
doubleword.
Fixes: 8b3b2d75c7c0 ("introduce get_cpu_vsr{l,h}() and set_cpu_vsr{l,h}()
helpers for VSR register access")
Signed-off-by: Anton Blanchard
---
target/ppc/translate/vsx-impl.inc.c | 4 ++--
1 file changed, 2 inser
On 2019/5/6 下午6:32, Lukas Straub wrote:
On Sat, 20 Apr 2019 19:14:25 +0200
Lukas Straub wrote:
From: Lukas Straub
Because event_unhandled_count may be accessed concurrently, it needs
to be protected by taking the lock. However the assert is outside the
lock, probably causing it to read garb
On Mon, 2019-05-06 at 16:20 +1000, David Gibson wrote:
> On Fri, May 03, 2019 at 03:53:03PM +1000, Suraj Jitindar Singh wrote:
> > This patch series adds the necessary parts so that a tcg guest is
> > able to use
> > kvm facilities. That is a tcg guest can boot its own kvm guests.
>
> The topic li
On Mon, 2019-05-06 at 13:23 +1000, David Gibson wrote:
> On Mon, May 06, 2019 at 11:48:03AM +1000, Suraj Jitindar Singh wrote:
> > The ibm,purr and ibm,spurr device tree properties are used to
> > indicate
> > that the processor implements the Processor Utilisation of
> > Resources
> > Register (PU
This patch allows us to enable/disable the RISC-V ISA extensions from
the QEMU command line. This works with the rv32 and rv64 machines. The
idea is that in the future we can now add extensions and leave them
disabled by default until enabled by the user.
Signed-off-by: Alistair Francis
---
Based
On Sat, May 04, 2019 at 01:52:51PM +0200, Philippe Mathieu-Daudé wrote:
> On 3/13/19 12:45 AM, Philippe Mathieu-Daudé wrote:
> > 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://
test-qapi.py doesn't force a specific encoding for stderr or
stdout, but the reference files used by check-qapi-schema are in
UTF-8. This breaks check-qapi-schema under certain circumstances
(e.g. if using the C locale and Python < 3.7).
We need to make sure test-qapi.py always generate UTF-8 out
On Mon, May 06, 2019 at 11:13:28AM -0500, Paolo Bonzini wrote:
> On 05/05/19 04:06, Peter Xu wrote:
> >> I wonder if it's possible to untangle this and make the irqchip
> >> option stop affecting guest ABI on 4.1+ machine-types? This way
> >> QEMU could choose smarter defaults in the future withou
On Mon, May 06, 2019 at 10:33:53AM -0700, Richard Henderson wrote:
> We now have an interface for guest visible random numbers.
>
> Cc: Paolo Bonzini
> Cc: Eduardo Habkost
> Signed-off-by: Richard Henderson
Reviewed-by: Eduardo Habkost
--
Eduardo
On 5/6/19 1:17 PM, Cornelia Huck wrote:
If a ccw has CCW_FLAG_SKIP set, and the command is of type
read, read backwards, or sense, no data should be written
to the guest for that command.
Signed-off-by: Cornelia Huck
---
Only extremely lightly tested (i.e., can boot a guest.)
---
hw/s390
in blockdev_backup_prepare, we check to make sure that the target is
associated with a compatible aio context. However, do_blockdev_backup is
called later and has some logic to move the target to a compatible
aio_context. The transaction version will fail certain commands
needlessly early as a resu
On Mon, 6 May 2019 12:27:46 -0500
Eric Blake wrote:
> On 5/3/19 3:27 AM, Antonio Ospite wrote:
> > From: Antonio Ospite
> >
> > The configure script breaks when the qemu source directory is in a path
> > containing white spaces, in particular the list of targets is not
> > correctly generated w
Yes
Sent from my cell phone, please ignore typos
On Mon, May 6, 2019, 6:11 PM Eric Blake wrote:
> On 5/4/19 3:36 AM, Sarah Harris wrote:
> > Signed-off-by: Sarah Harris
> > ---
>
> > +++ b/qapi/common.json
> > @@ -187,7 +187,7 @@
> > # Since: 3.0
> > ##
> > { 'enum' : 'SysEmuTarget',
> > -
We have to start by applying the permission restrictions to new_bs
before we can loosen them on old_bs. See the comment for the
explanation.
Signed-off-by: Max Reitz
---
block.c | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/block.c b/block.c
index fb6f0
On Mon, May 06, 2019 at 01:53:28PM +0200, Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > This series adds a new CPUClass::class_name_format field, which
> > allows us to delete 16 of the 21 *_cpu_class_by_name() functions
> > that exist today.
>
> Which five remain, and why?
alpha_cpu
If a block node uses bdrv_child_try_set_perm() to change the permission
it takes on its child, the result may be very short-lived. If anything
makes the block layer recalculate the permissions internally, it will
invoke the node driver's .bdrv_child_perm() implementation. The
permission/shared pe
raw_check_perm() + raw_set_perm() can change the flags associated with
the current FD. If so, we have to update BDRVRawState.open_flags
accordingly. Otherwise, we may keep reopening the FD even though the
current one already has the correct flags.
Signed-off-by: Max Reitz
---
block/file-posix.
This patch makes three functions report whether the necessary permission
change purely loosens restrictions or not. These functions are:
- bdrv_check_perm()
- bdrv_check_update_perm()
- bdrv_child_check_perm()
Callers can use this result to decide whether a failure is fatal or not
(see the next p
commit_top_bs never requests or unshares any permissions. There is no
reason to make this so explicit here.
Signed-off-by: Max Reitz
---
block/commit.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/block/commit.c b/block/commit.c
index 14e5bb394c..44b3083b84 100644
--- a/block/commit.c
+
We generally assume that loosening permission restrictions can never
fail. We have seen in the past that this assumption is wrong. This has
led to crashes because we generally pass &error_abort when loosening
permissions.
However, a failure in such a case should actually be handled in quite
the
We cannot use bdrv_child_try_set_perm() to give up all restrictions on
the child edge, and still have bdrv_mirror_top_child_perm() request
BLK_PERM_WRITE. Fix this by making bdrv_mirror_top_child_perm() return
0/BLK_PERM_ALL when we want to give up all permissions, and replacing
bdrv_child_try_set
Hi,
This series is mainly a fix for
https://bugzilla.redhat.com/show_bug.cgi?id=1703793. The problem
described there is that mirroring to a gluster volume, then switching
off the volume makes qemu crash. There are two problems here:
(1) file-posix reopens the FD all the time because it thinks t
Thomas Huth writes:
> On 03/05/2019 18.15, Alex Bennée wrote:
>>
>> Thomas Huth writes:
>>
>>> On 03/05/2019 16.39, Alex Bennée wrote:
This attempts to clean-up the output to better match the output of the
rest of the QEMU check system. This includes:
- formatting as " T
Vladimir Sementsov-Ogievskiy writes:
> 05.05.2019 18:54, Thomas Huth wrote:
>> On 03/05/2019 18.15, Alex Bennée wrote:
>>>
>>> Thomas Huth writes:
>>>
On 03/05/2019 16.39, Alex Bennée wrote:
> This attempts to clean-up the output to better match the output of the
> rest of the QEM
Sorry, I don't have the test code, since this was created by a memory
corruption. However, the way I understand the message is, that there is
some internal disagreement how to decode the op-code "05139517e2bf"
- which mige be an invalid opcode anyway. So a simple test application
would just con
On 5/6/19 5:17 PM, Laszlo Ersek wrote:
> On 05/05/19 22:06, Philippe Mathieu-Daudé wrote:
>> The pflash device is a child of TYPE_DEVICE, so it can implement
>> the DeviceReset handler. Actually it has to implement it, else
>> on machine reset it might stay in an incoherent state, as it has
>> been
This does require adjusting all existing users.
Signed-off-by: Richard Henderson
---
target/arm/translate-sve.c | 24
target/hppa/translate.c | 16
target/riscv/insn_trans/trans_rvc.inc.c | 10 +-
target/riscv/transla
:
https://github.com/rth7680/qemu.git tags/pull-dt-20190506
for you to fetch changes up to 451e4ffdb0003ab5ed0d98bd37b385c076aba183:
decodetree: Add DisasContext argument to !function expanders (2019-05-06
11:18:34 -0700)
Add s
Assuming that the ISA clearly describes how to determine
the length of the instruction, and the ISA has a reasonable
maximum instruction length, the input to the decoder can be
right-justified in an appropriate insn word.
This is not 100% convenient, as out-of-line %fields are
numbered relative to
Read the instruction, loading no more bytes than necessary.
Signed-off-by: Richard Henderson
---
scripts/decodetree.py | 175 +-
1 file changed, 172 insertions(+), 3 deletions(-)
diff --git a/scripts/decodetree.py b/scripts/decodetree.py
index 555a46522b.
On 5/3/19 12:06 PM, Stefano Garzarella wrote:
> net_client_init() uses a variable length array to store the prefix
> of 'ipv6-net' parameter (e.g. if ipv6-net=fec0::0/64, the prefix
> is 'fec0::0').
> Since the IPv6 prefix can be at most as long as an IPv6 address,
> we can use an array with fixed
This is the counter part patch against latest libvirt git master head to
support the 'vii' feature of patch 5, which introduces the XML config
XML tag "important" on libvirt side.
To stick with the previous example mentioned with patch 5, likewise
libvirt XML configuration might then look like thi
The last bios indeed helped. It knows runs under 200ms.
Do you anticipate doing minor release of 3.1.0 with updated bios to address
this issue? Or users are expected to upgrade to QEMU 4.0.0?
Regards,
Waldek
On Thu, May 2, 2019 at 4:05 AM Stefano Garzarella <
1826...@bugs.launchpad.net> wrote:
On 5/6/19 12:19 PM, Vladimir Sementsov-Ogievskiy wrote:
+++ b/block/vvfat.c
@@ -1494,8 +1494,8 @@ static int vvfat_read(BlockDriverState *bs, int64_t
sector_num,
DLOG(fprintf(stderr, "sectors %" PRId64 "+%" PRId64
" alloc
On 5/4/19 1:51 AM, Thomas Huth wrote:
>> Hmm, it's passing for me on ext4, but that probably means we have
>> different configuration parameters. I'm not sure how to easily show what
>> parameters a particular ext4 partition uses to compare the differences
>> between your setup and mine (mine is t
We now have an interface for guest visible random numbers.
Cc: Paolo Bonzini
Cc: Eduardo Habkost
Signed-off-by: Richard Henderson
---
target/i386/helper.h | 2 ++
target/i386/cpu.c| 5 ++--
target/i386/int_helper.c | 21 +++
target/i386/translate.c | 55 +
The random number is intended for use by the guest. As such, we should
honor the -seed argument for reproducibility. Use the *_nofail routine
instead of rolling our own error handling locally.
Cc: qemu-...@nongnu.org
Cc: Andrew Baumann
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard
We now have an interface for guest visible random numbers.
Acked-by: David Gibson
Signed-off-by: Richard Henderson
---
target/ppc/int_helper.c | 42 +
1 file changed, 30 insertions(+), 12 deletions(-)
diff --git a/target/ppc/int_helper.c b/target/ppc/int
The random number is intended for use by the guest. As such, we should
honor the -seed argument for reproducibility.
Cc: qemu-...@nongnu.org
Cc: Igor Mitsyanko
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
hw/misc/exynos4210_rng.c | 11 ---
1 file changed, 4
On Mon, May 06, 2019 at 03:23:08PM +0200, Markus Armbruster wrote:
> Stefano Garzarella writes:
>
> > net_client_init() uses a variable length array to store the prefix
> > of 'ipv6-net' parameter (e.g. if ipv6-net=fec0::0/64, the prefix
> > is 'fec0::0').
> > Since the IPv6 prefix can be at most
On 5/6/19 7:37 PM, Yuval Shaia wrote:
> Any GID change in guest must be propagated to the host. This is already
> done by firing QMP event to management system such as libvirt which in
> turn will update the host with the relevant change.
>
> When qemu is executed on non-qmp framework (ex from
Use a better interface for random numbers than rand() * 3.
Cc: Laurent Vivier
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
linux-user/aarch64/target_syscall.h | 2 --
linux-user/aarch64/cpu_loop.c | 29 ++-
linux-user/syscall.c
The random number is intended for use by the guest. As such, we should
honor the -seed argument for reproducibility. Use the *_nofail routine
instead of error_abort directly.
Cc: qemu-...@nongnu.org
Reviewed-by: Joel Stanley
Signed-off-by: Richard Henderson
---
hw/misc/nrf51_rng.c | 4 ++--
1
Cc: qemu-...@nongnu.org
Cc: Peter Maydell
Signed-off-by: Richard Henderson
---
v3: Log errors with -d unimp, for lack of a better flag.
---
target/arm/cpu.h| 5 +
target/arm/cpu64.c | 1 +
target/arm/helper.c | 44
3 files changed, 50 inser
Cc: Laurent Vivier
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
linux-user/main.c | 15 +--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/linux-user/main.c b/linux-user/main.c
index 7dfb202e5d..e05aebe4e1 100644
--- a/linux-user/main.c
++
Use a better interface for random numbers than rand * 16.
Cc: Laurent Vivier
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
linux-user/elfload.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/linux-user/elfload.c b/linux-user/elfload.c
ind
The random number is intended for use by the guest. As such, we should
honor the -seed argument for reproducibility. Use the *_nofail routine
instead of rolling our own error handling locally.
Cc: qemu-...@nongnu.org
Cc: Andrew Jeffery
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Cédric Le
Using uint8_t* merely requires useless casts for use with
other types to be filled with randomness.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Richard Henderson
---
include/crypto/random.h | 2 +-
crypto/random-gcrypt.c | 2 +-
crypto/random-gnutls.c
Avoids leaking the /dev/urandom fd into any child processes.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Richard Henderson
---
crypto/random-platform.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/crypto/random-platform.c b/cryp
Use a better interface for random numbers than rand().
Fail gracefully if for some reason we cannot use the crypto system.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Gerd Hoffmann
Reviewed-by: Daniel P. Berrangé
Signed-off-by: Richard Henderson
---
v2: Use qcrypto_random_bytes, not qemu_
When the -seed option is given, call qemu_guest_random_seed_main,
putting the subsystem into deterministic mode. Pass derived seeds
to each cpu created; which is a no-op unless the subsystem is in
deterministic mode.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Daniel P. Berrangé
Signed-off
This routine is intended to produce high-quality random numbers to the
guest. Normally, such numbers are crypto quality from the host, but a
command-line option can force the use of a fully deterministic sequence
for use while debugging.
Reviewed-by: Philippe Mathieu-Daudé
Reviewed-by: Daniel P.
This allows us to use a single syscall to initialize them all.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Richard Henderson
---
target/arm/cpu.h | 12 +++-
linux-user/aarch64/cpu_loop.c | 6 +-
linux-user/syscall.c | 10 +-
target/arm/helper.c
1 - 100 of 278 matches
Mail list logo
