Patchew URL:
https://patchew.org/QEMU/20200430190122.4592-1-alex.ben...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200430190122.4592-1-alex.ben...@linaro.org
Subject: [PATCH v1 0/9] gdbstub/next
Type: series
Will be merged in 20.10 with qemu >=5.0 where this came upstream.
** Tags added: qemu-20.10
** Changed in: qemu (Ubuntu)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
On 01/05/2020 15:54, Leonardo Bras wrote:
> If SELinux is setup without 'execmem' permission for qemu, all mmap
> with (PROT_WRITE | PROT_EXEC) will fail and print a warning in
> SELinux log.
>
> If "nvlink2-mr" memory allocation fails (fist diff), it will cause
> guest NUMA nodes to not be
Patchew URL:
https://patchew.org/QEMU/20200430162813.17671-1-richard.hender...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200430162813.17671-1-richard.hender...@linaro.org
Subject: [PATCH v4 00/18] target/arm:
Patchew URL:
https://patchew.org/QEMU/20200501082806.205696-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
On Fri, 1 May 2020 at 09:28, Stefan Hajnoczi wrote:
>
> The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d:
>
> Merge remote-tracking branch
> 'remotes/edgar/tags/edgar/xilinx-next-2020-04-30.for-upstream' into staging
> (2020-04-30 16:47:23 +0100)
>
> are available
Thanks! I applied the patch, and now it works also inside the docker container,
for all architectures (i386, x86_64, arm, aarch64) for which I have test cases
at hand.
Indeed, since the container is configured by a public cloud service, there is
no possibility to change any security settings.
If SELinux is setup without 'execmem' permission for qemu, all mmap
with (PROT_WRITE | PROT_EXEC) will fail and print a warning in
SELinux log.
If "nvlink2-mr" memory allocation fails (fist diff), it will cause
guest NUMA nodes to not be correctly configured (V100 memory will
not be visible for
The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d:
Merge remote-tracking branch
'remotes/edgar/tags/edgar/xilinx-next-2020-04-30.for-upstream' into staging
(2020-04-30 16:47:23 +0100)
are available in the Git repository at:
https://github.com/stefanha/qemu.git
From: Alexander Bulekov
The fuzzers are built into a binary (e.g. qemu-fuzz-i386). To select the
device to fuzz/fuzz target, we usually use the --fuzz-target= argument.
This commit allows the fuzz-target to be specified using the name of the
executable. If the executable name ends with
On Thu, Apr 30, 2020 at 11:46:06AM -0400, Igor Mammedov wrote:
> Since 5.0 QEMU uses hostmem backend for allocating main guest RAM.
> The backend however calls mbind() which is typically NOP
> in case of default policy/absent host-nodes bitmap.
> However when runing in container with black-listed
From: Daniel Brodsky
- __COUNTER__ doesn't work with ## concat
- replaced ## with glue() macro so __COUNTER__ is evaluated
Fixes: 3284c3ddc4
Signed-off-by: Daniel Brodsky
Message-id: 20200404042108.389635-2-dnbrd...@gmail.com
Signed-off-by: Stefan Hajnoczi
---
include/qemu/lockable.h | 7
From: Simran Singhal
Replace manual lock()/unlock() calls with lock guard macros
(QEMU_LOCK_GUARD/WITH_QEMU_LOCK_GUARD).
Signed-off-by: Simran Singhal
Reviewed-by: Yuval Shaia
Reviewed-by: Marcel Apfelbaum
Tested-by: Yuval Shaia
Message-id: 20200402065035.GA15477@simran-Inspiron-5558
On 30.04.20 20:22, Markus Armbruster wrote:
> David Hildenbrand writes:
>
>> On 28.04.20 18:34, Markus Armbruster wrote:
>>> Both s390_features[S390_FEAT_PCC_CMAC_AES_256].name and
>>> s390_features[S390_FEAT_PCC_CMAC_EAES_256].name is
>>> "pcc-cmac-eaes-256". The former is obviously a pasto.
This seems to be timing out quite often and occasionally running out
of disk space. Relegate it to light duties.
Signed-off-by: Alex Bennée
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
index 49267b73b3..fe708792ca 100644
---
This keeps breaking on Travis so lets just fall back to the Cirrus CI
builds which seem to be better maintained. Fix up the comments while
we are doing this as we never had a windows build.
Signed-off-by: Alex Bennée
---
.travis.yml | 28 +---
1 file changed, 1
Signed-off-by: Alex Bennée
---
.travis.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.travis.yml b/.travis.yml
index 2fd63eceaa..a4c3c6c805 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -113,6 +113,7 @@ script:
$(exit $BUILD_RC);
fi
after_script:
+ - df -h
- if
Patchew URL:
https://patchew.org/QEMU/20200430181003.21682-1-peter.mayd...@linaro.org/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200430181003.21682-1-peter.mayd...@linaro.org
Subject: [PATCH 00/36] target/arm: Convert Neon
From: Daniel Brodsky
- ran regexp "qemu_mutex_lock\(.*\).*\n.*if" to find targets
- replaced result with QEMU_LOCK_GUARD if all unlocks at function end
- replaced result with WITH_QEMU_LOCK_GUARD if unlock not at end
Signed-off-by: Daniel Brodsky
Reviewed-by: Juan Quintela
Message-id:
From: Alexander Bulekov
The fuzzers are built into a binary (e.g. qemu-fuzz-i386). To select the
device to fuzz/fuzz target, we usually use the --fuzz-target= argument.
This commit allows the fuzz-target to be specified using the name of the
executable. If the executable name ends with
The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d:
Merge remote-tracking branch
'remotes/edgar/tags/edgar/xilinx-next-2020-04-30.for-upstream' into staging
(2020-04-30 16:47:23 +0100)
are available in the Git repository at:
https://github.com/stefanha/qemu.git
On Mon, 27 Apr 2020 at 15:32, Eric Auger wrote:
>
> Instead of using a compat in the mach-virt machine to force
> PPI off for all virt machines (PPI not supported by the
> tpm-tis-device device), let's simply change the default value
> in the sysbus device.
>
> Best Regards
>
> Eric
>
> Eric
On Thu, 30 Apr 2020 at 16:52, Kevin Wolf wrote:
>
> The following changes since commit 16aaacb307ed607b9780c12702c44f0fe52edc7e:
>
> Merge remote-tracking branch 'remotes/cohuck/tags/s390x-20200430' into
> staging (2020-04-30 14:00:36 +0100)
>
> are available in the Git repository at:
>
>
Hopefully this will un-stick the test which has been broken for a long
time.
Signed-off-by: Alex Bennée
---
.cirrus.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.cirrus.yml b/.cirrus.yml
index 90645fede6..f06f5af2b9 100644
--- a/.cirrus.yml
+++ b/.cirrus.yml
@@ -3,7
Hi,
The following updates bring us to green across the board again. MacOSX
has been getting continually flakey on Travis but we still have
coverage on Cirrus. Please review.
Alex Bennée (4):
.travis.yml: show free disk space at end of run
.travis.yml: drop MacOSX
.cirrus.yml: bump FreeBSD
Patchew URL:
https://patchew.org/QEMU/2020050505.4225-1-alex.ben...@linaro.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
From: Bin Meng
Per QEMU deprecated doc, QEMU 4.1 introduced support for the -bios
option in QEMU for RISC-V for the virt machine and sifive_u machine.
The default behavior has been that QEMU does not automatically load
any firmware if no -bios option is included.
Now 2 releases passed, it's
On 5/1/20 1:15 PM, Alex Bennée wrote:
This keeps breaking on Travis so lets just fall back to the Cirrus CI
builds which seem to be better maintained. Fix up the comments while
we are doing this as we never had a windows build.
Signed-off-by: Alex Bennée
---
.travis.yml | 28
On Fri, May 1, 2020 at 6:01 PM Bin Meng wrote:
>
> From: Bin Meng
>
> To keep sync with other RISC-V machines, change the default bios
> to use .bin instead of the .elf images.
>
> Signed-off-by: Bin Meng
> ---
>
> hw/riscv/spike.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Philippe Mathieu-Daudé writes:
> On 5/1/20 1:15 PM, Alex Bennée wrote:
>> This seems to be timing out quite often and occasionally running out
>> of disk space. Relegate it to light duties.
>> Signed-off-by: Alex Bennée
>> ---
>> .travis.yml | 2 +-
>> 1 file changed, 1 insertion(+), 1
Patchew URL:
https://patchew.org/QEMU/2020050505.4225-1-alex.ben...@linaro.org/
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
Ping?
On Tue, 14 Jan 2020, BALATON Zoltan wrote:
The movec opcode does not exist on 68000 and should raise an
exception. Fix the feature mask to only allow movec on newer 68k CPUs.
Signed-off-by: BALATON Zoltan
---
target/m68k/translate.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
On Fri, 1 May 2020, Alex Bennée wrote:
罗勇刚(Yonggang Luo) writes:
On Fri, May 1, 2020 at 7:58 PM BALATON Zoltan wrote:
On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
That's what I suggested,
We preserve a float computing cache
typedef struct FpRecord {
uint8_t op;
float32 A;
float32 B;
}
Sonora Pass is a 2 socket x86 motherboard designed by Facebook
and supported by OpenBMC. Strapping configuration was obtained
from hardware and i2c configuration is based on dts found at:
On Donnerstag, 30. April 2020 15:30:49 CEST Greg Kurz wrote:
> > > I agree that a client that issues concurrent readdir requests on the
> > > same fid is probably asking for troubles, but this permitted by the
> > > spec. Whether we should detect such conditions and warn or even fail
> > > is
On Fri, May 01, 2020 at 12:15:03PM +0100, Alex Bennée wrote:
> This keeps breaking on Travis so lets just fall back to the Cirrus CI
> builds which seem to be better maintained. Fix up the comments while
> we are doing this as we never had a windows build.
FYI the current problem with macOS
On Fri, May 01, 2020 at 12:15:01PM +0100, Alex Bennée wrote:
> Hi,
>
> The following updates bring us to green across the board again. MacOSX
> has been getting continually flakey on Travis but we still have
> coverage on Cirrus. Please review.
Does anyone ever look at the cirrus jobs ? They
Daniel P. Berrangé writes:
> On Fri, May 01, 2020 at 12:15:01PM +0100, Alex Bennée wrote:
>> Hi,
>>
>> The following updates bring us to green across the board again. MacOSX
>> has been getting continually flakey on Travis but we still have
>> coverage on Cirrus. Please review.
>
> Does
On 4/30/20 9:01 PM, Alex Bennée wrote:
We don't really need to track this fd beyond the initial creation of
the socket. We already know if the system has been initialised by
virtue of the gdbserver_state so lets remove it. This makes the later
re-factoring easier.
Signed-off-by: Alex Bennée
The fuzzers are built into a binary (e.g. qemu-fuzz-i386). To select the
device to fuzz/fuzz target, we usually use the --fuzz-target= argument.
This commit allows the fuzz-target to be specified using the name of the
executable. If the executable name ends with -target-FUZZ_TARGET, then
we select
On Fri, May 1, 2020 at 7:58 PM BALATON Zoltan wrote:
> On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
> > That's what I suggested,
> > We preserve a float computing cache
> > typedef struct FpRecord {
> > uint8_t op;
> > float32 A;
> > float32 B;
> > } FpRecord;
> > FpRecord fp_cache[1024];
>
On 5/1/20 1:15 PM, Alex Bennée wrote:
This seems to be timing out quite often and occasionally running out
of disk space. Relegate it to light duties.
Signed-off-by: Alex Bennée
---
.travis.yml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/.travis.yml b/.travis.yml
On Fri, May 1, 2020 at 8:41 PM Anup Patel wrote:
>
> On Fri, May 1, 2020 at 6:01 PM Bin Meng wrote:
> >
> > From: Bin Meng
> >
> > To keep sync with other RISC-V machines, change the default bios
> > to use .bin instead of the .elf images.
> >
> > Signed-off-by: Bin Meng
> > ---
> >
> >
> -Original Message-
> From: Qemu-riscv bounces+anup.patel=wdc@nongnu.org> On Behalf Of Bin Meng
> Sent: 01 May 2020 18:15
> To: Anup Patel
> Cc: Bin Meng ; open list:RISC-V ri...@nongnu.org>; Sagar Karandikar ; Bastian
> Koppelmann ; Palmer Dabbelt
> ; QEMU Developers
Philippe Mathieu-Daudé writes:
> On 4/30/20 9:01 PM, Alex Bennée wrote:
>> As gdb will generally be talking to "foreign" guests lets use that if
>> we can. Otherwise the chances of gdb barfing are considerably higher.
>> Signed-off-by: Alex Bennée
>> ---
>> configure | 2 +-
>> 1 file
If SELinux is setup without 'execmem' permission for qemu, all mmap
with (PROT_WRITE | PROT_EXEC) will fail and print a warning in
SELinux log.
If "nvlink2-mr" memory allocation fails (fist diff), it will cause
guest NUMA nodes to not be correctly configured (V100 memory will
not be visible for
BALATON Zoltan writes:
> On Fri, 1 May 2020, Alex Bennée wrote:
>> 罗勇刚(Yonggang Luo) writes:
>>> On Fri, May 1, 2020 at 7:58 PM BALATON Zoltan wrote:
On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
> That's what I suggested,
> We preserve a float computing cache
> typedef
Le 01/05/2020 à 15:11, BALATON Zoltan a écrit :
> Ping?
I sent a comment:
https://lists.gnu.org/archive/html/qemu-devel/2020-01/msg02840.html
Thanks,
Laurent
>
> On Tue, 14 Jan 2020, BALATON Zoltan wrote:
>> The movec opcode does not exist on 68000 and should raise an
>> exception. Fix the
Make it possible to specify the RLIMIT_NOFILE on the command-line.
Users running multiple virtiofsd processes should allocate a certain
number to each process so that the system-wide limit can never be
exhausted.
When this option is set to 0 the rlimit is left at its current value.
This is useful
The system-wide fs.file-max sysctl value determines how many files can
be open. It defaults to a value calculated based on the machine's RAM
size. Previously virtiofsd would try to set RLIMIT_NOFILE to 1,000,000
and this allowed the FUSE client to exhaust the number of open files
system-wide on
On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
That's what I suggested,
We preserve a float computing cache
typedef struct FpRecord {
uint8_t op;
float32 A;
float32 B;
} FpRecord;
FpRecord fp_cache[1024];
int fp_cache_length;
uint32_t fp_exceptions;
1. For each new fp operation we push it to
On 5/1/20 1:15 PM, Alex Bennée wrote:
Signed-off-by: Alex Bennée
---
.travis.yml | 1 +
1 file changed, 1 insertion(+)
diff --git a/.travis.yml b/.travis.yml
index 2fd63eceaa..a4c3c6c805 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -113,6 +113,7 @@ script:
$(exit $BUILD_RC);
On 5/1/20 1:23 PM, Daniel P. Berrangé wrote:
On Fri, May 01, 2020 at 12:15:01PM +0100, Alex Bennée wrote:
Hi,
The following updates bring us to green across the board again. MacOSX
has been getting continually flakey on Travis but we still have
coverage on Cirrus. Please review.
Does anyone
From: Bin Meng
To keep sync with other RISC-V machines, change the default bios
to use .bin instead of the .elf images.
Signed-off-by: Bin Meng
---
hw/riscv/spike.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/hw/riscv/spike.c b/hw/riscv/spike.c
index
On 4/30/20 9:01 PM, Alex Bennée wrote:
As gdb will generally be talking to "foreign" guests lets use that if
we can. Otherwise the chances of gdb barfing are considerably higher.
Signed-off-by: Alex Bennée
---
configure | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
罗勇刚(Yonggang Luo) writes:
> On Fri, May 1, 2020 at 7:58 PM BALATON Zoltan wrote:
>
>> On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
>> > That's what I suggested,
>> > We preserve a float computing cache
>> > typedef struct FpRecord {
>> > uint8_t op;
>> > float32 A;
>> > float32 B;
>> > }
After commit f01643fb8b47e8a70c04bbf45e0f12a9e5bc54de when an image is
extended and BDRV_REQ_ZERO_WRITE is set then the new clusters are
zeroized.
The code however does not detect correctly situations when the old and
the new end of the image are within the same cluster. The problem can
be
If SELinux is setup without 'execmem' permission for qemu, all mmap
with (PROT_WRITE | PROT_EXEC) will fail and print a warning in
SELinux log.
If "nvlink2-mr" memory allocation fails (fist diff), it will cause
guest NUMA nodes to not be correctly configured (V100 memory will
not be visible for
This patch series introduces the --rlimit-nofile=NUM option for setting the
number of open files on the virtiofsd process. This gives users and management
tools more control over resource limits.
Previously it was possible for FUSE clients on machines with less than ~10 GB
of RAM to exhaust the
On 5/1/20 4:15 AM, Alex Bennée wrote:
> This keeps breaking on Travis so lets just fall back to the Cirrus CI
> builds which seem to be better maintained. Fix up the comments while
> we are doing this as we never had a windows build.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 28
On Thu, 30 Apr 2020 at 21:28, Richard Henderson
wrote:
>
> On 4/30/20 11:09 AM, Peter Maydell wrote:
> > These don't use do_3same() because they want to
> > operate on VFP double registers, whose offsets are different from the
> > neon_reg_offset() calculations do_3same does.
>
> Actually, no,
I doubt the well predicted trace event check is particularly special in
the grand context of TCG code execution.
Signed-off-by: Alex Bennée
---
accel/tcg/trace-events | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/accel/tcg/trace-events b/accel/tcg/trace-events
Hi,
> On Apr 30, 2020, at 4:20 PM, Thanos Makatos
> wrote:
>
More importantly, considering:
a) Marc-André's comments about data alignment etc., and
b) the possibility to run the server on another guest or host,
we won't be able to use native VFIO types. If we do want to
Daniel P. Berrangé writes:
> On Fri, May 01, 2020 at 12:15:03PM +0100, Alex Bennée wrote:
>> This keeps breaking on Travis so lets just fall back to the Cirrus CI
>> builds which seem to be better maintained. Fix up the comments while
>> we are doing this as we never had a windows build.
>
>
+ Helge & Aleksandar.
On 5/1/20 12:59 AM, Sergei Trofimovich wrote:
On Thu, 16 Apr 2020 18:59:57 +0100
Sergei Trofimovich wrote:
Fix syscall name and parameters priinter.
Before the change:
```
$ alpha-linux-user/qemu-alpha -strace -L /usr/alpha-unknown-linux-gnu/ /tmp/a
...
1274697
On Fri, May 01, 2020 at 10:32:02AM +0100, Peter Maydell wrote:
> On Fri, 1 May 2020 at 09:28, Stefan Hajnoczi wrote:
> >
> > The following changes since commit 27c94566379069fb8930bb1433dcffbf7df3203d:
> >
> > Merge remote-tracking branch
> >
On Wed, Apr 29, 2020 at 08:42:50PM +0200, Volker Rümelin wrote:
> The win32 keycode for VK_OEM_102 is 0xe2. The Microsoft docu-
> mentation for virtual-key codes agrees with mingw32/winuser.h.
Yes, I concur. I must have made a typo when entering this.
>
> Signed-off-by: Volker Rümelin
> ---
>
Joseph Myers writes:
> Conversions between IEEE floating-point formats should convert
> signaling NaNs to quiet NaNs. Most of those in QEMU's softfloat code
> do so, but those for floatx80 fail to. Fix those conversions to
> silence signaling NaNs as well.
>
> Signed-off-by: Joseph Myers
From: Bin Meng
This updates the GitLab CI opensbi job to build opensbi bios images
for the generic platform.
Signed-off-by: Bin Meng
---
.gitlab-ci-opensbi.yml | 26 --
1 file changed, 8 insertions(+), 18 deletions(-)
diff --git a/.gitlab-ci-opensbi.yml
From: Bin Meng
The RISC-V generic platform is a flattened device tree (FDT) based
platform where all platform specific functionality is provided based
on FDT passed by previous booting stage. The support was added in
upstream opensbi recently.
Bring the QEMU roms/opensbi submodule to the
On Friday, 2020-05-01 at 09:56:12 -04, Alexander Bulekov wrote:
> The fuzzers are built into a binary (e.g. qemu-fuzz-i386). To select the
> device to fuzz/fuzz target, we usually use the --fuzz-target= argument.
> This commit allows the fuzz-target to be specified using the name of the
>
On 5/1/20 4:15 AM, Alex Bennée wrote:
> This seems to be timing out quite often and occasionally running out
> of disk space. Relegate it to light duties.
>
> Signed-off-by: Alex Bennée
> ---
> .travis.yml | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Richard Henderson
On 4/30/20 12:01 PM, Alex Bennée wrote:
> From: Philippe Mathieu-Daudé
>
> When converted to use GByteArray in commits 462474d760c and
> a010bdbe719, the call to stfq_p() was removed. This call
> serialize a float.
> Since we now use a GByteArray, we can not use stfq_p() directly.
> Introduce
On 4/30/20 12:01 PM, Alex Bennée wrote:
> We don't really need to track this fd beyond the initial creation of
> the socket. We already know if the system has been initialised by
> virtue of the gdbserver_state so lets remove it. This makes the later
> re-factoring easier.
>
> Signed-off-by: Alex
We are in freeze so nothing's applied right now.
v8 which has all the bits will be a good step so we
are ready for after freeze.
On Fri, May 01, 2020 at 07:01:58AM +0300, Yuri Benditovich wrote:
> Michael/Jason,
>
> As Linux headers was updated in qemu and now include RSC/RSS/Hash definitions,
>
On 4/30/20 12:01 PM, Alex Bennée wrote:
> @@ -814,7 +814,7 @@ int main(int argc, char **argv)
> exit(1);
> }
> } else if (!strcmp(r, "g")) {
> -gdbstub_port = atoi(argv[optind++]);
> +gdbstub = g_strdup(argv[optind++]);
You've got one
On 4/30/20 12:01 PM, Alex Bennée wrote:
> When the gdbstub code was converted to the new API we missed a few
> snafus in the various guests. Add a simple gdb test script which can
> be used on all our linux-user guests to check for obvious failures.
>
> Signed-off-by: Alex Bennée
>
> ---
> v2
>
On 4/30/20 12:01 PM, Alex Bennée wrote:
> +if "system" in args.qemu:
> +gdb_cmd += " -ex 'target remote localhost:1234'"
> +else:
> +gdb_cmd += " -ex 'target remote %s'" % (socket_name)
Why should not system testing be moved to sockets?
Surely that has the same problem in
Le 30/04/2020 à 21:01, Alex Bennée a écrit :
> From: KONRAD Frederic
>
> Currently "cf-core.xml" is sent to GDB when using any m68k flavor. Thing is
> it uses the "org.gnu.gdb.coldfire.core" feature name and gdb 8.3 then expects
> a coldfire FPU instead of the default m68881 FPU.
>
> This is
On 4/30/20 12:01 PM, Alex Bennée wrote:
> From: KONRAD Frederic
>
> Currently "cf-core.xml" is sent to GDB when using any m68k flavor. Thing is
> it uses the "org.gnu.gdb.coldfire.core" feature name and gdb 8.3 then expects
> a coldfire FPU instead of the default m68881 FPU.
>
> This is not OK
Hi,
Cleaning up my queues into more focused trees these are all tweaks to
TCG related stuff. The guest_base changes where posted before but
where a little radical for 5.0 but I think are worth getting in early
as it enables the sanitizer builds for a range of linux-user targets
we couldn't run
From: Richard Henderson
Signed-off-by: Richard Henderson
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
---
include/exec/cpu-all.h | 2 +-
bsd-user/main.c| 4 ++--
linux-user/main.c | 4 ++--
3 files changed, 5 insertions(+), 5 deletions(-)
diff --git
This will become useful shortly for providing more information about
output assembly inline. While there fix up the indenting and code
formatting in disas().
Signed-off-by: Alex Bennée
---
include/disas/disas.h | 2 +-
include/exec/log.h| 4 ++--
accel/tcg/translate-all.c | 4
From: Richard Henderson
We cannot at present limit a 64-bit guest to a virtual address
space smaller than the host. It will mostly work to ignore this
limitation, except if the guest uses high bits of the address
space for tags. But it will certainly work better, as presently
we can wind up
Richard Henderson writes:
> On 4/30/20 12:01 PM, Alex Bennée wrote:
>> +if "system" in args.qemu:
>> +gdb_cmd += " -ex 'target remote localhost:1234'"
>> +else:
>> +gdb_cmd += " -ex 'target remote %s'" % (socket_name)
>
> Why should not system testing be moved to
Patchew URL:
https://patchew.org/QEMU/20200501113704.2240698-1-patr...@stwcx.xyz/
Hi,
This series seems to have some coding style problems. See output below for
more information:
Message-id: 20200501113704.2240698-1-patr...@stwcx.xyz
Subject: [PATCH] aspeed: Add support for the
On 5/1/20 4:57 PM, Alex Bennée wrote:
This will become useful shortly for providing more information about
output assembly inline. While there fix up the indenting and code
formatting in disas().
Signed-off-by: Alex Bennée
Reviewed-by: Philippe Mathieu-Daudé
---
include/disas/disas.h
On Fri, May 01, 2020 at 03:01:01PM +, Felipe Franciosi wrote:
> Hi,
>
> > On Apr 30, 2020, at 4:20 PM, Thanos Makatos
> > wrote:
> >
> More importantly, considering:
> a) Marc-André's comments about data alignment etc., and
> b) the possibility to run the server on another
On Thu, 30 Apr 2020 at 21:54, Richard Henderson
wrote:
> You can morph this into the gvec interface like so:
>
> #define DO_3SAME_64(INSN, FUNC) \
> static void gen_##INSN##_3s(unsigned vece, uint32_t rd_ofs,
> uint32_t rn_ofs, uint32_t rm_ofs,
>
On 5/1/20 8:36 AM, Peter Maydell wrote:
> On Thu, 30 Apr 2020 at 21:54, Richard Henderson
> wrote:
>> You can morph this into the gvec interface like so:
>>
>> #define DO_3SAME_64(INSN, FUNC) \
>> static void gen_##INSN##_3s(unsigned vece, uint32_t rd_ofs,
>>
From: Bin Meng
The RISC-V generic platform is a flattened device tree (FDT) based
platform where all platform specific functionality is provided based
on FDT passed by previous booting stage. The support was added in
upstream opensbi recently.
This series updates QEMU to switch to use generic
From: Bin Meng
To keep sync with other RISC-V machines, change the default bios
to use generic platform image.
While we are here, add some comments to mention that keeping ELF
files here was intentional.
Signed-off-by: Bin Meng
---
hw/riscv/spike.c | 9 +++--
1 file changed, 7
On Thu, 30 Apr 2020 at 21:54, Richard Henderson
wrote:
>
> On 4/30/20 11:09 AM, Peter Maydell wrote:
> > +
> > +rn = tcg_temp_new_i64();
> > +rm = tcg_temp_new_i64();
> > +rd = tcg_temp_new_i64();
> > +
> > +for (pass = 0; pass < (a->q ? 2 : 1); pass++) {
> > +
On 5/1/20 6:10 AM, Alex Bennée wrote:
>
> 罗勇刚(Yonggang Luo) writes:
>
>> On Fri, May 1, 2020 at 7:58 PM BALATON Zoltan wrote:
>>
>>> On Fri, 1 May 2020, 罗勇刚(Yonggang Luo) wrote:
That's what I suggested,
We preserve a float computing cache
typedef struct FpRecord {
uint8_t
Please ignore. I think I misunderstood the issue with the pull-request.
Additionally, this patch still has incorrect spacing and is missing
review tags.
On 200501 0956, Alexander Bulekov wrote:
> The fuzzers are built into a binary (e.g. qemu-fuzz-i386). To select the
> device to fuzz/fuzz
First we ensure all guest space initialisation logic comes through
probe_guest_base once we understand the nature of the binary we are
loading. The convoluted init_guest_space routine is removed and
replaced with a number of pgb_* helpers which are called depending on
what requirements we have
We already have information about where each guest instructions
representation starts stored in the tcg_ctx->gen_insn_data so we can
rectify the PC for faults. We can re-use this information to annotate
the out_asm output with guest instruction address which makes it a bit
easier to work out where
Include support for outputting a note at the top of a chunk of
disassembly to capstone as well.
Signed-off-by: Alex Bennée
---
disas.c | 20
1 file changed, 12 insertions(+), 8 deletions(-)
diff --git a/disas.c b/disas.c
index bb74650633..5e7eb65326 100644
--- a/disas.c
From: Bin Meng
We only ship plain binary bios images in the QEMU source. With Spike
machine that uses ELF images as the default bios, running QEMU test
will complain hence let's suppress the error report for QEMU testing.
Signed-off-by: Bin Meng
---
hw/riscv/boot.c | 14 +++---
1
From: Bin Meng
Update virt and sifive_u machines to use the opensbi bios image
built for the generic FDT platform.
Remove the out-of-date no longer used bios images.
Signed-off-by: Bin Meng
---
hw/riscv/sifive_u.c | 4 ++--
hw/riscv/virt.c
1 - 100 of 173 matches
Mail list logo
