On 5/5/20 12:24 PM, Huacai Chen wrote:
The description of "make check" is out-of-date, so fix it by adding
block and softfloat.
Reviewed-by: Claudio Fontana
Signed-off-by: Huacai Chen
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
On Fri, 10 Apr 2020 19:46:35 +0800
Dongjiu Geng wrote:
> Record the GHEB address via fw_cfg file, when recording
> a error to CPER, it will use this address to find out
> Generic Error Data Entries and write the error.
>
> In order to avoid migration failure, make hardware
> error table address
On 30.04.20 12:19, Denis Plotnikov wrote:
> v23:
>Undecided: whether to add zstd(zlib) compression
> details to the qcow2 spec
>03: tighten assertion on zstd decompression [Eric]
>04: use _rm_test_img appropriately [Max]
Thanks, applied to my block branch:
On Fri, 10 Apr 2020 19:46:34 +0800
Dongjiu Geng wrote:
> This patch builds Hardware Error Source Table(HEST) via fw_cfg blobs.
> Now it only supports ARMv8 SEA, a type of Generic Hardware Error
> Source version 2(GHESv2) error source. Afterwards, we can extend
> the supported types if needed.
уторак, 05. мај 2020., Huacai Chen је написао/ла:
> The description of "make check" is out-of-date, so fix it by adding
> block and softfloat.
>
> Signed-off-by: Huacai Chen
> ---
Reviewed-by: Aleksandar Markovic
> tests/Makefile.include | 2 +-
> 1 file changed, 1 insertion(+), 1
usbback_portid_add() leaks the error when qdev_device_add() fails.
Fix that. While there, use the error to improve the error message.
The qemu_opts_from_qdict() similarly leaks on failure. But any
failure there is a programming error. Pass _abort.
Fixes:
The description of "make check" is out-of-date, so fix it by adding
block and softfloat.
Reviewed-by: Claudio Fontana
Signed-off-by: Huacai Chen
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/Makefile.include b/tests/Makefile.include
index
nvdimm_set_uuid() leaks memory on qemu_uuid_parse() failure. Fix
that.
Fixes: 6c5627bb24dcd68c997857a8b671617333b1289f
Cc: Xiao Guangrong
Cc: Shivaprasad G Bhat
Signed-off-by: Markus Armbruster
---
hw/mem/nvdimm.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/hw/mem/nvdimm.c
The Error ** argument must be NULL, _abort, _fatal, or a
pointer to a variable containing NULL. Passing an argument of the
latter kind twice without clearing it in between is wrong: if the
first call sets an error, it no longer points to NULL for the second
create_cps() is wrong that way. The
On Fri, 10 Apr 2020 19:46:31 +0800
Dongjiu Geng wrote:
> RAS Virtualization feature is not supported now, so
> add a RAS machine option and disable it by default.
>
> Reviewed-by: Peter Maydell
> Signed-off-by: Dongjiu Geng
> Signed-off-by: Xiang Zheng
> Reviewed-by: Jonathan Cameron
Commit e47970f51d "s390x/cpumodel: Fix query-cpu-model-FOO error API
violations" neglected to change visit_check_struct()'s Error **
argument along with the others. If visit_check_struct() failed, we'd
take the success path. Fortunately, it can't fail here:
qobject_input_check_struct() checks we
Cc: Peter Maydell
Cc: Jean-Christophe Dubois
Signed-off-by: Markus Armbruster
Reviewed-by: Philippe Mathieu-Daudé
---
hw/arm/sabrelite.c | 7 +--
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/hw/arm/sabrelite.c b/hw/arm/sabrelite.c
index e31694bb92..04f4b96591 100644
---
The Error ** argument must be NULL, _abort, _fatal, or a
pointer to a variable containing NULL. Passing an argument of the
latter kind twice without clearing it in between is wrong: if the
first call sets an error, it no longer points to NULL for the second
call.
boston_mach_init() is wrong that
Replace
error_report("...: %s", ..., error_get_pretty(err));
by
error_reportf_err(err, "...: ", ...);
One of the replaced messages lacked a colon. Add it.
Signed-off-by: Markus Armbruster
Reviewed-by: Eric Blake
Reviewed-by: Philippe Mathieu-Daudé
---
chardev/char-socket.c | 5
migrate_get_socket_address() neglects to check
visit_type_SocketAddressList() failure. This smells like a leak, but
it actually will crash dereferencing @addrs. Pass _abort to
remove the code smell.
Signed-off-by: Markus Armbruster
---
tests/qtest/migration-test.c | 4 ++--
1 file changed, 2
The Error ** argument must be NULL, _abort, _fatal, or a
pointer to a variable containing NULL. Passing an argument of the
latter kind twice without clearing it in between is wrong: if the
first call sets an error, it no longer points to NULL for the second
call.
x86_cpu_load_model() is wrong
v2:
* PATCH 2: missing return [Paul]
* PATCH 3: commit message typo [David]
* PATCH 5: error message tidied up [Eric, Philippe]
* PATCH 7: commit message pasto
* Old PATCH 4 dropped [Matthew]
Cc: Paul Durrant
Cc: David Hildenbrand
Cc: Eric Blake
Cc: Philippe Mathieu-Daudé
Markus Armbruster
Fixes: df1d8a1f29f567567b9d20be685a4241282e7005
Cc: Paul Burton
Cc: Aleksandar Rikalo
Signed-off-by: Markus Armbruster
---
hw/mips/boston.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/mips/boston.c b/hw/mips/boston.c
index 2832dfa6ae..a896056be1 100644
---
Hi Eric,
On Tue, May 5, 2020 at 3:16 PM Bharat Bhushan wrote:
>
> hi Eric,
>
> On Tue, May 5, 2020 at 3:00 PM Auger Eric wrote:
> >
> > Hi Bharat,
> >
> > On 5/5/20 11:25 AM, Bharat Bhushan wrote:
> > > Hi Eric,
> > >
> > > On Fri, Apr 24, 2020 at 7:47 PM Auger Eric wrote:
> > >>
> > >> Hi
On Tue, 5 May 2020 04:14:41 +0530
Kirti Wankhede wrote:
> VM state change handler gets called on change in VM's state. This is used to
> set
> VFIO device state to _RUNNING.
>
> Signed-off-by: Kirti Wankhede
> Reviewed-by: Neo Jia
> ---
> hw/vfio/migration.c | 87
>
On Tue, 5 May 2020 at 11:09, Jan Kiszka wrote:
>
> On 05.05.20 11:59, Philippe Mathieu-Daudé wrote:
> I don't recall details anymore either (more than 10 year ago now...),
> but this looks reasonable.
My guess is that it dates back to when the serial code would
crash if passed a NULL pointer for
уторак, 05. мај 2020., chen huacai је написао/ла:
> Hi, Aleksandar,
>
> On Sun, May 3, 2020 at 6:50 PM Aleksandar Markovic
> wrote:
> >
> > нед, 3. мај 2020. у 12:21 Huacai Chen је
> написао/ла:
> > >
> > > Loongson-3 CPU family include Loongson-3A R1/R2/R3/R4 and Loongson-3B
> > > R1/R2.
On 05/05/20 12:07, Philippe Mathieu-Daudé wrote:
> Use the generic AUDIO_HOST_ENDIANNESS definition instead
> of a custom one.
>
> Signed-off-by: Philippe Mathieu-Daudé
> ---
> Who/what machine is using this device anyway?
PC, like all old ISA audio cards.
Paolo
On 05.05.20 11:59, Philippe Mathieu-Daudé wrote:
I can't find proper documentation or datasheet, but it is likely
a MMIO mapped serial device mapped in the 0x8000..0x8000
range belongs to the SoC address space, thus is always mapped in
the memory bus.
Map the devices on the bus
Am 30.04.2020 um 16:27 hat Kevin Wolf geschrieben:
> v2:
> - Fixed iotest 283
> - Corrected commit message for patch 3 [Vladimir]
> - Fixed permissions for the source node, too
> - Refactored the test case to avoid some duplication [Vladimir]
Thanks for the review, applied to the block branch.
Use the generic AUDIO_HOST_ENDIANNESS definition instead
of a custom one.
Signed-off-by: Philippe Mathieu-Daudé
---
Who/what machine is using this device anyway?
---
hw/audio/gus.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/hw/audio/gus.c b/hw/audio/gus.c
index
Hi, Philippe,
On Tue, May 5, 2020 at 5:33 PM Philippe Mathieu-Daudé wrote:
>
> On 5/5/20 9:29 AM, Huacai Chen wrote:
> > The description of "make check" is out-of-date, so fix it by adding
> > block and softfloat.
> >
> > Signed-off-by: Huacai Chen
> > ---
> > tests/Makefile.include | 2 +-
>
Am 30.04.2020 um 20:21 hat Vladimir Sementsov-Ogievskiy geschrieben:
> 30.04.2020 17:27, Kevin Wolf wrote:
> > Since the introduction of a backup filter node in commit 00e30f05d, the
> > backup block job crashes when the target image is smaller than the
> > source image because it will try to
I can't find proper documentation or datasheet, but it is likely
a MMIO mapped serial device mapped in the 0x8000..0x8000
range belongs to the SoC address space, thus is always mapped in
the memory bus.
Map the devices on the bus regardless a chardev is attached to it.
Signed-off-by:
On 5/5/20 10:23 AM, Laurent Vivier wrote:
On 05/05/2020 10:00, Laurent Vivier wrote:
On 04/05/2020 11:46, Philippe Mathieu-Daudé wrote:
In nvme_create_queue_pair() we create a page list using
qemu_blockalign(), then map it with qemu_vfio_dma_map():
q->prp_list_pages = qemu_blockalign0(bs,
On Mon, 4 May 2020 at 17:03, Richard Henderson
wrote:
>
> On 5/4/20 2:43 AM, Peter Maydell wrote:
> > I've reviewed patch 13, but I still don't understand why you've
> > made the size-related changes in patch 4, so I've continued
> > our conversation in the thread on the v3 version of that patch.
hi Eric,
On Tue, May 5, 2020 at 3:00 PM Auger Eric wrote:
>
> Hi Bharat,
>
> On 5/5/20 11:25 AM, Bharat Bhushan wrote:
> > Hi Eric,
> >
> > On Fri, Apr 24, 2020 at 7:47 PM Auger Eric wrote:
> >>
> >> Hi Bharat,
> >>
> >> On 4/2/20 11:01 AM, Bharat Bhushan wrote:
> >>> Hi Eric/Alex,
> >>>
>
Am 30.04.2020 um 15:30 hat Kevin Wolf geschrieben:
> What I was really investigating is why 055 was so slow. I couldn't solve
> that, but instead I found out that our VMDK code for zero clusters and
> write_zeroes was completely broken. Apart from segfaults when zero
> clusters were actually
On Tue, 5 May 2020 04:14:40 +0530
Kirti Wankhede wrote:
> - Migration functions are implemented for VFIO_DEVICE_TYPE_PCI device in this
> patch series.
I would drop this sentence; people looking at this patch in the future
are unlikely to care.
> - VFIO device supports migration or not is
On 5/5/20 7:48 AM, Klaus Jensen wrote:
From: Klaus Jensen
Changes since v5
No functional changes, just updated Reviewed-by tags. Also, I screwed up
the CC list when sending v4.
Philippe and Keith, please add a Reviewed-by to
* "nvme: factor out pmr setup" and
* "do
On 5/5/20 9:29 AM, Huacai Chen wrote:
The description of "make check" is out-of-date, so fix it by adding
block and softfloat.
Signed-off-by: Huacai Chen
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/Makefile.include
Hi Bharat,
On 5/5/20 11:25 AM, Bharat Bhushan wrote:
> Hi Eric,
>
> On Fri, Apr 24, 2020 at 7:47 PM Auger Eric wrote:
>>
>> Hi Bharat,
>>
>> On 4/2/20 11:01 AM, Bharat Bhushan wrote:
>>> Hi Eric/Alex,
>>>
-Original Message-
From: Alex Williamson
Sent: Thursday, March 26,
Hi Eric,
On Fri, Apr 24, 2020 at 7:47 PM Auger Eric wrote:
>
> Hi Bharat,
>
> On 4/2/20 11:01 AM, Bharat Bhushan wrote:
> > Hi Eric/Alex,
> >
> >> -Original Message-
> >> From: Alex Williamson
> >> Sent: Thursday, March 26, 2020 11:23 PM
> >> To: Auger Eric
> >> Cc: Bharat Bhushan ;
Patchew URL:
https://patchew.org/QEMU/20200504142125.31180-1-edgar.igles...@gmail.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200504142125.31180-1-edgar.igles...@gmail.com
Subject: [PATCH v2 0/1] target/arm: Remove
Am 05.05.2020 um 11:16 hat Alberto Garcia geschrieben:
> On Tue 05 May 2020 10:54:12 AM CEST, Kevin Wolf wrote:
> > But I think there is a more important problem with the test: It seems
> > to pass even with old binaries that don't have the fix. Is this only
> > on my system or do you get the
Patchew URL: https://patchew.org/QEMU/20200504131959.9533-1-mlevi...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
On Tue 05 May 2020 10:54:12 AM CEST, Kevin Wolf wrote:
> But I think there is a more important problem with the test: It seems
> to pass even with old binaries that don't have the fix. Is this only
> on my system or do you get the same?
With old binaries when qcow2_cluster_zeroize() is called it
Am 05.05.2020 um 10:54 hat Kevin Wolf geschrieben:
> Am 04.05.2020 um 19:07 hat Alberto Garcia geschrieben:
> > On Mon 04 May 2020 06:01:19 PM CEST, Eric Blake wrote:
> > >> +_supported_fmt qcow2
> > >> +_supported_proto file
> > >
> > > Do we have to limit it to qcow2 and file? Yes, it's testing
On Tue, May 05, 2020 at 04:59:40PM +0800, Chen Qun wrote:
> We can delete the redundant type conversion if
> we set the the AES_KEY parameter with 'const' in
> qcrypto_cipher_aes_ecb_(en|de)crypt() function.
>
> Reported-by: Euler Robot
> Signed-off-by: Chen Qun
> ---
> v1->v2:
> Cc: "Daniel P.
Patchew URL: https://patchew.org/QEMU/20200505090136.341426-1-j...@jms.id.au/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
export
On Fri, Apr 24, 2020 at 7:22 PM Auger Eric wrote:
>
> Hi Bharat,
> On 4/23/20 6:09 PM, Jean-Philippe Brucker wrote:
> > Hi Bharat,
> >
> > A few more things found while rebasing
> >
> > On Mon, Mar 23, 2020 at 02:16:16PM +0530, Bharat Bhushan wrote:
> >> This patch implements the PROBE request.
The AST2600 handles this differently with the extra 'hardlock' state, so
move the testing to the soc specific class' write callback.
Signed-off-by: Joel Stanley
---
hw/misc/aspeed_sdmc.c | 55 +++
1 file changed, 45 insertions(+), 10 deletions(-)
diff
We can delete the redundant type conversion if
we set the the AES_KEY parameter with 'const' in
qcrypto_cipher_aes_ecb_(en|de)crypt() function.
Reported-by: Euler Robot
Signed-off-by: Chen Qun
---
v1->v2:
Cc: "Daniel P. Berrangé"
Modify the AES_KEY parameter with 'const' in
Am 04.05.2020 um 19:07 hat Alberto Garcia geschrieben:
> On Mon 04 May 2020 06:01:19 PM CEST, Eric Blake wrote:
> >> +_supported_fmt qcow2
> >> +_supported_proto file
> >
> > Do we have to limit it to qcow2 and file? Yes, it's testing a bugfix
> > for qcow2, but are there other formats that it
On Tue, May 05, 2020 at 10:11:03 +0200, Kevin Wolf wrote:
> Am 03.04.2020 um 19:58 hat Eric Blake geschrieben:
> > Creating an image that requires format probing of the backing image is
> > inherently unsafe (we've had several CVEs over the years based on
> > probes leaking information to the
Le 04/05/2020 à 17:29, Philippe Mathieu-Daudé a écrit :
> This is the first part of a series reducing user-mode
> dependencies. By stripping out unused code, the build
> and testing time is reduced (as is space used by objects).
>
> Part 1 (generic):
> - reduce user-mode object list
> - remove
Patchew URL: https://patchew.org/QEMU/20200504155217.10325-1-be...@igalia.com/
Hi,
This series failed build test on FreeBSD host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit that
Patchew URL: https://patchew.org/QEMU/20200504152922.21365-1-phi...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Patchew URL:
https://patchew.org/QEMU/1588601168-27576-1-git-send-email-sai.pavan.bo...@xilinx.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 1588601168-27576-1-git-send-email-sai.pavan.bo...@xilinx.com
Subject: [PATCH v2
Patchew URL:
https://patchew.org/QEMU/20200504151438.362702-1-stefa...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Patchew URL:
https://patchew.org/QEMU/20200504151438.362702-1-stefa...@redhat.com/
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
Patchew URL:
https://patchew.org/QEMU/20200504151438.362702-1-stefa...@redhat.com/
Hi,
This series failed the docker-quick@centos7 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
Patchew URL: https://patchew.org/QEMU/20200504144352.23021-1-phi...@redhat.com/
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 ===
Patchew URL:
https://patchew.org/QEMU/20200504151438.362702-1-stefa...@redhat.com/
Hi,
This series failed build test on FreeBSD host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit
Patchew URL: https://patchew.org/QEMU/20200504144125.22435-1-phi...@redhat.com/
Hi,
This series failed the asan build test. Please find the testing commands and
their output below. If you have Docker installed, you can probably reproduce it
locally.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
Patchew URL: https://patchew.org/QEMU/87tv0vzrwj@dusky.pond.sub.org/
Hi,
This series failed the docker-quick@centos7 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 ===
Patchew URL: https://patchew.org/QEMU/87tv0vzrwj@dusky.pond.sub.org/
Hi,
This series failed build test on FreeBSD host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit that has
On 05/05/2020 10:00, Laurent Vivier wrote:
> On 04/05/2020 11:46, Philippe Mathieu-Daudé wrote:
>> In nvme_create_queue_pair() we create a page list using
>> qemu_blockalign(), then map it with qemu_vfio_dma_map():
>>
>> q->prp_list_pages = qemu_blockalign0(bs, s->page_size * NVME_QUEUE_SIZE);
Patchew URL:
https://patchew.org/QEMU/20200504142125.31180-1-edgar.igles...@gmail.com/
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
Patchew URL: https://patchew.org/QEMU/20200504142308.10446-1-be...@igalia.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200504142308.10446-1-be...@igalia.com
Subject: [PATCH v2] qcow2: Avoid integer wraparound in
Patchew URL:
https://patchew.org/QEMU/20200504123309.3808-1-peter.mayd...@linaro.org/
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
Patchew URL:
https://patchew.org/QEMU/20200504123309.3808-1-peter.mayd...@linaro.org/
Hi,
This series failed build test on FreeBSD host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a
Patchew URL:
https://patchew.org/QEMU/20200504132300.1ae883c1...@aeryn.lan.ktmba/
Hi,
This series failed build test on FreeBSD host. Please find the details below.
=== TEST SCRIPT BEGIN ===
#!/bin/bash
# Testing script will be invoked under the git checkout with
# HEAD pointing to a commit
Patchew URL: https://patchew.org/QEMU/20200504131959.9533-1-mlevi...@redhat.com/
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 ===
Patchew URL: https://patchew.org/QEMU/20200504131959.9533-1-mlevi...@redhat.com/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200504131959.9533-1-mlevi...@redhat.com
Subject: [PATCH v2] Fix iotest 153
Type: series
=== TEST
Am 03.04.2020 um 19:58 hat Eric Blake geschrieben:
> Creating an image that requires format probing of the backing image is
> inherently unsafe (we've had several CVEs over the years based on
> probes leaking information to the guest on a subsequent boot, although
> these days tools like libvirt
On 04/05/2020 11:46, Philippe Mathieu-Daudé wrote:
> In nvme_create_queue_pair() we create a page list using
> qemu_blockalign(), then map it with qemu_vfio_dma_map():
>
> q->prp_list_pages = qemu_blockalign0(bs, s->page_size * NVME_QUEUE_SIZE);
> r = qemu_vfio_dma_map(s->vfio,
On 5/5/20 9:29 AM, Huacai Chen wrote:
> The description of "make check" is out-of-date, so fix it by adding
> block and softfloat.
>
> Signed-off-by: Huacai Chen
> ---
> tests/Makefile.include | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/Makefile.include
Am 03.04.2020 um 19:58 hat Eric Blake geschrieben:
> The use of 'qemu-img amend' to change qcow2 backing files is not
> tested very well. In particular, our implementation has a bug where
> if a new backing file is provided without a format, then the prior
> format is blindly reused, even if this
Am 03.04.2020 um 19:58 hat Eric Blake geschrieben:
> qcow has no space in the metadata to store a backing format, and there
> are existing qcow images backed both by raw or by other formats
> (usually qcow) images, reliant on probing to tell the difference.
> While we don't recommend the creation
Hi, Aleksandar,
On Sun, May 3, 2020 at 6:50 PM Aleksandar Markovic
wrote:
>
> нед, 3. мај 2020. у 12:21 Huacai Chen је написао/ла:
> >
> > Loongson-3 CPU family include Loongson-3A R1/R2/R3/R4 and Loongson-3B
> > R1/R2. Loongson-3A R1 is the oldest and its ISA is the smallest, while
> >
The description of "make check" is out-of-date, so fix it by adding
block and softfloat.
Signed-off-by: Huacai Chen
---
tests/Makefile.include | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tests/Makefile.include b/tests/Makefile.include
index 03a74b6..5d32239 100644
---
>-Original Message-
>From: Daniel P. Berrangé [mailto:berra...@redhat.com]
>Sent: Monday, May 4, 2020 8:58 PM
>To: Chenqun (kuhn)
>Cc: qemu-devel@nongnu.org; Michael Tokarev ; qemu-
>triv...@nongnu.org; Laurent Vivier ; Euler Robot
>
>Subject: Re: [PULL 04/20] crypto: Redundant type
Thanks. I will test it.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1805256
Title:
qemu-img hangs on rcu_call_ready_event logic in Aarch64 when
converting images
Status in kunpeng920:
** Summary changed:
- Ubuntu 20.04 QEMU Failure with nested FreeBSD bhyve
+ Ubuntu 20.04 KVM / QEMU Failure with nested FreeBSD bhyve
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1876678
Title:
055 uses the backup block job to create a compressed backup of an
$IMGFMT image with both qcow2 and vmdk targets. However, cluster
allocation in vmdk is very slow because it flushes the image file after
each L2 update.
There is no reason why we need this level of safety in this test, so
let's
On 05/05/2020 15:50, David Gibson wrote:
> On Tue, May 05, 2020 at 10:56:17AM +1000, Alexey Kardashevskiy wrote:
>>
>>
>> On 04/05/2020 21:30, Greg Kurz wrote:
>>> On Fri, 17 Apr 2020 14:11:05 +1000
>>> Alexey Kardashevskiy wrote:
>>>
At the moment the VCPU init sequence includes setting
Hi Kirti,
On 5/5/20 12:44 AM, Kirti Wankhede wrote:
This function will be used for migration region.
Migration region is mmaped when migration starts and will be unmapped when
migration is complete.
Signed-off-by: Kirti Wankhede
Reviewed-by: Neo Jia
Reviewed-by: Cornelia Huck
---
On 5/4/20 9:23 PM, Richard Henderson wrote:
Do not explicitly store zero to the NEON high part
when we can pass !is_q to clear_vec_high.
Reviewed-by: Alex Bennée
Signed-off-by: Richard Henderson
---
Patch easier to review with 'git-diff --function-context'.
target/arm/translate-a64.c |
On 5/4/20 11:37 AM, Joel Stanley wrote:
> There are minimal differences from Qemu's point of view between the A0
> and A1 silicon revisions.
>
> As the A1 exercises different code paths in u-boot it is desirable to
> emulate that instead.
>
> Signed-off-by: Joel Stanley
Reviewed-by: Cédric Le
301 - 385 of 385 matches
Mail list logo
