Mark Cave-Ayland writes:
> On 18/05/2020 06:19, Markus Armbruster wrote:
>
>> This is the instrumentation mentioned in "[PATCH 00/24] Fixes around
>> device realization".
>>
>> PATCH 2/5 might have value on its own. You tell me.
>>
>> Shell script to smoke-test all machines:
>>
>> #!/bin/sh
>
Eric Blake writes:
> On 5/18/20 12:19 AM, Markus Armbruster wrote:
>> "info qom-tree" prints children in unstable order. This is a pain
>> when diffing output for different versions to find change. Print it
>> sorted.
>
> Yes, this does seem reasonable to include even without the rest of the
>
Philippe Mathieu-Daudé writes:
> On 5/18/20 12:39 PM, BALATON Zoltan wrote:
>> On Mon, 18 May 2020, Markus Armbruster wrote:
>>> sm501_init() and ati_vga_realize() create an "i2c-ddc" device, but
>>> neglect to realize it. Affects machines sam460ex, shix, r2d, and
>>> fulong2e.
>>>
>>> I wonder
BALATON Zoltan writes:
> On Mon, 18 May 2020, Markus Armbruster wrote:
>> sm501_init() and ati_vga_realize() create an "i2c-ddc" device, but
>> neglect to realize it. Affects machines sam460ex, shix, r2d, and
>> fulong2e.
>>
>> I wonder how this ever worked. If the "device becomes real only on
Cédric Le Goater writes:
> On 5/18/20 7:04 AM, Markus Armbruster wrote:
>> pnv_chip_power8_instance_init() creates a "pnv-psi-POWER8" sysbus
>> device in a way that leaves it unplugged.
>> pnv_chip_power9_instance_init() and pnv_chip_power10_instance_init()
>> do the same for "pnv-psi-POWER9" and
Cédric Le Goater writes:
> On 5/18/20 7:04 AM, Markus Armbruster wrote:
>> pnv_init() creates "power10_v1.0-pnv-chip", "power8_v2.0-pnv-chip",
>> "power8e_v2.1-pnv-chip", "power8nvl_v1.0-pnv-chip", or
>> "power9_v2.0-pnv-chip" sysbus devices in a way that leaves them
>> unplugged.
>>
>> pnv_chip
Mark Cave-Ayland writes:
> On 18/05/2020 06:03, Markus Armbruster wrote:
>
>> The devices we plug into the macio-bus are all sysbus devices
>> (DeviceClass member bus_type is TYPE_SYSTEM_BUS), but macio-bus does
>> not derive from TYPE_SYSTEM_BUS. Fix that.
>>
>> "info qtree" now shows the devi
BALATON Zoltan writes:
> On Mon, 18 May 2020, Markus Armbruster wrote:
>> object_property_set_bool(OBJECT(dev), true, "realized", ...) right
>> after qdev_init_nofail(dev) does nothing, because qdev_init_nofail()
>> already realizes. Drop.
>>
>> Cc: BALATON Zoltan
>
> Shouldn't this Cc line com
Mark Cave-Ayland writes:
> On 18/05/2020 06:03, Markus Armbruster wrote:
>
>> These devices go with the "via-pmu" device, which is controlled by
>> property "has-pmu". macio_newworld_init() creates it unconditionally,
>> because the property has not been set then. macio_newworld_realize()
>> re
On 18.05.2020 18:56, Alex Bennée wrote:
Philippe Mathieu-Daudé writes:
+ Alex
On 5/6/20 10:17 AM, Pavel Dovgalyuk wrote:
Sometimes virtual timer callbacks depend on order
of virtual timer processing and warping of virtual clock.
Therefore every callback should be logged to make replay dete
Hi all,
I want to understand, how we can differentiate the actual sound
card(PCI passthrough) and emulated sound card. Basically i want to check it
in qemu itself. Any suggestions?
On 18.05.2020 19:07, Alex Bennée wrote:
Pavel Dovgalyuk writes:
In record/replay icount mode main loop thread and vCPU thread
do not perform simultaneously. They take replay mutex to synchronize
the actions. Sometimes vCPU thread waits for locking the mutex for
very long time, because main l
Joel Stanley writes:
> On Mon, 18 May 2020 at 12:24, Cédric Le Goater wrote:
>>
>> On 5/18/20 7:03 AM, Markus Armbruster wrote:
>> > The number of CPUs is controlled by property "num-cpus".
>> > aspeed_soc_ast2600_init() creates the maximum supported number.
>> > aspeed_soc_ast2600_realize() rea
"Andrew Jeffery" writes:
> On Mon, 18 May 2020, at 21:49, Cédric Le Goater wrote:
>> On 5/18/20 7:03 AM, Markus Armbruster wrote:
>> > These devices are optional, and controlled by @nb_nics.
>> > aspeed_soc_ast2600_init() and aspeed_soc_init() create the maximum
>> > supported number. aspeed_soc
On 18.05.2020 19:14, Alex Bennée wrote:
Pavel Dovgalyuk writes:
This patch fixes shift=auto when record/replay is enabled.
Now user does not need to guess the best shift value.
Signed-off-by: Pavel Dovgalyuk
---
cpus.c |4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --
Joel Stanley writes:
> On Mon, 18 May 2020 at 12:19, Cédric Le Goater wrote:
>>
>> On 5/18/20 7:03 AM, Markus Armbruster wrote:
>> > These devices are optional, and controlled by @nb_nics.
>> > aspeed_soc_ast2600_init() and aspeed_soc_init() create the maximum
>> > supported number. aspeed_soc_
Philippe Mathieu-Daudé writes:
> On 5/18/20 12:30 PM, Peter Maydell wrote:
>> On Mon, 18 May 2020 at 06:04, Markus Armbruster wrote:
>>>
>>> xlnx_dp_init() creates these two devices, but they're never realized.
>>> Affects machine xlnx-zcu102.
>>>
>>> I wonder how this ever worked. If the "devi
Fred Konrad writes:
> Le 5/18/20 à 7:03 AM, Markus Armbruster a écrit :
>> xlnx_dp_init() creates these two devices, but they're never realized.
>> Affects machine xlnx-zcu102.
>>
>> I wonder how this ever worked. If the "device becomes real only on
>> realize" thing actually works, then we've a
Alistair Francis writes:
> On Sun, May 17, 2020 at 10:06 PM Markus Armbruster wrote:
>>
>> stm32f405_soc_initfn() creates six such devices, but
>> stm32f405_soc_realize() realizes only one. Affects machine
>> netduinoplus2.
>>
>> I wonder how this ever worked. If the "device becomes real only
Cédric Le Goater writes:
> On 5/18/20 3:17 PM, Markus Armbruster wrote:
>> Paolo Bonzini writes:
>>
>>> On 15/05/20 07:58, Markus Armbruster wrote:
Philippe Mathieu-Daudé writes:
> Remove unnecessary casts using coccinelle scripts.
>
> The CPU()/OBJECT() patches don't int
On 5/17/20 4:01 AM, Philippe Mathieu-Daudé wrote:
> Fix OUTL instructions incorrectly displayed as OUTW.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> target/i386/misc_helper.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Richard Henderson
as far as it goes. We sh
Thank you very much, Kirti and Yan!
On 2020/5/18 11:36, Yan Zhao wrote:
> On Mon, May 18, 2020 at 10:39:52AM +0800, Xiang Zheng wrote:
>> Hi Kirti and Yan,
>>
>> How can I test this patch series on my SR-IOV devices?
>> I have looked through Yan's pathes for i40e VF live migration support:
>>
Mirror the signal frame by storing all of the registers
as a lump. Use the signal macros to pull out the values.
Signed-off-by: Richard Henderson
---
risu_reginfo_aarch64.h | 16 +
risu_reginfo_aarch64.c | 135 +
2 files changed, 73 insertions(+), 78
Adjust some of the aarch64 code to look at the reginfo struct
instead of looking at test_sve, so that we do not need to pass
the --test-sve option in order to dump sve trace files.
Signed-off-by: Richard Henderson
---
risu.h | 1 +
risu.c | 108 +
Rather than doing some work in the signal handler and
some work outside, move all of the non-resume work outside.
This works because we arranged for RES_OK to be 0, which
is the normal return from sigsetjmp.
Signed-off-by: Richard Henderson
---
risu.c | 50 ---
Sanity check that we're not getting out of sync with
the trace stream. This will be especially bad with
the change in size of the sve save data.
Signed-off-by: Richard Henderson
---
risu.h| 8 ++-
reginfo.c | 160 --
risu.c| 6 ++
For trace, master of course must write to the file we create.
For sockets, we can report mismatches from either end. At present,
we are reporting mismatches from master. Reverse that so that we
report mismatches from the apprentice, just as we do for trace.
Signed-off-by: Richard Henderson
---
By remembering the specific comparison that failed, we do not
have to try again when it comes time to report. This makes
the mem_used flag redundant. Also, packet_mismatch is now
redundant with RES_BAD_IO.
This means that the only thing that report_match_status does
is to report on register stat
This will allow dumping of SVE frames without having
to know the SVE vector length beforehand.
Signed-off-by: Richard Henderson
---
risu.h | 2 +-
reginfo.c | 6 +++---
risu_reginfo_aarch64.c | 4 ++--
risu_reginfo_arm.c | 2 +-
risu_reginfo_i386.c| 2 +-
ris
Do not pass status like RES_BAD_IO from apprentice to master.
This means that when master reports i/o error that we know it
came from master; the apprentice will report its own i/o error.
Signed-off-by: Richard Henderson
---
reginfo.c | 11 +--
1 file changed, 5 insertions(+), 6 deletion
Some of the time we exit via the return value from main.
This can make it easier to tell what it is we're returning.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
comms.c| 26 +-
risu.c | 22 +++---
risu_r
Formalize the set of defines, plus -1, into an enum.
Signed-off-by: Richard Henderson
---
risu.h | 23 +++
reginfo.c | 32 +++-
risu_aarch64.c | 6 +++---
risu_arm.c | 6 +++---
risu_i386.c| 4 ++--
risu_m68k.c| 4 ++--
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
risu.h| 3 ++-
reginfo.c | 2 +-
risu.c| 8
3 files changed, 7 insertions(+), 6 deletions(-)
diff --git a/risu.h b/risu.h
index 8d2d646..e2b4508 100644
--- a/risu.h
+++ b/risu.h
@@ -17,6 +17,7 @@
#include
#inclu
Push the trace check down from the function calling the reginfo
function down into the i/o function. This means we don't have
to pass a function pointer.
Return a RisuResult from the i/o functions. This fixes a minor bug
in send_register_info (even before the conversion to RisuResult),
which ret
Formalize the random set of numbers into an enum. Doing this
makes it easy to see that one of the responses in
recv_and_compare_register_info was inconsistent.
Signed-off-by: Richard Henderson
---
risu.h| 25 +
reginfo.c | 32
risu.c
We will want to share this code with --dump.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
risu.c | 37 +
1 file changed, 17 insertions(+), 20 deletions(-)
diff --git a/risu.c b/risu.c
index 059348f..1c66885 100644
--- a/risu.c
+++ b/risu.c
Any one invocation cannot be both master and apprentice.
Let's use only one variable for the file descriptor.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
risu.c | 40
1 file changed, 20 insertions(+), 20 deletions(-)
diff --git a/ris
These are unused in other translation units.
Signed-off-by: Richard Henderson
---
risu.c | 24
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/risu.c b/risu.c
index 979341c..24ada8f 100644
--- a/risu.c
+++ b/risu.c
@@ -31,18 +31,18 @@
void *memblock;
Truncate the new output file. Rely on umask to remove
group+other file permissions, if desired.
Reviewed-by: Peter Maydell
Signed-off-by: Richard Henderson
---
risu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/risu.c b/risu.c
index 1c66885..f404d8f 100644
--- a/risu.c
This patch set does alter the format of the trace files, and thus
means we'll have to re-generate these. However, the space saved
for sve trace files is significant, so I consider it worthwhile.
In addition, the new --dump option allows one to inspect the
contents of the trace file.
Version 2 ad
> -Original Message-
> From: Alessandro Di Federico
> Sent: Monday, May 18, 2020 4:15 PM
> To: qemu-devel@nongnu.org Developers
> Cc: Taylor Simpson ; Niccolò Izzo ;
> Brian Cain
> Subject: Simplifying the Hexagon frontend
>
> Hi, this e-mail is intended to bootstrap a public discussio
Public bug reported:
Hi Expert:
The VM is hung here after (2, or 3, or 5 and the longest time is 10 hours) by
qemu-kvm.
Notes:
for VM:
OS: RHEL 7.6
CPU: 1
MEM:4G
For qemu-kvm:
1) version:
/usr/libexec/qemu-kvm -version
QEMU emulator version 2.10.0(qemu-kvm-ev-2.10.0-21.el7_5.4
> Can we make it a run-time value instead?
It's definitely possible, but will require a bit of refactoring. How
about for now I set a reasonable maximum which is supported by all
platforms (32)? That still increases it a lot from 8, and we can
figure out how best increase it even more for other ta
On Mon, 18 May 2020 at 12:24, Cédric Le Goater wrote:
>
> On 5/18/20 7:03 AM, Markus Armbruster wrote:
> > The number of CPUs is controlled by property "num-cpus".
> > aspeed_soc_ast2600_init() creates the maximum supported number.
> > aspeed_soc_ast2600_realize() realizes only the wanted number.
On Mon, 18 May 2020 at 12:19, Cédric Le Goater wrote:
>
> On 5/18/20 7:03 AM, Markus Armbruster wrote:
> > These devices are optional, and controlled by @nb_nics.
> > aspeed_soc_ast2600_init() and aspeed_soc_init() create the maximum
> > supported number. aspeed_soc_ast2600_realize() and
> > aspe
On 5/18/20 3:33 PM, Vladimir Sementsov-Ogievskiy wrote:
> 18.05.2020 21:23, John Snow wrote:
>>
>>
>> On 5/18/20 2:14 PM, Vladimir Sementsov-Ogievskiy wrote:
>>> 14.05.2020 08:53, John Snow wrote:
move python/qemu/*.py to python/qemu/lib/*.py.
To create a namespace package, the 'q
On Mon, 18 May 2020, at 21:49, Cédric Le Goater wrote:
> On 5/18/20 7:03 AM, Markus Armbruster wrote:
> > These devices are optional, and controlled by @nb_nics.
> > aspeed_soc_ast2600_init() and aspeed_soc_init() create the maximum
> > supported number. aspeed_soc_ast2600_realize() and
> > asp
Patchew URL:
https://patchew.org/QEMU/20200518122041.10694-1-mlevi...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200518122041.10694-1-mlevi...@redhat.com
Subject: [PATCH v7 00/14] LUKS: encryption slot management
On Mon, 18 May 2020 11:26:34 +0530
Kirti Wankhede wrote:
> VFIO_IOMMU_DIRTY_PAGES ioctl performs three operations:
> - Start dirty pages tracking while migration is active
> - Stop dirty pages tracking.
> - Get dirty pages bitmap. Its user space application's responsibility to
> copy content of
NUMA nodes corresponding to GPU memory currently have the same
affinity/distance as normal memory nodes. Add a third NUMA associativity
reference point enabling us to give GPU nodes more distance.
This is guest visible information, which shouldn't change under a
running guest across migration betw
Make the number of NUMA associativity reference points a
machine-specific value, using the currently assumed default (two
reference points). This preps the next patch to conditionally change it.
Signed-off-by: Reza Arbab
---
hw/ppc/spapr.c | 6 +-
include/hw/ppc/spapr.h | 1 +
2 file
On 5/13/20 10:49 PM, John Snow wrote:
Give block-dirty-bitmap-populate a workout.
Signed-off-by: John Snow
---
tests/qemu-iotests/287 | 242 ++
tests/qemu-iotests/287.out | 4544
Sheesh, that output file is a workout indeed.
tests/qemu-iotests/g
Hi, this e-mail is intended to bootstrap a public discussion on how to
improve the Hexagon frontend implementation. At rev.ng, Niccolò and I,
developed an Hexagon frontend, and we're (finally!) joining forces with
the QuIC guys to merge our efforts (did you see our talk [1]?).
The status is as fol
On 5/13/20 10:49 PM, John Snow wrote:
This is a new job-creating command.
Signed-off-by: John Snow
---
qapi/block-core.json | 18 +++
qapi/transaction.json | 2 ++
blockdev.c| 74 +++
3 files changed, 94 insertions(+)
diff --gi
On 5/18/20 12:19 AM, Markus Armbruster wrote:
"info qom-tree" prints children in unstable order. This is a pain
when diffing output for different versions to find change. Print it
sorted.
Yes, this does seem reasonable to include even without the rest of the
series.
Signed-off-by: Markus
Include actions for --add, --remove, --clear, --enable, --disable, and
--merge (note that --clear is a bit of fluff, because the same can be
accomplished by removing a bitmap and then adding a new one in its
place, but it matches what QMP commands exist). Listing is omitted,
because it does not re
Upcoming patches want to add some basic bitmap manipulation abilities
to qemu-img. But blockdev.o is too heavyweight to link into qemu-img
(among other things, it would drag in block jobs and transaction
support - qemu-img does offline manipulation, where atomicity is less
important because there
Upcoming patches will enhance bitmap support in qemu-img, but in doing
so, it turns out to be nice to suppress output when persistent bitmaps
make no sense (such as on a qcow2 v2 image). Add a hook to make this
easier to query.
This patch adds a new callback .bdrv_supports_persistent_dirty_bitmap
On 5/13/20 10:49 PM, John Snow wrote:
They have the same fields -- rename it BlockJobState.
This says BlockJobState...
Signed-off-by: John Snow
---
blockdev.c | 30 --
1 file changed, 12 insertions(+), 18 deletions(-)
diff --git a/blockdev.c b/blockdev.c
inde
The next patch will split blockdev.c, which will require accessing
some previously-static functions from more than one .c file. But part
of promoting a function to public is picking a naming scheme that does
not reek of exposing too many internals (two of the three functions
were named starting wi
On 18/05/2020 06:19, Markus Armbruster wrote:
> This is the instrumentation mentioned in "[PATCH 00/24] Fixes around
> device realization".
>
> PATCH 2/5 might have value on its own. You tell me.
>
> Shell script to smoke-test all machines:
>
> #!/bin/sh
> success=0
> fail=0
> ulimit -c 0
> gi
Dirty bitmaps are important to incremental backups, including exposure
over NBD where I'm already maintainer. Also, I'm aware that lately I
have been doing as much code/review on bitmaps as John Snow who is
trying to scale back in order to focus elsewhere; and many of the
recent patches have come
Missed in commit e13c59fa.
Signed-off-by: Eric Blake
Reviewed-by: Max Reitz
Message-Id: <20200513011648.166876-3-ebl...@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
qemu-img.c | 2 +-
qemu-img-cmds.hx | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/qem
We already list the subcommand summaries alphabetically, we should do
the same for the documentation related to subcommand-specific
parameters.
Signed-off-by: Eric Blake
Reviewed-by: Max Reitz
Message-Id: <20200513011648.166876-2-ebl...@redhat.com>
Reviewed-by: Vladimir Sementsov-Ogievskiy
---
The following changes since commit a28c9c8c9fc42484efe1bf5a77affe842e54e38b:
Merge remote-tracking branch 'remotes/kraxel/tags/vga-20200518-pull-request'
into staging (2020-05-18 16:37:09 +0100)
are available in the Git repository at:
https://repo.or.cz/qemu/ericb.git tags/pu
On 5/18/20 11:32 AM, Eric Blake wrote:
The following changes since commit debe78ce14bf8f8940c2bdf3ef387505e9e035a9:
Merge remote-tracking branch 'remotes/rth/tags/pull-fpu-20200515' into
staging (2020-05-15 19:51:16 +0100)
n
On 5/13/20 10:49 PM, John Snow wrote:
This job copies the allocation map into a bitmap. It's a job because
there's no guarantee that allocation interrogation will be quick (or
won't hang), so it cannot be retrofit into block-dirty-bitmap-merge.
retrofitted
It was designed with different poss
On 18/05/2020 06:04, Markus Armbruster wrote:
> This would have caught some of the bugs I just fixed.
>
> Signed-off-by: Markus Armbruster
> ---
> hw/core/qdev.c | 5 +
> 1 file changed, 5 insertions(+)
>
> diff --git a/hw/core/qdev.c b/hw/core/qdev.c
> index 9e5538aeae..0df995eb94 100644
On 18/05/2020 06:03, Markus Armbruster wrote:
> The devices we plug into the macio-bus are all sysbus devices
> (DeviceClass member bus_type is TYPE_SYSTEM_BUS), but macio-bus does
> not derive from TYPE_SYSTEM_BUS. Fix that.
>
> "info qtree" now shows the devices' mmio ranges, as it should
>
>
On 18/05/2020 06:03, Markus Armbruster wrote:
> macio_oldworld_init() creates a "macio-nvram", sysbus device, but
> neglects to but it on a bus.
>
> Put it on the macio bus. Affects machine g3beige. Visible in "info
> qtree":
>
> bus: macio.0
>type macio-bus
>
Create base class 'common secret'. Move common data and logic from
'secret' to 'common_secret' class. This allowed adding abstraction layer
for easier adding new 'secret' objects in future.
Convert 'secret' class to child from basic 'secret_common' with 'data'
and 'file' properties.
Signed-off-by:
On 5/15/20 7:40 AM, Vladimir Sementsov-Ogievskiy wrote:
Important thing for bitmap migration is to select destination block
node to obtain the migrated bitmap.
Prepatch, on source we use bdrv_get_device_or_node_name() to identify
the node, and on target we do bdrv_lookup_bs.
bdrv_get_device_or_n
Add tests:
test_secret_keyring_good;
test_secret_keyring_revoked_key;
test_secret_keyring_expired_key;
test_secret_keyring_bad_serial_key;
test_secret_keyring_bad_key_access_right;
Added tests require libkeyutils. The absence of this library is not
critical, because these tests will be s
On 18/05/2020 06:03, Markus Armbruster wrote:
> These devices go with the "via-pmu" device, which is controlled by
> property "has-pmu". macio_newworld_init() creates it unconditionally,
> because the property has not been set then. macio_newworld_realize()
> realizes it only when the property i
Add the ability for the secret object to obtain secret data from the
Linux in-kernel key managment and retention facility, as an extra option
to the existing ones: reading from a file or passing directly as a
string.
The secret is identified by the key serial number. The upper layers
need to insta
Add the ability to store encryption keys in the Linux keyring
facility.
For that, factor out common parts from secret to a new abstract class
secret_common, and introduce new user-creatable secret_keyring class
inheriting from it.
Use '--enable-keyring/--disable-keyring' configuration parameters
t
Machine file names should not have prefix "mips_".
Fuloong2e machine source file will be handled in a separate patch,
to avoid conflicts. That patch is pending integration into the
main tree.
Reviewed-by: Philippe Mathieu-Daudé
Signed-off-by: Aleksandar Markovic
---
MAINTAINERS
Achieves clearer code and slightly better performance.
Signed-off-by: Aleksandar Markovic
---
target/mips/helper.h | 6 ++-
target/mips/msa_helper.c | 79
target/mips/translate.c | 19 --
3 files changed, 93 insertions(+), 11 deletions(-)
d
Achieves clearer code and slightly better performance.
Signed-off-by: Aleksandar Markovic
---
target/mips/helper.h | 6 ++-
target/mips/msa_helper.c | 79
target/mips/translate.c | 19 --
3 files changed, 92 insertions(+), 12 deletions(-)
d
On 18/05/2020 06:03, Markus Armbruster wrote:
> mac_via_realize() creates a "mos6522-q800-via1" and a
> "mos6522-q800-via2" device, but neglects to realize them. Affects
> machine q800.
>
> I wonder how this ever worked. If the "device becomes real only on
> realize" thing actually works, then
The original coversion function is used for regular and MSA floating
point instructions handling. Since there are some nuanced differences
between regular and MSA floating point exception handling, provide two
instances of the conversion function, rather than just a single common
one. Inline both i
Use consistently 'l' and 'h' for low and high halves.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 62
1 file changed, 31 insertions(+), 31 deletions(-)
diff --git a/target/mips/fpu_helper.c b/target/m
After demacroing ., these macros
are not needed anymore.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 50
1 file changed, 50 deletions(-)
diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper.
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 44 +++-
1 file changed, 43 insertions(+),
Log the cases where a guest attempts read or write using bad
register offset.
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Signed-off-by: Aleksandar Markovic
---
hw/mips/mips_malta.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff --git a/hw/
After demacroing ., this macro is not
needed anymore.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 39 ---
1 file changed, 39 deletions(-)
diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper.c
in
After demacroing CLASS., this macro is not needed anymore.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 39 ---
1 file changed, 39 deletions(-)
diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper
After demacroing RINT., this macro is not needed anymore.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 13 -
1 file changed, 13 deletions(-)
diff --git a/target/mips/fpu_helper.c b/target/mips/fpu_helper.c
index dae1331f23..56ba49
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 37 -
1 file changed, 36 insertions(+), 1 d
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 70 ++--
1 file changed, 68 insertions(+),
Aleksandar Rikalo wants to use a different email address from
now on.
Reviewed-by: Aleksandar Rikalo
Reviewed-by: Philippe Mathieu-Daudé
Tested-by: Philippe Mathieu-Daudé
Signed-off-by: Aleksandar Markovic
---
.mailmap| 3 ++-
MAINTAINERS | 12 ++--
2 files changed, 8 insertions(
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 37 -
1 file changed, 36 insertions(+), 1 d
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 44 +++-
1 file changed, 43 insertions(+),
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 40 +++-
1 file changed, 39 insertions(+),
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 41 +++-
1 file changed, 40 insertions(+),
This series contains some pathces that split heprers in msa_helper.c.
It will make easier for debugging tools to display involved source
code, and also introduces some modest performance improvements gains
for all involved MSA instructions.
Also, this series contains mostly cosmetic FPU cleanups a
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 37 -
1 file changed, 36 insertions(+), 1 d
This is just a cosmetic change to enable tools like gcov, gdb,
callgrind, etc. to better display involved source code.
Reviewed-by: Aleksandar Rikalo
Signed-off-by: Aleksandar Markovic
---
target/mips/fpu_helper.c | 38 +-
1 file changed, 37 insertions(+), 1
On 5/15/20 6:23 AM, Daniel P. Berrangé wrote:
> On Fri, May 15, 2020 at 12:11:17PM +0200, Thomas Huth wrote:
>> On 07/04/2020 12.59, Philippe Mathieu-Daudé wrote:
>>> Hello,
>>>
>>> Following Markus thread on deprecating unmaintained (untested) code
>>> (machines) [1] and the effort done to gath
1 - 100 of 432 matches
Mail list logo